Because of its high speed and safe, user-friendly layout, Google Chrome is by far the most popular web browser. It does, however, contain several flaws. If you use Chrome as your primary browser, you’ve probably encountered the ‘This site cannot provide a secure connection’ message. The ‘ERR_SSL_PROTOCOL_ERROR is another name for this error.
When you reload the website, the ERR_SSL_PROTOCOL_ERROR problem typically goes away, but if it doesn’t, you’ll have to repair it yourself.
There are a variety of causes for not being able to connect to a server or website, ranging from an incorrect date and time to a lack of client authentication and other complex server issues. While it is normally impossible to pinpoint a single cause, this problem can be resolved by following a set of instructions.
Here’s how to fix the ‘ERR_SSL_PROTOCOL_ERROR‘ in Google Chrome step by step. Try each of these eight approaches one at a time until the problem is fixed.
ERR_SSL_PROTOCOL_ERROR How to Resolve
Some of the most efficient ways to get rid of ERR_SSL_PROTOCOL_ERROR are listed below. Let’s take a look at each one individually.
Method 1: Sync the system date
Having your system date out of sync with the date on the website’s server can cause a slew of issues during login, but don’t panic; this can be simply remedied by updating your system’s date.
You can do this manually or have your system date and time automatically synced with the internet. After that, reload the website, and if the error persists, proceed to the next step.
Method 2: Clearing the browser’s cache
It’s quite easy to clear the cache. To accomplish this;
Step 1: To begin, press Ctrl + Shift + Delete. In the time range area, choose ‘AA range‘.
Step 2: Select the ‘select all‘ option and uncheck the ‘browser history’ checkbox to erase your browsing data but not your browser history. This is done because if the cache is not clear, the CSS modifications will not be reflected.
Even if this solution does not resolve the issue, clearing your browsing data regularly is highly suggested.
Method 3: Delete the host file and restore it to its original state
There are two methods for recovering the host file. The first method requires downloading and installing a host file storage program. This program automatically corrects the problem.
On the other hand, you must manually construct the host file in a second manner. C:WindowsSystem32driversetc is the path to this file. When this file becomes infected, it displays inaccurate data; thus, you must delete it and replace it with the correct code.
Method 4 – Clearing the system’s SSL state
Clearing the system’s SSL state aids in swiftly resolving the problem. To clear the SSL status, go through the following steps:
Step 1: Click the three dots in the top right corner of your screen to access the Google Chrome settings.
Step 2: From the dropdown menu, choose ‘Settings‘. Then, from the advanced dropdown menu that appears as you scroll down, choose ‘System‘.
Step 3: Click ‘Open proxy settings, which will open a new window with ‘Internet Properties‘.
Step 4: Click the ‘Clear SSL State’ button in the Content box.
Reload the website once more. The problem must have been resolved, but if it hasn’t, proceed to the next step.
Method 5: Adjusting the antiviral settings
Antivirus software scans the websites you visit and protects you from sites that may still be employing unsafe SSL/TLS protocols. As a result, this procedure isn’t completely safe because it could lead to you establishing a link with one of these dangerous websites.
Regardless, if you wish to access the website, you can change the antivirus software’s settings. Because these settings differ among antiviruses, there is no one-size-fits-all solution.
In general, examine the antivirus settings and look for the SSL protocol in the ‘advanced options section‘. Check whether the software scans SSL protocols in these settings, and if it does, stop the feature and switch to the ‘Ask about non-visited sites‘ option.
To see if the problem has been resolved, reload the webpage. If the error persists, move on to the next method.
Remember that if your antivirus has blocked the site, it’s most likely because it employs an insecure SSL protocol, therefore it’s best not to fiddle with the antivirus settings. You can always skip this step and move on to the next.
Method 6: Disabling the QUIC protocol
Quick UDP Internet Connections (QUIC) is an acronym for Quick UDP Internet Connections. QUIC is enabled by default in Chrome and generates a secure connection to the server that is equivalent to TSL/SSL.
It does, however, occasionally clash with the SSL protocol, resulting in the ‘ERR_SSL_PROTOCOL_ERROR’ error message.
To turn it off, put ‘chrome:/flags/#enable-quic’ into the URL bar and hit ‘Enter.’ The ‘Experimental QUIC Protocol’ will most likely be selected as the default choice.
Reload your webpage after disabling this feature. If the error persists, move on to the next method.
Method 7: Changing Internet Security and Privacy Settings
Nowadays, everyone who uses the internet is concerned about the security and privacy of their system. ‘High‘ level security and privacy settings are preferred to secure the system and the information it contains.
However, the SSL connection may be banned as a result of this. The procedure outlined below can be used to modify these settings:
Step 1: Open the Control Panel first. After that, go to the ‘Internet Options‘ page.
Step 2: Select the ‘Security‘ tab and set the security level to ‘medium‘.
Then go to the ‘Privacy’ page and set the privacy setting to ‘medium.’
Step 3: Last but not least, restart the webpage to see if the error has been resolved.
Method 8: Activating all TSL/SSL versions
The SSL/TSL version used by a website to communicate with the server may be incompatible with your Chrome version. You’ll have to alter the settings because Chrome doesn’t support these versions by default.
This approach should only be used as a last resort because it can be dangerous in some instances. Activating all TSL/SSL versions would allow access to sites that use older, less secure SSL protocols, which can be dangerous at times.
Regardless, if you want to activate all versions, follow the steps below:
Step 1: Click the three dots in the top right corner of the screen to access Chrome settings.
Step 2: Go to Chrome’s advanced settings and select the ‘System‘ option. After that, go to the ‘advanced‘ page and select ‘Open Proxy settings‘.
Step 3: Next, go to the ‘Security‘ tab. Select all TLS/SSL versions now.
Step 4: Press the ‘Apply‘ button. Check if the error has been fixed by reloading the webpage.
For security reasons, browsers do not enable support for prior TSL versions. As a result, it’s best to avoid using TSL and SSL versions that are known to be vulnerable to attack.
Begin with the first method and work your way to the next until the problem is solved. Remember the hazards involved with a few actions, and unless you trust the website, it’s best to avoid them.
It is not advisable to put your system’s security at risk to interact with a website, and no legitimate company would expect you to do so.
I hope this article helped resolve your ‘ERR_SSL_PROTOCOL_ERROR‘ or ‘This site can’t provide a secure connection‘ issues.