ERR_SSL_PROTOCOL_ERROR Fix in Chrome

This guide walks you through the most common causes of the ERR_SSL_PROTOCOL_ERROR in Chrome and shows you how to fix them. You’ll learn to check your system clock, clear SSL state, disable problematic extensions, and more—usually resolving the issue in under 10 minutes.

What You’ll Need

Access to Chrome’s settings and developer tools
Administrator rights on your computer (for some steps)
Your router login credentials (if you need to restart it)

Step-by-Step

Check your system date and time. SSL certificates are only valid for a specific time window. If your computer’s clock is off by even a few minutes, Chrome will reject the certificate. Right-click the clock in your taskbar (Windows) or go to System Settings > Date & Time (Mac), and enable automatic time and timezone. If it’s already automatic, toggle it off and on again, then restart Chrome.
Clear Chrome’s SSL cache. Chrome stores SSL certificate data to speed up connections, but corrupted data can trigger this error. Go to Chrome Settings > Privacy and security > Security. Scroll down to “Advanced” and click “Manage certificates.” In the window that opens, go to the “Trusted Root Certification Authorities” tab, select any certificates from the site you’re visiting (or all of them if you’re unsure), and click “Remove.” Then restart Chrome. (This is safe—Chrome will re-download valid certificates as needed.)
Disable QUIC protocol. QUIC is a newer network protocol that Chrome uses by default, but some servers or firewalls don’t handle it well. Type chrome://flags in the address bar and press Enter. Use the search box to find “Experimental QUIC protocol,” set it to “Disabled,” and click “Relaunch” at the bottom.
Turn off your VPN or proxy. VPNs and proxy services can interfere with SSL handshakes. Temporarily disconnect from your VPN and try the site again. If it works, re-enable your VPN and switch to a different server. For proxy settings, go to Chrome Settings > System > Open your computer’s proxy settings. Make sure “Use a proxy server” is off (Windows) or the proxy is set to “Off” (Mac).
Disable Chrome extensions. Extensions can modify network requests and cause SSL errors. Type chrome://extensions in the address bar. Toggle off all extensions, then restart Chrome and try the site. If it loads, re-enable extensions one by one to find the culprit. Pay special attention to ad blockers, security tools, and VPN extensions.
Clear Chrome’s cache and cookies. Corrupted cached data can cause SSL errors. Go to Chrome Settings > Privacy and security > Clear browsing data. Select “All time” as the time range, check “Cookies and other site data” and “Cached images and files,” then click “Clear data.” Restart Chrome.
Check your antivirus or firewall. Some security software performs SSL scanning, which can break connections. Temporarily disable your antivirus’s web protection (or the entire software) and try the site. If it works, add an exception for the site or switch to a different antivirus. Remember to re-enable your antivirus afterward.
Reset Chrome settings. If nothing else works, reset Chrome to its default state. Go to Chrome Settings > Advanced > Reset and clean up > Restore settings to their original defaults. This will disable extensions, clear temporary data, and reset settings—but won’t delete your bookmarks or passwords.
Restart your router. A router with corrupted DNS or connection state can cause SSL errors. Unplug your router, wait 30 seconds, plug it back in, and wait for it to fully restart. Then try the site again.
Try another browser or device. If the error persists, test the site in Firefox, Edge, or on your phone. If it works there, the problem is Chrome-specific. If it fails everywhere, the issue is likely on the website’s server or your network.

Common Mistakes

Skipping the clock check. This is the most common cause, yet many people jump straight to clearing caches. Always check the date and time first.
Disabling all extensions permanently. You don’t need to keep them off—just identify the bad one and remove or update it.
Clearing SSL state too aggressively. Removing all trusted root certificates can break other sites. Only remove certificates related to the site you’re having trouble with.
Forgetting to restart Chrome after changes. Most fixes require a full restart (close all Chrome windows and reopen). Using the “Relaunch” button in chrome://flags is the easiest way.

Tips

Use Chrome’s Incognito mode to test if the issue is caused by extensions or cached data. If the site loads in Incognito, the problem is likely an extension or cache.
Check if the website itself is down using a service like Down For Everyone Or Just Me (downforeveryoneorjustme.com). If it’s down, the error isn’t on your end.
Keep Chrome updated. Go to Chrome Settings > About Chrome to see if an update is pending. Updates often fix SSL-related bugs.
If you’re on a corporate network, the error might be caused by your company’s security policies. Contact your IT department.

Troubleshooting

If you’ve tried all the steps and still see the error, here are additional things to check:

Check the URL. Make sure you’re using the correct domain (e.g., https://example.com not https://www.example.com if the site’s certificate only covers one). Try adding or removing “www.”
Look at the certificate details. Click the padlock icon in the address bar (if there is one) or use the developer tools (F12) > Security tab to see the certificate’s validity. If it’s expired, the site owner needs to renew it—you can’t fix that.
Try a different network. Connect to your phone’s hotspot or a public Wi-Fi. If the site loads, the problem is your home network or ISP.
Flush your DNS cache. Open Command Prompt (Windows) or Terminal (Mac) and type ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (Mac). Then restart Chrome.
Reinstall Chrome. As a last resort, uninstall Chrome completely (back up your bookmarks first) and download a fresh copy from Google’s official site. This will clear all settings and data.

Frequently Asked Questions

What does ERR_SSL_PROTOCOL_ERROR mean?

It means Chrome couldn’t establish a secure connection with the website because the SSL/TLS handshake failed. This can be due to mismatched security protocols, incorrect time settings, or interference from software.

Will clearing my SSL cache delete my passwords?

No. Clearing the SSL cache only removes certificate data. Your passwords and other saved data are stored separately and won’t be affected.

Why does this error happen on only one website?

If it’s site-specific, the problem is likely on the website’s server—maybe their SSL certificate is expired or misconfigured. You can check the certificate’s details using the developer tools.

Can I ignore this error and continue?

No. Continuing past an SSL error means your connection isn’t encrypted, and your data could be intercepted. Always fix the error or avoid the site.

Does this error mean my computer is hacked?

Not necessarily. It’s usually a configuration issue. However, if you see the error on multiple sites and none of the fixes work, it’s worth running a malware scan as a precaution.

How do I update Chrome to fix SSL errors?

Go to Chrome Settings > About Chrome. Chrome will automatically check for updates and install them. If an update is available, click “Relaunch” to apply it.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →