r machine. That doesn't seem to be very helpful when it comes to localhost development certificates, which are more or less throwaway certs managed by development tools. Thankfully, you can get around this quickly and easily through the browser by configuring the browser flags.

If you're using Edge or Chrome, go into edge://flags or chrome://flags and look for the Allow invalid certificates for resources loaded from localhost flag. Change that setting from Disabled to Enabled, and now your browser will accept your localhost certificates.

It's a simple solution to a problem that's hard to find any answers for, though maybe the AI bots already know this by now (though a quick ask seems to indicate otherwise). In any case, here's where we found the answer:

https://stackoverflow.com/questions/62699391/how-to-bypass-certificate-errors-using-microsoft-edge/

Hope that helps!

Looking for help upgrading your web apps to Blazor? Contact us and let's see what we can do to help!