Forum Discussion
MS Edge Dev 81.0.389.2 won't load any (remote) sites over HTTPS
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 Edge
Deleted
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.
- Eric_Lawrence
Microsoft
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/1028602Eric_Lawrence Thank you so much, msedge.exe --disable-features=PostQuantumCECPQ2 did the trick for accessing external/remote https sites! I will pass the info about the Zscaler "support case 983026 / (view restricted) issue 1033401" that you mentioned 17 Jan 2020 on https://bugs.chromium.org/p/chromium/issues/detail?id=1028602 to our network team. If you have any more details or more recent information about the fix, I would be (even more) grateful.
To summarize and also confirm danielthecoder's findings:
Chrome (80.0.3987.122 ) = OK
Chrome Dev (82.0.4068.5) = Error
Edge Dev (82.0.432.3) = Error
Edge Canary (82.0.438.0) = ErrorEdge Dev with the --disable-features=PostQuantumCECPQ2 flag = OK
And thanks oddnes for starting this thread!
Cheers,
Adam
adamohman danielthecoder Thank you both. I'm working with the team to get more info on this. In the meantime, can you both please confirm:
1) Do your DNS settings seem to be correctly configured?
2) Is this happening with any other browsers, specifically Chromium-based ones?
Fawkes (they/them)
Project & Community Manager - Microsoft Edge- We have the same problem with Chrome Dev (Chromium 82.*) on multiple machines.
Seems like there is a change with Chromium 82.* which causes this problem.
In addition, websites which are hosted inside the corporate network are working. Websites outside the coorparte network are having this problem, like azure.com.
