When I'm trying to run a new MVC app from the localhost, I receive the following error both in Edge and in Chrome:
The connection for this site is not secure, localhost uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Unsupported protocol
The client and server don't support a common SSL protocol version or cipher suite.
The two standard Microsoft commands have no effect, the certificate is created but the problem persists.
Outdated certificates are not present in my C:/Users/…/AppData/Roaming/ folder. So it looks like that's not the issue with old certificates.
The ASP.NET folder exists in the C:/Users/…/AppData/Local/ASP.NET, deleting files from it has no effect either.
When I comment out the app.UseHttpsRedirection(); , the app starts, but in the http mode only
I had the same issue with Blazor WebAssembly, but I resolved it somehow, probably by tinkering with Win+R and running mmc and adding certificates manually. I don't know whether it helped or something else happened.
This time running mmc and installing the certificates manually seems to have no effect. I followed the instructions from this Microsoft page:
https://docs.microsoft.com/en-us/troubleshoot/developer/visualstudio/installation/warnings-untrusted-certificate
When I'm trying to run a new MVC app from the localhost, I receive the following error both in Edge and in Chrome:
The connection for this site is not secure, localhost uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH Unsupported protocol The client and server don't support a common SSL protocol version or cipher suite.
The two standard Microsoft commands have no effect, the certificate is created but the problem persists.
Outdated certificates are not present in my C:/Users/…/AppData/Roaming/ folder. So it looks like that's not the issue with old certificates. The ASP.NET folder exists in the C:/Users/…/AppData/Local/ASP.NET, deleting files from it has no effect either.
When I comment out the
app.UseHttpsRedirection();
, the app starts, but in the http mode onlymy LaunchSettings.json:
I had the same issue with Blazor WebAssembly, but I resolved it somehow, probably by tinkering with
Win+R
and runningmmc
and adding certificates manually. I don't know whether it helped or something else happened. This time runningmmc
and installing the certificates manually seems to have no effect. I followed the instructions from this Microsoft page: https://docs.microsoft.com/en-us/troubleshoot/developer/visualstudio/installation/warnings-untrusted-certificate