Forum Discussion
Solved
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 anyth...
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
Eric_Lawrence starting edge dev (82.*) with msedge.exe --disable-features=PostQuantumCECPQ2 is working for me.
I don't know if we are using ZScaler, I'll check it with our IT department.
Eric_Lawrence We are not using ZScaler, we are seeing this issue with citrix netscaler.