- Check the date on your system.
- Clear browser data.
- Clear your SSL status.
- Disable QUIC protocol in Chrome.
- Check your antivirus settings.
- Check your firewall.
- Disable extensions.
- Adjust the level of security and privacy on the Internet.
April 10, 2018Jason Parms
Are you using Google Chrome to browse the web? That’s cool! Most other internet users are happy with the smooth user experience. However, sometimes you may encounter an SSL security error. This website cannot provide a secure connection – ERR_SSL_PROTOCOL_ERROR – when browsing SSL-protected websites in Google Chrome browser.
Now this error often goes away on its own every time you refresh the page, but sometimes it keeps showing up. When such warnings occur, various solutions to fix “ERR_SSL_PROTOCOL_ERROR” are explained here.
Why Are You Getting ERR_SSL_PROTOCOL_ERROR?
Well, we cannot connect our system to yours, and we cannot understand why. We can tell you several reasons that may cause this problem. There may even be multiple reasons to team up to let yourself down.
These issues range from incorrect date and time to firewall blocking your browser extension. It can literally be anything. In most cases, this error occurs anddue to server problems. But you’re not for diagnostics, are you? Here is a list of medications that you should try one by one until one works.
So take one pill at a time and watch what happens. If the problem persists, call us in the morning.
Chrome Quick Fix Guide: “This Site Cannot Provide A Secure Connection” Or “ERR_SSL_PROTOCOL_ERROR”.
If Google Chrome is your gateway to the world of the Internet, you must have encountered the “This website cannot connect securely” error or ERR_SSL_PROTOCOL_ERROR message at least once. The frustration with this bug (actually a family of bugs) is that most of the time it’s not easy to determine the cause behind it. SSL errors can appear on the most popular and fewer websites. Heck, I have one here on our website and I can assure you that our SSL / TLS setup is great.
As we just said, since Google sometimes says, “This website can’t provide a secure connection,” it’s almost impossible to boil it down to one reason. It could be that goodBut, from something as trivial as an incorrect system date to much more convoluted server problems, it can be almost anything.
Set aside the diagnostic part for a while and focus on what you have to treat.
Here is a quick troubleshooting guide to fix ERR_SSL_PROTOCOL_ERROR in Google Chrome. If one doesn’t work, try the next one. Sooner or later, you will be able to get rid of this problem.
Correct ERR_SSL_PROTOCOL_ERROR With Correct Date And Time
Sounds too obvious, doesn’t it? Well, in most cases, the simplest solution to the problem is the correct one. In this case, incorrect date and time settings can cause problems. So make sure your system keeps up andnot ahead of time.
Why is this a problem? The validity of certificates is an extremely important factor in the authentication process. This means that you must keep a close eye on when the certificate was signed and when it will expire. If your system has date and time issues, it can lead to all sorts of authentication issues. These browsers are built for security, so something as simple as a bad timing can cause an SSL connection to fail.
Fix ERR_SSL_PROTOCOL_ERROR By Removing Browsing Data From Chrome
From one obvious solution to the next.
If you already have the correct date and time, you need to clear your Chrome cache and cookies. To do this, press Ctrl Shift Delete and delete the browsing data. While this does not fix the “This site cannot securely connect” error, we recommend that you periodically clear your browsing data.
Fix ERR_SSL_PROTOCOL_ERROR By Clearing Your SSL Status
If none of the above methods work, the next thing you should try is clearing your SSL status. To do this, do the followinge actions:
- First, go to the Personalize and Control Google Chrome section, the three dots you see just below the X (close) button.
- Now click on “Settings”.
- Scroll down the page and open advanced settings.
- Go to the Open Proxy Settings section by scrolling down or in the search bar.
- A window titled “Internet Properties” will open.
- Go to the content pane and click the Clear SSL Status button.
Fix ERR_SSL_PROTOCOL_ERROR By Disabling QUIC Protocol
QUIC (Quick UDP Internet Connections) provides a TLS / SSL equivalent to Google servers. By default, the QUIC protocol is enabled in Chrome. To disable it, copy chrome: // flags / # enable-quic and paste it into the address bar. Press the Enter key. At the top of the screen, the QUIC experimental protocol is set by default. Disable it and restart Chrome.
We don’t necessarily recommend it, but it has been shown to work in some dark cases, so let’s list it.
Fix ERR_SSL_PROTOCOL_ERROR By Checking Your Antivirus Settings
Warning nie. This step is not completely secure as it allows the use of the old and insecure SSL / TLS protocols still in use on some websites.
You may not know this, but your antivirus software will monitor the web pages you visit and protect you from potential threats. For this, the SSL / TLS protocol used by the website is checked. If you find that the journal is insecure and out of date, you will no longer be able to visit this site.
There is no specific method to change the settings of all antivirus software as the user interface and settings differ from software to software. You need to know if SSL protocols are being scanned. If so, turn it off and see what happens. If the problem persists, go back to the original settings.
Editor’s Note: Usually antivirus triggers an alarm on SSL / TLS connections because the server is trying to negotiate a connection with an outdated or vulnerable version of SSL or TLS such as SSL 3.0 andwhether TLS 1.0. As we wrote in similar tips, don’t change your antivirus or lower your TLS version settings to accommodate a website’s SSL / TLS misconfiguration. The risks far outweigh the opportunities.
Fix ERR_SSL_PROTOCOL_ERROR To Enable All SSL / TLS Versions – Last Resort
Warning. This step is not completely secure as it allows the use of the old and insecure SSL / TLS protocols still in use on some websites.
When you visit an SSL-compliant website, SSL / TLS is used to communicate with the server. Sometimes the SSL / TLS version of the website might not be compatible with your version of Chrome, as Chrome doesn’t allow legacy SSL / TLS protocols to run by default. Therefore, you must change these SSL / TLS settings. Here’s how to do it:
- Click on the three dots in the upper right corner of Chrome and select “Settings.”
- Now scroll down and go to advanced settings.
- Find proxy settings and open it.
- Click Advanced
- Scroll down until you see See section “Security”. Now make sure you have checked all SSL and TLS versions.
- Click Apply.
- Restart Chrome.
Editor’s note. Consider this proposal purely academic. All major browsers have announced their intention to disable support for all previous versions of TLS except TLS 1.2 and the recently released TLS 1.3. This is for security reasons. Do not enable support for legacy TLS and SSL versions with known security vulnerabilities. No legitimate organization will ask you to violate your browser’s security settings in order to interact with their website.
We hope this guide helped you troubleshoot errors related to ERR_SSL_PROTOCOL_ERROR or “This website cannot connect securely” messages in Chrome. If not, please share your concerns in the comments section and we’ll try.