Forum Discussion
MS Edge Dev 81.0.389.2 won't load any (remote) sites over HTTPS
Some time after receiving the latest update on the dev channel, the browser seemingly broke for almost all HTTPS sites. I've got a local webpack dev server running that still seems to work, but anything other than localhost seems to fail.
One example is http://www.httpvshttps.com/ which loads fine, but as soon as I select to run the test over HTTPS, I immediately get the "Hmmm... can't reach this page" with an "ERR_CONNECTION_CLOSED" error code. Google.com, bing.com, etc, they all fail.
I've tried it on several different networks, but the issue still persists.
Every other browser on my system works just fine (Firefox, Edge (Non-Chromium), IE, Chrome Dev, and Edge Dev worked fine up until very recently (last week, perhaps?). I mostly use it as a browser for development, so it might've broken before the latest dev channel update, but that's when I first discovered it.
I've tried reinstalling Edge Dev, I've double-checked that it's not using any weird proxy settings, my OS and AV is fully updated (Win 10 b1909, Windows Defender). Maybe there's an obvious thing causing this, but I can't see it 
adamohman danielthecoder oddnes
This is very likely the same issue as some users saw in December, whereby most or all HTTPS connections fail with one of several error messages. You can verify if this is the case by closing all Edge instances and hitting Win+R, then running
msedge.exe --disable-features=PostQuantumCECPQ2If that works, then something on your network path is not compatible with large ClientHello messages in the HTTPS handshake. For instance, older versions of ZScaler are known to have a bug whereby they fail to "pass along" the ServerNameIndicator TLS extension if the ClientHello spans multiple packets, and when that happens, the server typically will return the wrong certificate, resulting in a NET::ERR_CERT_COMMON_NAME_INVALID error message. ZScaler has released a fix for this that you'll need to apply.In other cases, the network device is completely incompatible with handshakes that span multiple packets and an ERR_CONNECTION_RESET will be seen instead. You'll need to talk to your network administrators about contacting the vendor of your networking equipment about getting a fix.The reason this issue appeared and disappeared only to reappear again is because the PostQuantumCECPQ2 feature was changed to "off-by-default" for version 80/81 but it is now enabled again for version 82.
The upstream issue can be found here: https://crbug.com/1028602
oddnes Thanks for letting us know. If the issue is persisting, can you please first try on the newest version of MS Edge Dev then Canary? And if it's still not working, it would be great if you could submit feedback through the browser so our devs can see the logs.
Fawkes (they/them)
Project & Community Manager - Microsoft EdgeDeleted
Currently I've the same problem with Edge Dev (82.0.425.3) and Edge Can (82.0.436.0)
danielthecoder I have the exact same problem, started with Edge Dev 82.0.425.3 and is still present with 82.0.432.3. I downloaded Canary today (82.0.437.0), same problem.
Deleted At my organisation, we use Zscaler. I used to have the "Your connection isn't private" issue that was talked about in https://techcommunity.microsoft.com/t5/discussions/your-connection-isn-t-private-zscaler/m-p/1059762, but that went away after some update and all was good for a while.
I have also sent this as feedback through the browser.
