sodcalculator

10 Tech How-To

Fix ERR SSL Protocol Error on Windows

Guide 10-44976 · Updated · Step by step

If you see “ERR_SSL_PROTOCOL_ERROR” in Chrome or Edge on Windows, the browser cannot establish a secure connection to the site you are trying to visit. The fix usually involves checking your system date and time, clearing the SSL state, or disabling a misconfigured antivirus or VPN, and this article walks through those steps in order.

What the Error Means

ERR_SSL_PROTOCOL_ERROR is a Chromium-based browser error (Chrome, Edge, Brave, Opera) that appears when the TLS handshake between your browser and the web server fails. TLS (Transport Layer Security) is the cryptographic protocol that encrypts data between your computer and the site. When the handshake is interrupted or rejected, the browser aborts the connection and shows this error instead of the page.

The error can appear on a single website or on every site you visit. A single-site error usually points to a problem with that site’s certificate or server configuration. A widespread error points to something on your own system: wrong clock, corrupted cached SSL data, an interfering security program, or a network-level filter.

Quick Fixes to Try First

Start with these low-risk steps. They resolve a large share of SSL protocol errors without touching advanced settings.

  1. Check the date and time. Right-click the clock in the taskbar, choose “Adjust date/time,” and turn on “Set time automatically” and “Set time zone automatically.” If the clock is off by even a few minutes, certificate validation fails because the browser compares the certificate’s validity window against your system clock.
  2. Reload the page with a hard refresh. Press Ctrl + Shift + R to bypass the cached version. A stale cached copy of a page can trigger the error after a site updates its certificate.
  3. Try the site in an InPrivate or Incognito window. Press Ctrl + Shift + N in Chrome or Ctrl + Shift + P in Edge. If the site loads there, the problem is tied to your normal profile’s cached data or extensions.
  4. Restart the computer. A simple reboot clears temporary network state and stops background processes that may be interfering with TLS connections.

Clear the SSL State and Browser Cache

Windows stores a cache of certificates and SSL session data. When this cache becomes corrupted, the browser may reject valid certificates. Clearing it forces a fresh handshake.

To clear the Windows SSL cache:

  1. Open the Start menu, type Internet Options, and press Enter.
  2. Go to the Content tab.
  3. Click Clear SSL state.
  4. Click OK, then close the window.

Also clear the browser’s cache and cookies. In Chrome, go to Settings → Privacy and security → Clear browsing data. Select “Cached images and files” and “Cookies and other site data,” then click “Clear data.” In Edge, the path is identical. After clearing, close the browser completely and reopen it.

Disable or Adjust Antivirus and VPN Software

Many antivirus programs include “HTTPS scanning” or “SSL inspection.” This feature intercepts encrypted traffic, decrypts it to scan for threats, then re-encrypts it. If the re-encryption uses an outdated or incorrectly installed certificate, your browser rejects it and shows ERR_SSL_PROTOCOL_ERROR.

To test whether your antivirus is the cause, temporarily disable its web protection or HTTPS scanning feature. The exact menu name varies by product: look for “Web Shield,” “SSL Scanning,” or “Encrypted Connection Scanning” in the settings. If the error disappears, re-enable the feature and update the antivirus program, or add the affected website to its exclusion list.

VPNs and proxy extensions can also break TLS handshakes, especially if they are misconfigured or use an older protocol. Disconnect the VPN and try the site again. If it works, update the VPN client or switch to a different server location.

Reset Chrome or Edge Flags and Extensions

Browser flags are experimental features that can alter TLS behavior. A misconfigured flag, particularly one related to QUIC or TLS 1.3, can cause protocol errors.

To reset Chrome flags:

  1. Type chrome://flags in the address bar and press Enter.
  2. Click Reset all in the top-right corner.
  3. Relaunch the browser.

For Edge, use edge://flags and follow the same steps.

Extensions can also interfere. Disable all extensions by going to the extensions page (chrome://extensions or edge://extensions) and toggling them off one by one. Reload the failing site after each toggle to identify the culprit. Ad blockers and “security” extensions are the most common offenders because they often modify request headers or block certificate chains.

Flush DNS and Reset Network Settings

A corrupted DNS cache or a stuck network stack can prevent your browser from reaching the correct server, which sometimes surfaces as an SSL error.

Open Command Prompt as administrator (right-click Start → “Terminal (Admin)” or “Command Prompt (Admin)”) and run these commands one at a time:

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset
netsh int ip reset

After the last command, restart the computer. The netsh winsock reset command restores the Windows Sockets catalog to a clean state, which fixes many connection-level errors. This does not delete personal files or change your IP address permanently.

Check the Website Itself

Sometimes the problem is not on your side. The website’s SSL certificate may be expired, the server may be misconfigured, or the site may be using an outdated TLS version that your browser no longer supports.

To check the site’s certificate, click the padlock icon next to the address bar (if it appears) and view the certificate details. Look at the “Valid from” and “Valid to” dates. If the certificate is expired, only the site owner can fix it. You can also use an online SSL checker by entering the domain name; these tools report the certificate’s validity, issuer, and chain status.

If the site works in another browser (Firefox, for example) but not in Chrome or Edge, the issue is likely a browser-specific setting or a cached certificate in that browser. If the site fails in all browsers and on other devices (like your phone), the server is almost certainly at fault.

Frequently Asked Questions

Why does ERR_SSL_PROTOCOL_ERROR appear only on one website?

This usually means the website’s certificate is expired, the server is misconfigured, or the site uses an outdated TLS version. Check the certificate’s expiration date and try the site on your phone’s mobile data to confirm whether the problem is server-side.

Is it safe to ignore this error and continue?

No. The error means the browser cannot verify the site’s identity. Continuing past it (if the browser even offers an option) could expose your data to interception. Only proceed if you are absolutely certain the site is legitimate and you understand the risk.

Will resetting Windows fix the SSL protocol error?

Resetting Windows is a last resort and usually unnecessary. The steps above—clearing SSL state, flushing DNS, and disabling antivirus scanning—resolve the vast majority of cases without a full reset. Try those first.

Does this error mean my computer has a virus?

Not necessarily. The most common causes are a wrong system clock, corrupted cache, or antivirus HTTPS scanning. However, some malware does tamper with certificate stores, so if the error persists after all fixes, run a full antivirus scan as a precaution.

Why does the error appear in Chrome but not Firefox?

Chrome and Firefox maintain separate SSL caches and use different certificate stores. Chrome uses the Windows certificate store, while Firefox has its own. Clearing the Windows SSL state and Chrome’s cache usually fixes the Chrome-only issue.

Related

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 →