sodcalculator

10 Tech How-To

SSL Certificate Error Google Chrome Fix

Guide 10-49226 · Updated · Step by step

If you’re seeing an SSL certificate error in Google Chrome, it means the site’s security certificate is invalid, expired, or doesn’t match the domain, and the fix usually involves updating your system date, clearing browser data, or checking the site’s certificate details. Most of these errors are safe to resolve yourself in a few minutes, but some require caution because they can signal a phishing attempt. Below are the specific steps to fix the most common SSL certificate errors in Chrome, along with explanations of what each error means and when to be wary.

What SSL Certificate Errors Look Like in Chrome

Chrome displays a full-page warning (often with a red padlock or “Not secure” label) instead of loading the site. Common messages include:

  • NET::ERR_CERT_DATE_INVALID – the certificate is expired or the system date is wrong.
  • NET::ERR_CERT_AUTHORITY_INVALID – the certificate issuer isn’t trusted by your browser.
  • NET::ERR_CERT_COMMON_NAME_INVALID – the certificate doesn’t match the site’s address.
  • NET::ERR_CERT_REVOKED – the certificate has been revoked by the issuer.

Each error has a different cause, but the fixes overlap. Start with the simplest and most common solutions below.

Fix 1: Check Your System Date and Time

The most frequent cause of SSL errors is an incorrect date or time on your device. If your clock is off by even a few minutes, Chrome can’t verify the certificate’s validity period.

  1. On Windows: right-click the clock in the taskbar → “Adjust date/time” → toggle “Set time automatically” on.
  2. On macOS: System Settings → General → Date & Time → enable “Set time and date automatically”.
  3. On Android: Settings → System → Date & time → enable “Automatic date & time”.
  4. On iPhone/iPad: Settings → General → Date & Time → enable “Set Automatically”.

After correcting the time, restart Chrome and try the site again. If the error persists, move to the next fix.

Fix 2: Clear Chrome’s SSL State and Cache

Sometimes Chrome caches an old or corrupted certificate. Clearing the SSL state and browsing data forces Chrome to re-fetch the certificate.

  1. In Chrome, go to Settings → Privacy and security → Security.
  2. Scroll to “Advanced” and click “Manage certificates” (on Windows) or “Manage device certificates” (on Mac).
  3. In the certificate manager, look for a tab like “Trusted Root Certification Authorities” and remove any suspicious entries (but don’t delete standard ones like DigiCert or GlobalSign unless you’re sure).
  4. Go back to Settings → Privacy and security → Clear browsing data.
  5. Select “Cached images and files” and “Cookies and other site data”, then click “Clear data”.

This often resolves errors caused by a stale certificate store. If you’re on a managed work or school device, you may need to contact your IT admin instead.

Fix 3: Check the Site’s Certificate Manually

If the error persists, you can inspect the certificate to see exactly what’s wrong. This also helps you decide whether it’s safe to proceed.

  1. Click the padlock icon (or “Not secure” text) in the address bar.
  2. Click “Connection is secure” (or “Certificate is not valid”).
  3. Click “Certificate is valid” (or “Certificate information”) to open the details.

Look for:

  • Issued to: should match the domain you’re visiting.
  • Valid from / to: should include today’s date.
  • Issued by: should be a known certificate authority (like Let’s Encrypt, DigiCert, Comodo).

If the certificate is expired, the site owner needs to renew it – you can’t fix that from your side. If the certificate is for a different domain, you might be on a phishing site, so leave immediately.

Fix 4: Disable Chrome Extensions That Interfere

Some extensions (especially security or VPN extensions) can intercept HTTPS traffic and cause SSL errors. To test:

  1. Click the three-dot menu → More tools → Extensions.
  2. Toggle off all extensions, then try the site again.
  3. If the site loads, re-enable extensions one by one to find the culprit.

Also, check if you’re using a VPN or a proxy – these can sometimes present their own certificates. Disconnect and try again.

Fix 5: Update Chrome and Your Operating System

Outdated browsers and OSes may not recognize newer certificate authorities or security protocols. Chrome updates automatically, but you can force it:

  1. Click the three-dot menu → Help → About Google Chrome.
  2. Chrome will check for updates and install them automatically.
  3. Relaunch Chrome.

Also check for OS updates: Windows Update, macOS Software Update, or your phone’s system update. These often include root certificate updates.

When to Be Cautious: Proceed at Your Own Risk

Chrome allows you to click “Advanced” and then “Proceed to [site] (unsafe)” to bypass the warning. Only do this if you’re absolutely sure the site is legitimate – for example, if you’re on a corporate intranet or a test server you control. If you see this warning on a banking site, an email link, or a site you’ve never visited, close the tab immediately. A valid SSL certificate is the foundation of secure HTTPS; ignoring the warning could expose your passwords or payment details to a man-in-the-middle attacker.

Also note that some legitimate sites have misconfigured certificates (e.g., missing intermediate certificates). In that case, the site owner must fix it – you can’t resolve it on your end. You can report the issue to the site’s support team.

Frequently Asked Questions

Why does Chrome keep saying my connection is not private?

This is Chrome’s generic message for any SSL certificate error. It appears when the certificate is invalid, expired, or not trusted. The fixes above address the most common causes, but if it happens on every site, check your system date, clear your SSL cache, or scan for malware that might be intercepting your traffic.

Can I permanently ignore SSL errors in Chrome?

No, Chrome intentionally doesn’t allow you to permanently ignore SSL errors for all sites. You can bypass the warning for a single session by clicking “Advanced” → “Proceed”, but Chrome will warn again next time. This is a security feature to protect you from malicious sites.

What does NET::ERR_CERT_AUTHORITY_INVALID mean?

It means the certificate was issued by an authority that Chrome doesn’t trust. This can happen if you’re using a corporate proxy that injects its own certificate, or if the site’s certificate chain is incomplete. If you’re at work, contact your IT department; if it’s a public site, avoid proceeding.

Does clearing cookies fix SSL errors?

Clearing cookies and cached files can help if the error is caused by a corrupted cached certificate or a redirect issue. It’s a common step in the troubleshooting process, but it’s not a guaranteed fix for all SSL errors.

Is it safe to click “Proceed to site”?

Only if you’re certain the site is legitimate. If you typed the address manually or have used the site before without issues, it might be a temporary glitch. But if you arrived via a link in an email or a pop-up, treat it as a red flag and leave.

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 →