I am working on a fabric application where I have configured HTTPS. It is throwing an exception though I have a valid installed certificate.
I hope a separate answer is ok since I don't have the rep to comment. Here's the solution I found, which I didn't see mentioned anywhere else on SO or other sites. This is specific to the Windows certificate manager, not sure if other OSes run into similar issues.
dotnet dev-certs https
argumentsI tried various combinations of dotnet dev-certs https
with --trust
, --clean
--verbose
(which didn't seem to actually log any additional info), and --check
(which never found a certificate)
As suggested in other answers, I deleted all localhost certificates under Trusted Root Certification Authorities\Certificates in certmgr.msc
in conjunction with dotnet dev-certs https --clean
Eventually I realized that certmgr.msc
also showed a number of localhost certificates under Personal\Certificates, in addition to those under Trusted Root Certification Authorities\Certificates. It turned out that these all needed to be deleted.
Then running dotnet dev-certs https -t
a single time created and trusted a new development certificate.
I verified by debugging an ASP.NET Core App. Another way to verify is by running dotnet dev-certs https --check --verbose