Here\u2019s a quick, troubleshooting guide to fix ERR_SSL_PROTOCOL_ERROR on Google Chrome. If one doesn\u2019t work, try the next one. Sooner or later, you should be able get rid of this issue.<\/p>\n\n\n\n Sounds too obvious, doesn\u2019t it? Well, most of the time, the simplest solution to a problem is the correct one. In this case, incorrect date & time settings might be causing trouble for you. So, make sure that your system isn\u2019t lagging behind or running ahead.<\/p>\n\n\n\n Related<\/strong>: Secure Your Domain & Sub-Domains with a RapidSSL Wildcard Certificate<\/a>.<\/em><\/p>\n\n\n\n Why is this a problem? Certificate validity is an extremely important factor in the authentication process, and that means keeping very specific tabs on the time the certificate was signed and when it will expire. If there is an issue with your system’s time and date, it can cause all kinds of problems during authentication. These browsers are designed to err on the side of caution, which is why something as simple as having the wrong time can cause an SSL connection error.<\/p>\n\n\n\n From one obvious solution to another.<\/p>\n\n\n\n If you already have the correct date & time, it\u2019s time to clear Chrome\u2019s cache and cookies. To do so, press Ctrl + Shift + Delete<\/strong> and erase your browsing data. Even if this hasn’t fixed the “This site can\u2019t provide a secure connection” error, we recommend clearing your browsing data on a regular basis.<\/p>\n\n\n\n If neither of the above works, clearing your SSL State is the next thing you should try. Follow the steps below to do so:<\/p>\n\n\n\n QUIC (Quick UDP Internet Connections) provides a TLS\/SSL equivalent connection to Google’s servers. By default, the QUIC protocol is enabled in Chrome. To disable it, copy chrome:\/\/flags\/#enable-quic <\/strong>and paste it into the address bar, hit enter. On top of your screen, the Experimental QUIC Protocol <\/strong>would have been set as Default<\/strong>. Disable it and relaunch Chrome.<\/p>\n\n\n\n We don’t necessarily advise this, but it’s been proven to work in some obscure cases so we’re putting it on the list.<\/p>\n\n\n\n Warning: <\/strong>This step isn’t entirely safe as it allows the older, insecure SSL\/TLS protocols that some of the websites still use.<\/em><\/p>\n\n\n\n You might not know this, but your Antivirus software keeps an eye on the web pages you visit and protects you against any threats they may pose or contain. It does this by checking the SSL\/TLS protocol a website uses. Upon finding the protocol to be unsafe and outdated, it prevents you from visiting the site.<\/p>\n\n\n\n There isn\u2019t any one particular way to change the settings for all Antivirus software as the UI and settings differ from one software to another. You\u2019d have to find and see if it\u2019s scanning the SSL protocols. If it does, disable it and see what happens. If the problem persists, revert to the original settings.<\/p>\n\n\n\n Editor’s Note:<\/strong> Generally, the reason you will see an antivirus program cause alarm about an SSL\/TLS connection is because the server is attempting to negotiate a connection using a deprecated or vulnerable SSL or TLS version such a SSL 3.0 or TLS 1.0<\/a>. As we’ve written in similar advice articles, don’t tamper with your antivirus or reduce your TLS version settings to accommodate a website’s bad SSL\/TLS configuration<\/a>. The risks far outweigh the rewards.<\/span> <\/em><\/p>\n\n\n\n Warning: <\/strong>This step isn’t entirely safe as it allows the older, insecure SSL\/TLS protocols that some of the websites still use.<\/em><\/p>\n\n\n\n When you visit an SSL-enabled website, it uses SSL\/TLS protocols to communicate with the server<\/a>. Sometimes, the SSL\/TLS version of a website might not be compatible with your Chrome version as Chrome doesn\u2019t permit deprecated SSL\/TLS protocols to run by default. Therefore, you\u2019d need to change those SSL\/TLS protocol settings. Here\u2019s how you can do it:<\/p>\n\n\n\n Editor’s Note:<\/strong> Again, consider this suggestion entirely academic. The major browsers have all announced plans to disable support for all previous TLS versions, save TLS 1.2<\/a> and the recently-published TLS 1.3<\/a>. This is being done for security reasons. Don’t enable support for outmoded TLS and SSL versions with known vulnerabilities. No legitimate organization will ask you to compromise your browser’s security settings to interact with its website.<\/em><\/span><\/p>\n\n\n\n We hope that this guide has helped you fix ERR_SSL_PROTOCOL_ERROR or “This site can\u2019t provide a secure connection” messages on Chrome. And if it doesn\u2019t, share your concerns in the comments section and we\u2019ll try to help you out with it.<\/p>\n\n\n\n As always, leave any comments or questions below…<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" A quick guide on how to fix Chrome\u2019s \u2018This site can\u2019t provide a secure connection\u2019 or \u2018ERR_SSL_PROTOCOL_ERROR.’ If Google Chrome is your window to the world of the internet, you…<\/p>\n","protected":false},"author":10,"featured_media":5468,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":"","tve_updated_post":"","tve_custom_css":"","tve_user_custom_css":"","tve_globals":{},"tcb2_ready":0,"tcb_editor_enabled":0,"tve_landing_page":"","_tve_header":"","_tve_footer":""},"categories":[130],"tags":[131,155],"class_list":["post-5466","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-everything-encryption","tag-google","tag-google-chrome","post-with-tags"],"views":2106397,"jetpack_featured_media_url":"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2017\/12\/iStock-842883252.jpg","_links":{"self":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/5466","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/comments?post=5466"}],"version-history":[{"count":0,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/5466\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media\/5468"}],"wp:attachment":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media?parent=5466"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/categories?post=5466"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/tags?post=5466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"This](\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2017\/12\/iStock-836755066.jpg\")
<\/figure>\n\n\n\nFix ERR_SSL_PROTOCOL_ERROR by setting the correct Date & Time<\/h2>\n\n\n\n
Fix ERR_SSL_PROTOCOL_ERROR by clearing Chrome\u2019s Browsing Data<\/h2>\n\n\n\n
Fix ERR_SSL_PROTOCOL_ERROR by clearing your SSL State<\/h2>\n\n\n\n
\n
Fix ERR_SSL_PROTOCOL_ERROR by disabling QUIC Protocol<\/h2>\n\n\n\n
Fix ERR_SSL_PROTOCOL_ERROR by checking your Antivirus Settings<\/h2>\n\n\n\n
Fix ERR_SSL_PROTOCOL_ERROR by Enabling all SSL\/TLS Versions \u2013 The Last Resort<\/h2>\n\n\n\n
\n