Fix: “ERR_SSL_PROTOCOL_ERROR” on Windows 11 Chrome Browser

You may encounter the error message “This site cannot provide a secure connection” when you visit websites through the Chrome or Yandex Browser on your Windows 11 PC. The error also mentions “The site sent an invalid response ” and indicate the code ERR_SSL_PROTOCOL_ERROR. The error may also be accompanied by another message “SSL connection error” explaining “Unable to create a secure connection to the server … ” and the code “Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error”. This is to allow users to visit secure sites on the Internet, site owners need to integrate secure SSL (Secure Sockets Layer) certificates on the server. If the website does not have reliable SSL certification, you may encounter an error in your browser.

In most cases, the error is related to the server on which the website itself is located. The fact is that browsers began to warn that the site is on the insecure HTTP protocol, and the site owner neglects the safety of users. It may be that an SSL certificate just flew off the site, and the site owner did not have time to correct it. It should be borne in mind that there are problems when the SSL certificate is reissued and sometimes there are warning errors for users with SSL security. The error is not your fault. If the site worked fine without ERR SSL PROTOCOL ERROR, then come back later.


How to Fix “ERR_SSL_PROTOCOL_ERROR” on Windows 11 Chrome Browser

First of all, look at the address bar of your Windows11 browser, if the address begins with HTTP and does not have a lock icon, then this site is unsafe and you must leave it for your own safety. If the site starts with HTTP s and has a lock icon (this is a secure site), and you get the ERR_SSL_PROTOCOL_ERROR error, then we will try to fix this problem.

1. Delete the Hosts file

There is a hosts file on every version of Windows, and it is a text file that contains a mapping between domain names and IP addresses. Sometimes virus software can modify this file, thereby causing various errors. Deleting this file may fix the ERR_SSL_PROTOCOL_ERROR error.

Press Win + R and enter the path C: \ Windows \ System32 \ drivers \ etc to quickly navigate to the location of the host’s file. Click on the “View” tab at the top and check the “Filename extension” box. Now delete the host’s file, which does not have extensions like .ics, etc. at the end. Restart your PC and check if the error is resolved.

2. Clear SSL

When you connect to a site, your PC asks the website for a certificate, which is checked for security. After the verification is complete, a connection is made to the site, if SSL is secure. This whole process is time-consuming, and the website certificates are stored locally on your computer to speed up the process the second time you connect to the site. These local files can get corrupted, thus causing various SSL errors.

Press Win + R and type inetcpl.cpl to quickly open internet properties. Go to the Content tab and click on Clear SSL. Click OK and restart your browser.

3. Disable QUIC Protocol

QUIC Protocol establishes a connection between two endpoints via UDP. If one of them has problems, then the error code ERR SSL PROTOCOL ERROR will appear in the browser.

Open your browser and enter chrome: // flags / in the address bar . Next, write in the search for Experimental QUIC protocol and disable Disabled on the right. Restart your browser and check if the problem is resolved.

4. Date and time setting

Incorrect date and time can cause the ERR_SSL_PROTOCOL_ERROR error in any browser. Go to Options > Time & Language > Date & Time and set the correct time, date, and region if they are not correct.

You can also try the below methods to fix ERR_SSL_PROTOCOL_ERROR

  1. Disable third-party antivirus and check the error. The problem was seen in NOD32.
  2. If you encounter this problem on all of your computers on the same network, then restarting the routers may solve the problem.
  3. Scan your Windows system with an anti-virus scanner.
  4. Disable all browser extensions, restart your browser and check. (to the address bar chrome: // extensions / for a quick transition).

Leave a Reply