Fix ERR_SSL_PROTOCOL_ERROR in Chrome in 3 Steps

What Actually Causes ERR_SSL_PROTOCOL_ERROR

This error pops up when Chrome and the server can't agree on a secure handshake. The culprit is almost always one of three things: your system clock is wrong, the SSL cache is corrupted, or your antivirus is intercepting the connection. I've seen this on Windows 10, 11, macOS, and Linux. It happens most often after a time change (daylight saving) or after an antivirus update.

Don't bother reinstalling Chrome — that's overkill. The fix is simpler. Start with Step 1, it takes 30 seconds.

Step 1: Check Your System Clock (30 seconds)

Chrome uses your computer's time to validate SSL certificates. If your clock is off by more than a few minutes, certificates look expired or invalid. This is the #1 cause of ERR_SSL_PROTOCOL_ERROR.

Windows 10 / 11

1. Right-click the clock in the taskbar and select Adjust date/time.
2. Toggle Set time automatically to On, then Sync now.
3. If it still fails, toggle off automatic time, set it manually to the correct time, then toggle it back on. This forces a fresh sync with time.windows.com.

macOS

1. Open System Settings > General > Date & Time.
2. Enable Set date and time automatically. Use time.apple.com.

Linux (Ubuntu/Debian)

sudo timedatectl set-ntp true
sudo timedatectl status

Wait 10 seconds, then restart Chrome and try the site again. If it works, you're done. Don't move to Step 2 unless the error persists.

Step 2: Clear SSL Cache (5 minutes)

If the clock was fine, the next suspect is a corrupted SSL session cache. Chrome stores SSL session data locally to speed up handshakes. Sometimes that data gets stale or corrupt. Clearing it forces a fresh handshake.

Clear SSL State on Windows

1. Open Control Panel > Internet Options (yes, that's the old Internet Explorer settings — still controls Chrome's SSL cache).
2. Go to the Content tab.
3. Under Certificates, click Clear SSL state.
4. Click OK. Restart Chrome.

Clear Chrome's Internal Cache (All OS)

1. In Chrome, type chrome://net-internals/#hsts in the address bar.
2. Scroll down to Delete domain security policies and type the domain you're having trouble with (e.g., google.com). Click Delete.
3. Then go to chrome://net-internals/#sockets and click Flush socket pools.

Test the site again. If it works, stop here. If not, move to Step 3.

Step 3: Disable Antivirus HTTPS Scanning (15+ minutes)

This is the annoying one. Most modern antivirus software (Norton, McAfee, Bitdefender, Avast, even Windows Defender's tamper protection sometimes) intercepts HTTPS traffic to scan it. They install their own root certificate, which Chrome doesn't always trust. This causes the SSL protocol error.

How to test if your AV is the problem

Before you uninstall anything, temporarily disable the HTTPS scanning feature:

• Bitdefender: Settings > Protection > Online Threat Prevention > Toggle off Scan SSL.
• Norton 360: Settings > Firewall > SSL Inspection > Turn off.
• Avast: Protection > Core Shields > Web Shield > Enable Scan HTTPS connections — toggle it off (and confirm the warning).
• Kaspersky: Settings > Additional > Network > Do not scan encrypted connections.
• Windows Defender: Usually not the culprit, but if you have tamper protection on, turn it off temporarily. Go to Windows Security > Device Security > Core Isolation > Memory Integrity — turn off, reboot.

If the error disappears after disabling, you have two options:

1. Keep HTTPS scanning off (I do this — I've never seen it catch a real threat that Defender wouldn't).
2. Re-enable it and add the problematic domain to the exclusion list in your AV settings. But that's a whack-a-mole approach.

If none of these steps work, the problem is likely on the server side — the site's SSL certificate is expired or misconfigured. You can verify using SSL Labs. But 95% of the time, it's one of the three things above.

What NOT to Do

• Don't reinstall Chrome. It doesn't touch the SSL cache or your system clock.
• Don't mess with Chrome flags like --ignore-certificate-errors. That disables security entirely and is a bad habit.
• Don't clear all browsing data unless you're desperate. You'll lose passwords and history for no reason.

Stick to the order above. Step 1 fixes half the cases. Step 2 fixes another quarter. Step 3 catches the rest. You'll be back online in under 20 minutes.