ERR_SSL_PROTOCOL_ERROR appears when Chrome cannot complete the secure HTTPS handshake with a website. The browser and server fail to agree on a usable encrypted connection, often because of a wrong system clock, cached security state, browser extension, antivirus HTTPS scanning, or a network policy.
Does this affect you?
Use this for Chrome, Edge, and other Chromium browsers on Windows, Mac, or Chromebook when the page says it cannot provide a secure connection and shows ERR_SSL_PROTOCOL_ERROR. Similar secure-connection warnings in Firefox usually respond to the same clock, security software, and network checks.
Check your system date and time
A wrong clock can make valid certificates look expired or not yet valid.
- On Windows, right-click the taskbar clock and choose Adjust date/time. Turn on Set time automatically and, if available, Set time zone automatically.
- On Mac, open System Settings > General > Date & Time and enable automatic date and time.
- Compare the computer time against your phone. If it is off, let the computer sync.
- Restart Chrome and reload the site.
Clear SSL state and browsing data
Cached site data or an old security record can keep the same secure connection failure returning.
- In Chrome, open Settings > Privacy and security > Delete browsing data.
- Set the time range to All time.
- Select Cookies and other site data plus Cached images and files.
- Clear the data.
- On Windows, open Internet Options, go to the Content tab, click Clear SSL state, and confirm.
- Restart Chrome completely and try again.
Rule out antivirus HTTPS scanning and extensions
Traffic inspection tools can break encrypted connections while trying to scan them.
- Open your antivirus or security suite.
- Find HTTPS scanning, SSL scanning, Web protection, or a similar feature and turn it off briefly for testing.
- Reload the site. If it works, update the security software or add an exception before deciding whether to leave that feature off.
- Open an Incognito window with Ctrl+Shift+N or Cmd+Shift+N.
- If the site works there, disable extensions from chrome://extensions and re-enable them one at a time.
More control
Check TLS settings on older Windows systems
Open Internet Options > Advanced and make sure Use TLS 1.2 is enabled while old protocols such as SSL 3.0 are not. Windows 11 may also show TLS 1.3. Apply changes and restart the browser.
Managed networks may intercept HTTPS
Work and school networks sometimes inspect HTTPS traffic intentionally. If the problem happens only there and not at home, ask IT to check the policy or certificate setup.
The site can still be at fault
If the same site fails on several devices and networks, its SSL certificate or server configuration may be broken. In that case, wait or contact the site owner.
Sources
- Google Chrome Help – Fix connection errors (2025)
- Chromium Project – Net error list documentation (2025)
- Microsoft Support – Troubleshoot certificate errors in Microsoft Edge (2025)