Unable to configure HTTPS endpoint. No server certificate was specified, and the default developer certificate could not be found

asp.net Core .Net Core asp.net Core-2.1 Kestrel

asp.net Core Problem Overview

I am working on a fabric application where I have configured HTTPS. It is throwing an exception though I have a valid installed certificate.

asp.net Core Solutions

Solution 1 - asp.net Core

These instructions from this blog worked for me

dotnet dev-certs https --clean
dotnet dev-certs https -t
Restart VS

Solution 2 - asp.net Core

I am on OSX and dotnet dev-certs https --clean and sudo dotnet dev-certs https --clean were not working for me. Finally I was able to fix it with the following steps.

Go into Keychain Access
Unlock System Keychain
Delete the localhost certificate
Run dotnet dev-certs https -t

You should now be able to run without the error.

Edit:

If, after following the above answer, you do run into an error that reads There was an error saving the HTTPS developer certificate... check out this answer https://stackoverflow.com/a/56709117/621827

Solution 3 - asp.net Core

Solution

(for Windows, not sure if there's an equivalent issue/solution for other OSs)

In a command prompt or Powershell terminal:

Run certmgr.msc and delete all localhost certificates under both Personal\Certificates and Trusted Root Certification Authorities\Certificates.
Then run dotnet dev-certs https -t a single time to create and trust a new development certificate.
Verify by running dotnet dev-certs https --check --verbose, or just try debugging your ASP.NET app again.

You may also need to run dotnet dev-certs https --clean before creating the new certificate.

Solution 4 - asp.net Core

For me the problem was resolved by running:

dotnet dev-certs https --clean
dotnet dev-certs https --verbose

Solution 5 - asp.net Core

I had this issue on my Windows 10 system using visual studio. The problem seemed to be that the command used in the GUI to clear the local certs for HTTPS was failing with an error message that I can no longer reproduce.

The solution for me was to open the certmgr for the current windows account and to delete all of the personal localhost certs. There was ~20 certs there for me because I've tried re-creating them many times. After deleting all of those certs I ran my .Net core HTTPS API once more and everything worked!

In summary, open your certmgr for your current user and clear all personal/localhost certs.

Solution 6 - asp.net Core

For me deleting the files under file:\\%APPDATA%\Microsoft\SystemCertificates\My\Certificates and run in cmd dotnet dev-certs https -t solved my issue.

Solution 7 - asp.net Core

In windows, dotnet dev-certs https --clean doesn't work for me, I have to delete these localhost certs manually.

Open certmgr.msc
Delete all localhost certs under 'Trusted Root Certification Authorities/Certificates'
Run dotnet dev-certs https -t

Solution 8 - asp.net Core

Open RUN , then type mmc.exe, then

double click certificate

Delete localhost cert in both folders

then open your powershell

dotnet dev-certs https --clean
dotnet dev-certs https 
dotnet dev-certs https --trust

Solution 9 - asp.net Core

I had a similar (but not exactly the same) problem.
With 2.1 you have to configure your certificate.
I do this now completely in appsettings.json.
You can find my posting here:
Configure self hosting Kestrel App with certificate for https (internet web server)

Only have a look to the solution...

Solution 10 - asp.net Core

If dotnet dev-certs https --clean not working.

Open Run and open mmc.exe
Inside MMC from File menu click on Add/Remove Snap-in.
In the add/remove snap-in window, find certificates in available snap-ins and add it to the selected
Pick User account
In the console root -> Certificates Current User -> Personal click on Certificates
You will see the list of issued and installed certificates for the current user. DON’T remove or change any certificates you don’t know, only remove certificates related to self-sign localhost ASP.NET Core.

Solution 11 - asp.net Core

I had the same issues and cleaning -> then installing certs helped me (another answer here). You also may issue a certificate as like for production server. Quite helpful to know.

Solution 12 - asp.net Core

Not sure if this will help anybody else but I had exactly this issue on my Mac. I have the project in Dropbox and so it is shared across machines, on the '2nd' machine I had to go in and manually delete the 'obj' and 'bin' folders, then re-run the application and it all worked

Solution 13 - asp.net Core

If you want to work with an environment that is not Development, don't forget that user secrets are only added automatically when env is Development.

You can use the AddUserSecrets methods to resolve this :

public static IHostBuilder CreateHostBuilder(string[] args) =>
        Host.CreateDefaultBuilder(args)
            .ConfigureWebHostDefaults(webBuilder =>
            {
                webBuilder.ConfigureAppConfiguration((hostingContext, builder) =>
                {
                    var env = hostingContext.HostingEnvironment;
                    if (env.IsEnvironment("Local"))
                    {
                        builder.AddUserSecrets<Startup>();
                    }
                })
                .UseStartup<Startup>();
            });

Solution 14 - asp.net Core

I was having the same issue. The problem was that the project was with .net 4.6.1 and not .net core .

Solution 15 - asp.net Core

I run this on my command prompt. btw I am using Window 10 dotnet dev-certs https dotnet dev-certs https -t

Solution 16 - asp.net Core

dotnet tool uninstall --global dotnet-dev-certs --version (required version)
dotnet tool install --global dotnet-dev-certs
dotnet dev-certs https --trust

For more details visit the GitHub issue page here also the official documentation Here

Solution 17 - asp.net Core

I ran into this problem and my solution was to restart. When I did and then reopened Visual Studio 2019, it asked me to accept a new SSL certificate. After that, I was able to run my program.

Solution 18 - asp.net Core

One more detail - If you generally log in as a normal (non-admin) user, do NOT run the "dotnet dev-certs https" commands from an admin command prompt if you have a separate admin-level identity. Run them in a normal command prompt under your normal login. Ask me how I know. :-P

If you run these commands from an elevated command prompt (using a distinctly separate admin identity) you will experience the following:

"dotnet dev-certs https --trust" will work just fine
"dotnet dev-certs https --check --verbose" will tell you that everything is fine
VS Code will continue to spit out the "Unable to configure HTTPS endpoint ..." error when you try to start the debugger
You will continue to get "Certificate Not Trusted" warnings from your browser.

If you see these issues, run the "dotnet dev-certs https" commands from a normal command prompt. Fixed it for me. Hope this helps someone without spending the time that I did on this!

Solution 19 - asp.net Core

If you are visiting this page and if you are unfortunate like me who tried every single solution/approach mentioned on this page but nothing worked, then you may like to know what I did and solved my problem.

I was getting this error from my ASP.NET Core web application no matter how many times I deleted the localhost certificates.

Then, I created a self-signed certificate using Powershell with this command. [I copied this PowerShell snippet from somewhere on the internet. Cannot remember the source.]

  $cert = New-SelfSignedCertificate -DnsName mydemowebapp.net -CertStoreLocation cert:\LocalMachine\My
  $pwd = ConvertTo-SecureString -String "MyPassword" -Force -AsPlainText
  Export-PfxCertificate -Cert $cert -FilePath C:\temp\cert.pfx -Password $pwd

Then, in my appsertings.Development.json, I added this entry.

  "Kestrel": {
    "EndPoints": {
      "Https": {
        "Url": "https://localhost:5000",
        "Certificate": {
          "Path": "C:\\temp\\cert.pfx",
          "Password": "MyPassword",
          "AllowInvalid": "true"
        }
      }
    }
  }

Ran the application, boom! problem solved. I used the same URL https://localhost:5000 as I found in my LaunceSettings.

I hate a solution like this, but at least I could continue my development with such a solution. I do not know what really happened recently that I had to face this issue. Was that a windows update? or something else? I don't know. I did not face this issue before, until recently. And yes, I remembered to run the Website in Kestrel rather than IIS.

Solution 20 - asp.net Core

Generate a new certificate:

$ dotnet dev-certs https --trust
The HTTPS developer certificate was generated successfully.

Solution 21 - asp.net Core

I commented following line in 'Startup.cs' file, and it worked for me.

app.UseHttpsRedirection();

Content Type	Original Author	Original Content on Stackoverflow
Question	Balanjaneyulu K	View Question on Stackoverflow
Solution 1 - asp.net Core	Peter Morris	View Answer on Stackoverflow
Solution 2 - asp.net Core	Stephen Gilboy	View Answer on Stackoverflow
Solution 3 - asp.net Core	hikarikuen	View Answer on Stackoverflow
Solution 4 - asp.net Core	Davor	View Answer on Stackoverflow
Solution 5 - asp.net Core	SomeGoodCodeHelp	View Answer on Stackoverflow
Solution 6 - asp.net Core	Veleirian	View Answer on Stackoverflow
Solution 7 - asp.net Core	Liang	View Answer on Stackoverflow
Solution 8 - asp.net Core	Amith Thillenkery	View Answer on Stackoverflow
Solution 9 - asp.net Core	FredyWenger	View Answer on Stackoverflow
Solution 10 - asp.net Core	Mehdi Daustany	View Answer on Stackoverflow
Solution 11 - asp.net Core	cyberpug2077	View Answer on Stackoverflow
Solution 12 - asp.net Core	Kevin Jones	View Answer on Stackoverflow
Solution 13 - asp.net Core	Maxime Frappat	View Answer on Stackoverflow
Solution 14 - asp.net Core	Fernando Moreira	View Answer on Stackoverflow
Solution 15 - asp.net Core	hr person	View Answer on Stackoverflow
Solution 16 - asp.net Core	Jawahar05	View Answer on Stackoverflow
Solution 17 - asp.net Core	dmrobotix	View Answer on Stackoverflow
Solution 18 - asp.net Core	Steve G	View Answer on Stackoverflow
Solution 19 - asp.net Core	Emran Hussain	View Answer on Stackoverflow
Solution 20 - asp.net Core	Jhonny Ramirez Zeballos	View Answer on Stackoverflow
Solution 21 - asp.net Core	siddharth borania	View Answer on Stackoverflow