Fix ERR_SSL_PROTOCOL_ERROR in Chrome: 9 Working Solutions

You try to open a website, and Chrome stops you with ERR_SSL_PROTOCOL_ERROR. This means Chrome could not set up a safe, private connection to the site. Most of the time the problem is on your end, and you can fix it in a few minutes. Work through the steps below in order and stop when the page loads.

What ERR_SSL_PROTOCOL_ERROR Means

When you visit a secure site, your browser and the website agree on a shared code to keep the connection private. If that handshake fails, Chrome shows this error instead of the page. A wrong clock, old cached data, a browser setting, or security software are the usual causes.

How to Fix ERR_SSL_PROTOCOL_ERROR

1. Reload the page. Press the refresh icon or hit Ctrl + R (or Cmd + R on a Mac). A one-time glitch often clears on the second try.
2. Check your date and time. A clock that is off by even a few minutes breaks the security check. Set your device to update the date and time automatically, then reload the page.
3. Try Incognito mode. Open a new Incognito window with Ctrl + Shift + N and visit the site. If it loads there, an extension or your cache is the problem, so keep going.
4. Clear your cache and cookies. Go to Settings, then Privacy and security, then Delete browsing data. Pick Cookies and other site data and Cached images and files, then click Delete data.
5. Clear the SSL state. Old security data can get stuck. Delete your cached files and cookies as in the step above, then close and reopen Chrome so it rebuilds a fresh secure connection.

Note: Flags are experimental features and can make Chrome unstable. If Chrome behaves unexpectedly after changing a flag, return to chrome://flags and click Reset all.

6. Turn off the QUIC protocol. Type chrome://flags in the address bar and press Enter. Search for QUIC, set Experimental QUIC protocol to Disabled, then click Relaunch. If you cannot find this flag, your version of Chrome may have removed it, so skip to the next step.
7. Turn off your extensions. Go to chrome://extensions and switch them all off, then reload the page. If it works, turn them back on one at a time to find the bad one.

Note: Only turn off your antivirus or firewall for a quick test, and turn it back on right after.

8. Check your antivirus, firewall, or VPN. Some security tools scan secure traffic and can trip this error. Turn off HTTPS or SSL scanning, or pause your VPN, then reload the page. Turn your protection back on when you are done.
9. Reset Chrome settings. Go to Settings, then Reset settings, then Restore settings to their original defaults. This clears bad settings without deleting your bookmarks or passwords.

Good to Know

• If only one website shows the error but every other site works, the problem is likely on that site, not your browser. Try again later.
• Test the same page in another browser like Edge or Firefox. If it fails everywhere, the issue is your network or the site itself.

ERR_SSL_PROTOCOL_ERROR looks scary, but it usually points to a small fix like a wrong clock, stale cache, or one setting. Start at the top of the list, and you will likely be back on the page within a couple of minutes.