sodcalculator

10 Tech How-To

Net ERR_CERT_AUTHORITY_INVALID Error in Chrome: Fix

Guide 10-48977 · Updated · Step by step

The “NET::ERR_CERT_AUTHORITY_INVALID” error in Chrome means the website’s security certificate was not issued by a recognized certificate authority (CA), so Chrome cannot verify the site is legitimate. This guide explains why the error appears and walks you through the safe fixes, from checking your system clock to clearing the SSL state.

What This Error Actually Means

Every secure website uses an SSL/TLS certificate to prove its identity and encrypt your connection. That certificate is digitally signed by a certificate authority (CA) — a trusted organization like DigiCert, Let’s Encrypt, or GlobalSign. When you visit a site, Chrome checks the certificate’s signature against its built-in list of trusted CAs. If the signature doesn’t match, the certificate was issued for a different domain, or the certificate chain is incomplete, Chrome blocks the page and shows NET::ERR_CERT_AUTHORITY_INVALID.

This is different from other certificate errors. For example, ERR_CERT_DATE_INVALID means the certificate has expired or the system date is wrong. ERR_CERT_COMMON_NAME_INVALID means the certificate doesn’t match the domain name. The authority error specifically points to the issuer — your browser doesn’t trust who signed the certificate.

Common Causes

  • Incorrect system date or time — a certificate is only valid within a specific date range. If your clock is off by more than a few hours, Chrome can’t verify validity.
  • Missing intermediate certificates — the server may only send its own certificate, not the chain that links it to a trusted root.
  • Corporate or antivirus SSL inspection — security software intercepts encrypted traffic and re-signs it with its own certificate, which your browser doesn’t trust by default.
  • Self-signed certificates — the site’s owner created a certificate without a CA. This is common on internal networks or test servers.
  • Outdated Chrome or operating system — older versions may not recognize newer root certificates.
  • Malware or browser hijacking — in rare cases, malicious software injects fake certificates.

How to Fix It (Step by Step)

Start with the simplest and safest checks, and only proceed to more involved fixes if needed.

  1. Check your system clock. Right-click the time in your taskbar (Windows) or menu bar (Mac), choose “Adjust date/time,” and enable automatic time sync. Restart Chrome after fixing.
  2. Reload the page in Incognito mode. Press Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac). If the error disappears, a browser extension is likely interfering. Disable extensions one by one.
  3. Try another browser or device. If the error only appears in Chrome, the problem is likely Chrome-specific. If it appears everywhere, the issue is on the server or your network.
  4. Clear Chrome’s SSL state (Windows only). Go to Settings → Privacy and security → Security, and click “Manage certificates.” In the window that opens, go to the “Trusted Root Certification Authorities” tab, select any suspicious entries, and remove them. Then restart Chrome. On Mac, use Keychain Access instead.
  5. Update Chrome and your OS. Go to Settings → About Chrome to check for updates. Also install the latest Windows or macOS updates.
  6. Check for antivirus SSL scanning. Look in your antivirus or firewall settings for an option like “Scan SSL” or “HTTPS scanning” and temporarily disable it to test. If the error goes away, add an exception for the site or contact your IT admin.
  7. If it’s a corporate or school network, contact your IT department. They may need to install their root certificate on your device.

What NOT to Do

The biggest mistake is clicking “Advanced” and then “Proceed to site” without understanding the risk. That bypasses the warning and sends your data over an unverified connection — a man-in-the-middle attacker could intercept everything you type. Only do this if you are absolutely certain the site is legitimate (e.g., a personal router admin page or a test server you control) and you understand the risk.

Also avoid downloading “certificate fixer” tools or disabling Chrome’s security warnings entirely. Those are common malware vectors.

How to View the Certificate Details

Before fixing, you can inspect the certificate to understand what’s wrong:

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

Look at the “Issued By” field. If it says the site’s own name, it’s self-signed. If it shows a company you don’t recognize, it might be a corporate proxy. If the “Valid from” dates are outside today’s date, the certificate is expired.

When the Problem Is on the Website’s Side

If the error appears on a well-known site (like google.com or wikipedia.org) on multiple devices and networks, the website’s server is misconfigured. They may have an incomplete certificate chain or an expired certificate. You can check the site’s certificate status using an online SSL checker (search “SSL checker” and enter the domain). If the checker reports a chain issue, the site owner needs to fix it — there’s nothing you can do on your end except wait or contact them.

Frequently Asked Questions

Is it safe to click “Proceed to site”?

Generally no. It bypasses the warning entirely, leaving your connection unencrypted and unverified. Only do it for a site you know and trust, such as your router’s admin page, and only if you understand the risk.

Why does this error appear on my own website?

Your web server is likely missing intermediate certificates. Most hosting providers have a guide to install the full certificate chain (your certificate + intermediate + root). Check your hosting control panel or contact support.

Does clearing cookies help?

No, cookies are unrelated to certificate validation. Clearing them won’t fix this error. Stick to the steps above.

Why does it happen only on Chrome and not Firefox?

Chrome and Firefox use different certificate stores. Chrome uses the operating system’s store (on Windows and Mac), while Firefox has its own. If a root certificate is missing from the OS store, Chrome fails but Firefox may succeed. You can often fix this by updating your OS.

Can a VPN cause this error?

Yes, some VPNs or proxy extensions intercept traffic and present their own certificates. Try disconnecting the VPN and reloading the page.

What if the error appears on every HTTPS site?

That strongly suggests a system-wide issue: wrong date, a security program injecting certificates, or a corrupted certificate store. Start with the clock, then temporarily disable your antivirus, then clear the SSL state.

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 →