Just a friendly reminder to myself (and for whom it may concern): This error message tends to appear when the ASP.NET API can’t talk to the IdentityServer.
Especially tricky when using an ASP.NET API and IdentityServer4 behind a reverse proxy (like nginx). The external world might be able to talk to the IdentityServer, but the API server / container might need some additional configuration with the internal host:port of the IdentityServer.
After not finding a good resoure online and having to ask a colleague here is what he has told me to do:
Start the app in the browser. Instead of the app content Chrome displays a security warning “Your connection is not private”
Click on the “Not secure” field
Click on certificate
Select the “Details” tab
Click on “copy to file” button. The wizard opens
Safe certificate as a file (go with the defaults)
Use the default format and save to a file of your choice.
Open the saved certificate file with doubleclick
Go with “Current User” and click next.
Add certificate to the windows certificate store. Make sure to select “Trusted Root Certification Authorities”. (Disclaimer: I don’t really like to add dev certificates to that store because they are definitely not CA Authorities, but the other stores do not seem to work. If you find a better way feel free to send me an email or Twitter message)
Finish the installation
Confirm security warning with yes. (like I said above. Please tell me if you have a better solution)
Restart Chrome and try again.
Chrome should be happy now, show the lock-symbol instead of the warning and load your application!
(corrections 21.07.2020: I have falsely written “Multithreading” instead of “Hyperthreading” in some places)
Because my Windows Server 2019 guest system felt quite sluggish, I first googled (of course! 😉 and then tested myself to improve the performance.
Thanks to a blog entry from Mihai Matei on the topic at hand y had an idea on where to look and I could confirm his findings regarding Hyperthreading.
Here are my test-details, in case you are interested. If not you can jump right to the conclusions at the end of the article.
CPU: Intel 8350U (4 Cores, 8 Threads, 15W TDP) Host RAM: 32GB Host OS: Windows 10 Pro (1809) 64 bit Guest OS: Windows Server 2019 Benchmarking-Tool: CPU-Z
Hyperthreading on (Bios setting on host)
CPU-Z benchmark results on the host
Guest with 4 Cores
Observation: Opening Windows Explorer slow
SC: 280 Max
MC: 1300 Max
Guest with 1 Core
Observation: Opening Windows Explorer much faster
Note: SC is substantially higher, but MC a lot lower. The GUI feels a lot more responsive with only 1 core assigned.
Hyperthreading off (Bios setting on host)
CPU-Z on the host
Note: SC performance not changed, but about 25% loss on MC performance.
Guest with 4 Cores
1) Task manager on guest: 6% (almost idle), task manager on host: 28% for VirtualBox task
2) CPU-Frecuency drops from 3,6 to 2,5 during MC test and goes only back up to 3Ghz during SC. Explanation: CPU seems to throttle because of temperature (monitored with HW Info Tool). Environment temp is about 32 C
SC: 295 Max
MC: 1070 Max
Guest with 1 Core
Observation: The benchmark does not get 100% CPU, because 18% is eaten up by “System Interrupts” accoring to task manager.
Guest with 2 Cores
Observation: System interrupts low (2%, almost all % used by benchmark)
Note: Best result so far. SC performance still high and MC doubled compared to 1 Core.
Guest with 3 Cores
Observation: System interrupts low (2%, almost all % used by benchmark). Looks like 3 cores is not a good idea! 😉
On my particular system the best setting for my Windows Server 2019 guest are:
Host: Disable Hyperthreading in BIOS settings
VirtualBox Guest Settings: Assign 2 cores
Due to the switched off hyperthreading some mulithreading performance is lost. But as I am mostly depending on high single-threading performance for compiling tasks it is not an issue.
Depending on your CPU and number of cores available your optimal settings may vary.
Object Exporter – Serialize objects in memory captured with the Debugger. I use it to generate test-data for integration tests (legacy applications). Needs some tweaks to install on Visual Studio 2019. See also the authors homepage.
AsyncFixer – Helps you detecting and fixing bad usage of async/await in your code.
Tweaks – A collection of minor fixes and tweaks for Visual Studio to reduce the paper cuts and make you a happier developer
LINQPad – Amazing power-tool. Instantly test .NET code snippets, query your database, create and analyse LINQ/Entity framework queries. Most used by me to create, analyse and run LINQ to entities queries. It will show the generated SQL and query you database for you. Great learning utility also. It has a ton of code examples from the book C# 3/4/5/6/7 in a Nutshell.
ReSharper – Helps you writing better code. Tons of hints for improvements. Great test-runner. Performance tip: Exclude the ..\AppData\Local\Jetbrains folder from the antivirus realtime-protection.
WinDirStat – Visualize the occupied space on your disk. I use that for deleting crap when the disk is getting full.
MiniTool Partition Wizard – Manage partitions, move OS from harddrive to SSD and much more. Many features already available in the free version.
CPU-Z – Lightweight and fast tool to check you hardware-configuration and run some basic CPU benchmarks.
Paint.NET – Free and powerful image editor. When Photoshop is too much (and too expensive).
ActivePresenter– Records your screen and microphone. Used it for recording tutorials (screencast for YouTube). It also makes a great tool for helping you test your GUI, as you can record what you are doing and what is happening. When something breaks, you can replay and go back in time. Version 7 did not work for me, better try Version 6 of their program while it’s still available.
Health and productivity
OneNote – All my notes, bookmarks, screenshots and complete knowledge bases go into OneNote. Make screenshots, format your entries with simple keyboard-shortcuts without touching the mouse, collaborate on content with notebooks stored on MS SharePoint or OneDrive.
EyeLeo – Prevents eye strain. Gentle reminders now and then to get your eyes off the screen.
Tomighty Pomodoro timer – Get more done with more breaks. The Pomodoro technique works out great for development. Moving my body every half-hour amps up my creativity and helps me getting unstuck. I prefer to move my body, jog for a couple of minutes. Many times it’s off the screen when the aha-moments hit me.
For a much more extensive list of tools check out the resource from Scott Hanselman. Last time I checked it has been updated in 2014, but still of great value for discovering stuff:
I quite like it. A few notes about some issues I had:
Don’t mix testing frameworks (MsTest, NUnit, xUnit). Live testing will use one or another test adapter, but only one at the same time. Depending on which one is active you will have tests excluded from live-testing.
Update your references. If you cannot debug your unit-tests anymore with Live Unit Testing enabled, have a look at this support case. You might need to delete your existing project reference to “Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll” and install the NuGet packages MSTest.TestAdapter and MSTest.TestFramework instead.
Choose your tests wisely. You might want to exclude your long-running integration tests and other tests from being executed by Live Unit Testing: Right-Click on your test project, go into that “Live Unit Testing” entry and include and exclude what you need to be covered by Live Testing.
Included test files not updated automatically. If you have included test-data files in your project that are copied to your Output Directory by the build process: These are not updated automatically. I had to Stop and Start Live Testing in order to access added or updated files.