Visual Studio 2019：本地主机上的“此站点无法提供安全连接”

Question

I've installed Visual Studio 2019 and uninstalled Visual Studio 2017.

Now if I start an ASP.NET (Core) site with https, it always say on Chrome:

This site can't provide a secure connection

or on Edge

Can't connect securely to this page

Screenshots:

Chrome:

Edge:

The URLs are correct. This also the same http://localhost:56784/ (it redirects to https)

Tried

What I've tried:

• Updated Visual Studio 2019
• Create a new ASP.NET Core 2 website
• Tested with a ASP.NET site (non core)
• Remove IIS certificates with MMC
• Checking/changing the IIS settings in Visual Studio 2019 (project properties with context menu and project properties with F4)
• Searching on Stackoverflow & Google;)
• Repair Visual Studio 2019

Issue

I think the issue is introduced by:

• Installing Visual Studio 2019 and/or,
• Uninstalling Visual Studio 2017 and/or,
• Updating Windows 10 (current Version: 10.0.18362 Build 18362)

The underlining issue looks like a wrong/old/not supported TLS version?

Question

What can I do to diagnose/fix the problem?

Answer 1

Just as it did not work for @Nosnetrom - repairing IIS 10.0 Express did not work for me either. As @Julian mentioned my problem was caused by uninstalling VS 2017 as well.

This is what did not work for me:

• uninstalling / re-installing VS 2019
• installing VS 2017
• uninstalling / re-installing / repairing IIS 10.0 Express

This is what worked for me:

• after reading this advice - I realized that I was using port 51542 instead of a port in the range of 44300 through 44399
• then I updated the applicationhost.config file according to this advice. The location of said file on my Windows 10 machine is: C:\Program Files (x86)\IIS Express\config\templates\PersonalWebServer\applicationhost.config . I had to open that file in Notepad ran as an administrator otherwise I could not save these changes:
• then in Visual Studio I created a new virtual directory
• that seemed to have done the trick for me - when I ran the application it worked

Answer 2

Repair of IIS Express fixed my problem:

Answer 3

None of this worked for me. What did work (and it's not as drastic as the other answers)...

Go into web project and set Start URL and Project URL to this: https://localhost:44365/

Save (but don't run the Project).

Edit.vs/[ProjectName]/config/applicationhost.config and change the bindings for the web project to this:

<binding protocol="https" bindingInformation="*:44365:localhost" />
<binding protocol="http" bindingInformation="*:53269:localhost" />

Reopen Visual Studio and when I started the website it worked.

Answer 4

I solved this problem as follows;

1. run the web project in debug mode on Visual studio 2019.
2. if it's on chrome you should do this; Empty cache and hard reload

Answer 5

For those who all the above methods didn't worked:

open a command prompt and then run:

dotnet dev-certs https --clean

and then:

dotnet dev-certs https --trust

Answer 6

In my case use SSL check box was gone in debug section of project properties. everything was fixed by checking again

Answer 7

Right click on the project, select Properties, 'Debug', check the checkbox "Enable SSL", that's it, worked with me by doing this

Answer 8

None of the above solutions worked for me, Following steps worked for me. Go to chrome or edge browser and type chrome://net-internals/#hsts search for localhost in query domain, you will find lists of domain including localhost. Now delete the domain

Delete the domain by typing localhost

Answer 9

Just follow below steps:

1. Close Visual Studio
2. Delete .vs folder
3. Restart Visual Studio
4. Build and Run the Application

As per my understanding, .vs folder keeps the old settings inside the applicationhost.config file. So better to delete all cached settings and start with fresh.

Answer 10

If you 'are using services.AddHttpsRedirection like

services.AddHttpsRedirection(options =>
{
    options.RedirectStatusCode = (int)HttpStatusCode.TemporaryRedirect;
    options.HttpsPort = Configuration.GetValue<int?>("https_port", null);
});

Make sure HttpsPort is null or a valid port in appsettings.json or appsettings.Development.json file.

Answer 11

Clear your browser history and cookie