{"id":291,"date":"2019-07-18T15:41:48","date_gmt":"2019-07-18T15:41:48","guid":{"rendered":"https:\/\/www.rapidsslonline.com\/ssl\/?p=291"},"modified":"2022-03-28T06:53:32","modified_gmt":"2022-03-28T06:53:32","slug":"fix-err-ssl-version-interference-google-chrome","status":"publish","type":"post","link":"https:\/\/www.rapidsslonline.com\/ssl\/fix-err-ssl-version-interference-google-chrome\/","title":{"rendered":"How to Fix ‘ERR SSL VERSION INTERFERENCE’ in Google Chrome"},"content":{"rendered":"\n

What causes the \u201cThis site can\u2019t be reached\u201d Chrome error & how you can fix it<\/h2>\n\n\n\n

The internet is full of many things: cat videos,\npornography, questionable social media posts, and bad advice. Lots and lots of\nbad advice. Anytime you search for help with a browser error, you\u2019re bound to\nwade into a pool that\u2019s waist deep with highly-optimized SEO content that\ndoesn\u2019t actually answer the question properly. Or, if it does, but it then\noffers egregious advice on working around it. <\/p>\n\n\n\n

The Google Chrome ERR_SSL_VERSION_INTERFERENCE (sometimes written “ERR SSL VERSION INTERFERENCE”) is a perfect example of this. Most of these garbage answers start off with some keyword stuffed boiler plate language about how common SSL errors are. <\/p>\n\n\n\n

Shade aside, there aren\u2019t \u201cmany reasons\u201d for this problem. There\u2019s one reason only. And, aside from adjusting their protocol version support, there\u2019s nothing that a user could responsibly<\/em> do to solve this problem. Advising anything else is patently irresponsible and should be punishable by flogging. <\/p>\n\n\n\n

Why \u201cERR SSL VERSION INTERFERENCE\u201d Appears in Chrome<\/h2>\n\n\n\n

The reason you get the \u201cERR_SSL_VERSION_INTERFERENCE\u201d in\nChrome is that the website you\u2019re attempting to visit doesn\u2019t support a\nmutually agreeable TLS\nprotocol version<\/a>. The most common iteration is one of you \u2014 either as the\nclient or the server \u2014 is exclusively supporting TLS 1.3 and the other doesn\u2019t\nsupport it at all.<\/p>\n\n\n\n

TLS 1.3 is not backward compatible<\/a> with former versions of the protocol. While this may initially seem like an oversight, it\u2019s done quite a on purpose. Older versions are susceptible to oracle padding and downgrade attacks. The vast majority of the internet is still using TLS 1.2, but about 35-40% of the Alexa Top 100,000<\/a> have begun supporting TLS 1.3. The smart move would be to support both 1.2 and 1.3 until the latter achieves the right degree of proliferation.<\/p>\n\n\n\n

Unfortunately, some sites have already turned off support\nfor 1.2 in favor of 1.3. For most modern browsers, this won\u2019t be an issue. But\nif you\u2019re running an older version, or you don\u2019t have support for 1.3 activated\non your OS, you could run into this problem.<\/p>\n\n\n\n

Fixing ERR_SSL_VERSION_INTERFERENCE for Web Users<\/h2>\n\n\n\n

Provided your browser supports TLS 1.3 and TLS 1.2 \u2014 and\nwith Chrome, that\u2019s actually a decision made on the OS level \u2014 there\u2019s not\nanything you can do to fix this beside contacting the site owner. Some of the\nbad advice you might see with regard to solving this from the client side\nincludes:<\/p>\n\n\n\n