Edge 124 - Cannot access to website due to ERR_SSL_PROTOCOL_ERROR or ERR_CONNECTION_CLOSED

Question

Hi Team,

Since the release of Edge 124, our users have been unable to access the website due to ERR_CONNECTION_CLOSED or ERR_SSL_PROTOCOL_ERROR. After searching, we knew it could be figured out by disabling the TLS 1.3 hybridized Kyber support setting at edge://flags/.

Due to all our PCs being managed by Intune, it's very hard for us to change the settings for users one by one on their PCs locally. Do you have any Intune setting, Powershell script or registry key regarding the setting of TLS 1.3 hybridized Kyber support? Then we could apply the policy of this setting to all the PCs.

Thank you.

Answer 1

It can be done with Edge Administrative templates by using this setting:

Policy:

Computer Configuration > Policies > Administrative Templates > Microsoft Edge> Enable post-quantum key agreement for TLS > Disabled

Intune:

Administrative Templates > Microsoft Edge> Enable post-quantum key agreement for TLS > Disabled

See: https://www.reddit.com/r/sysadmin/comments/1carvpd/chrome_124_breaks_tls_handshake/

Answer 2

Simply disabling the #enable-tls13-kyber flag in Edge doesn't solve it for us.

We use Fortigate firewalls, and I have to completely disable SSL Deep Inspection on the appropriate firewall policies. I created a case with Fortinet Support and I'm awaiting their feedback.