Microsoft Edge forcing HTTPS and refusing a self-signed certificate

Question

Doing dev work on several sites on my local (Windows 10) PC when out of the blue this morning one site refuses to load in Microsoft Edge (Version 89.0.774.45 (Official build) (64-bit)). Other local sites are working fine.

I removed the redirect to SSL from web.config and issued a fresh self-signed certificate: NET::ERR_CERT_COMMON_NAME_INVALID - You can't visit local-prodject.mydomain.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.

There is no HSTS in web.config. I removed the HTTPS redirect from web.config and it's still trying to force HTTPS. I've done the edge://net-internals/#hsts to delete for local-prodject.mydomain.com and localhost, no change.

I'd prefer to have self-signed working as it was yesterday, and on other sites on my local PC so when they get pushed to a production environment they're ready to go.

I should also note that Chrome and Firefox (Dev and regular) work fine.

Have you followed the steps like [this article](https://www.thesslstore.com/blog/clear-hsts-settings-chrome-firefox/) to delete HSTS settings? Have you specified the proper subdomain when delete? The HSTS settings for subdomains may be different. I suggest that you can clear Edge cache and history to try again. You can also try in inprivate window to see if the issue still exists. — Yu Zhou, Mar 10 '21 at 08:25
Yes, I've cleared HSTS and it seems to help for a short while. I've resorted to typing "thisisnotsafe" in the browser window in Edge and Chrome now to get to any of my local dev sites. — Steve, Apr 01 '21 at 19:34
It seems that you have found a workaround for the issue. You can put it as an answer which can help other community members in future in similar kind of issues. Thanks for your understanding. — Yu Zhou, Apr 05 '21 at 08:04

score 47 · Accepted Answer · edited Jun 23 '23 at 07:12

47

Chrome, Opera, and Edge have a safe word you can use to bypass this SSL issue for local development. Click anywhere within the browser window and type: thisisunsafe

edited Jun 23 '23 at 07:12

TylerH

20,799
66
75
101

answered Apr 06 '21 at 11:08

Steve

2,776
3
25
44

will this add the exception permanently ? – J Santosh Sep 18 '21 at 06:17
No the exception is not permanent. – Steve Sep 19 '21 at 13:23
Edge will remember it in a normal window, then it will have effect with InPrivate windows as well. – Nagev Jul 19 '22 at 12:58

Microsoft Edge forcing HTTPS and refusing a self-signed certificate

1 Answers1