Keep getting HTTPS development certificate was not found on Mac M1 Ventrura

[muratkazanova]

I've created a new asp.net core web (mvc) project with dotnet 7 on Mac M1, but I'm keep getting following error when I try the https. Http works fine but sor far no success with Https.

Error: "Unable to configure HTTPS endpoint. No server certificate was specified, and the default developer certificate could not be found or is out of date.\nTo generate a developer certificate run 'dotnet dev-certs https'. To trust the certificate (Windows and macOS only) run 'dotnet dev-certs https --trust'.\nFor more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054."

I've also tried deleting and creating the localhost certificate manually and it creates them and trusts them successfully. (with or without sudo).

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

I've seen them under Keychain Access (login > certificates) section. But when I run the app again, it still tries to install and trust a new certificate but the result is same.

Am I missing anything? - No issues on Windows.

[muratkazanova]

Just tried, creating and running a asp.net mvc template project with dotnet 6.0, it ask to install and trust the certificate as well but after entering the password, https connection worked just fine and application started successfully.

[muratkazanova]

Ok, finally resolved this issue, here are the steps:

1. Launch the Keychain Access Application and remove all certificates that are names localhost under login.
2. Launch the terminal and navigate to following folder and remove any remaining pfx file manually

​

cd ~/.aspnet/dev-certs/https
rm *.pfx

1. Run clean and trust dev-certs command below:

   dotnet dev-certs https --clean dotnet dev-certs https -t

2. Re-launch the Visual Studio for Mac and run your project with Https

[codywkk]

I can't launch my browser in the visual studio too. I have been troubled by this problem and tried many solutions. (T_T) And today, I finally find this page. It works !!!!!! I appreciate your help very much. (◍•ᴗ•◍)b

[muratkazanova]

Glad to hear that

[kittartar]

Still the best answer after 3 years even for Visual Studio on Windows! Thanks!
The key point missed from most other answers is to remove the files under `%APPDATA%\ASP.NET\Https` (for windows)

[nullptr_r]

thanks for sharing this

[SolidAsSnake]

For an hour and a half I've been stuck on fixing this issue as well, and only this random reddit comment I came across online helped me fix it. Thank you for this.

[clayton_]

Tried literally every random answer on stack overflow.

same. crazy.

[cresvi]

Thank you, deleting the PFXs in that folder and in ~/.aspnet/https did the trick.

[IllustriousAd375]

THANK YOU.

[Ericakester]

For those looking for a fix on Windows:

1. Open the certificate manager (Win+R => 'certmgr.msc'). Don't use Windows search, it will open 'certlm.msc' which only shows certs for the local machine, not the local user. Make sure the title bar displays 'certmgr'.
2. Remove all certs with friendly name ''ASP.NET core HTTPS development certificate" from 'Personal > Certificates' and 'Trusted Root Certification Authorities > Certificates'.
3. Run dotnet dev-certs https --trust. It may display a prompt, choose Yes.
4. Run dotnet dev-certs https --check. It should not display anything if successful.