Back to Articles
Troubleshooting2026-06-18•4 min read•CSR.plus Team

NET::ERR_CERT_AUTHORITY_INVALID: What It Means and How to Fix It

NET::ERR_CERT_AUTHORITY_INVALID: What It Means and How to Fix It

When Chrome shows NET::ERR_CERT_AUTHORITY_INVALID it could not chain the server's certificate back to a root it trusts. The most common real cause is a missing intermediate certificate on the server, not a malicious site. Site owners should deploy the full chain (leaf + intermediates); visitors should first check the system clock, try another network or browser, and only bypass the warning for sites they own and trust.

What the browser is telling you

This is a "certificate not trusted" error, different in nature from expiry or hostname mismatch. It appears at chain validation: after receiving the leaf, the browser cannot walk up to a trusted root, so it cannot confirm the issuer is trusted. The page may still be reachable via "Advanced > Proceed", but only do that when you are sure it is a configuration issue, not an attack.

Why a missing intermediate is the usual cause

Most public CAs do not sign leaves directly from the root; they use root-issued intermediates. The server must send the leaf and the full intermediate chain. If it sends only the leaf, some clients lack the intermediate needed to complete the path to the root and report an untrusted authority. The Certificate Decoder shows exactly which certificates the server sent.

Other causes: internal CAs, expired roots, TLS-inspecting proxies

Internal corporate CAs trigger this error when the client trust store does not contain the root. A few legacy (SHA-1 era) roots are no longer trusted by some clients. TLS-inspecting antivirus or corporate proxies present their own CA; if that root is not trusted, many sites error at once.

Step 1: Confirm whether the chain is incomplete

Use the SSL Checker or openssl s_client -connect yourdomain.com:443 -servername yourdomain.com and check the Verify return code. A code of 20 indicates the local issuer certificate could not be found (usually a missing intermediate); 21 means the first (leaf) certificate could not be verified.

OpenSSL verify codes: 20 = unable to get local issuer certificate (usually a missing intermediate) · 21 = unable to verify the first certificate.

Step 2: Obtain and deploy the full chain

Download the CA's full chain bundle, concatenate leaf + intermediates in order, and deploy it (on Nginx, point ssl_certificate at the fullchain). Reload and re-test.

Step 3: Replace certificates whose root has expired

If the chain reaches an expired root (some SHA-1 era roots still fail on certain clients), reissue from the CA using a currently trusted root.

Step 4: Handle internal CAs and corporate proxies

For internal tools, install the internal root into client trust stores and keep its CRL reachable. For a TLS-inspecting proxy, add the proxy's root to the trust store or temporarily disable inspection to compare.

Step 5: Quick checks for visitors

First correct the system date and time (clock skew breaks every certificate check), then try another network and another browser. If it works elsewhere it is local; if it fails everywhere the site is misconfigured — report it to the owner.

Troubleshooting checklist

SymptomLikely causeFix
Error on a single site you manageMissing intermediate certificateDeploy the full chain; verify with the Certificate Decoder
Error on many sites at onceTLS-inspecting AV / corporate proxy, or wrong clockCheck the proxy certificate or correct the device clock
Error right after a certificate swapWrong/expired root or wrong chain orderRe-deploy leaf + intermediates in the correct order
Internal tool fails for employeesInternal CA not in the trust storeInstall the internal root into client trust stores
Fails only on some older clientsLegacy root (e.g. SHA-1 era) not trustedReissue from a currently trusted root

Related articles

FAQ

Is it safe to click "Proceed anyway"?

Only if you are certain the site is legitimate and the problem is a server configuration issue (for example, you manage the site). On any public site you did not initiate, treat it as a warning and leave.

Does antivirus software cause this error?

Yes. TLS-inspecting antivirus or corporate proxies present their own CA. If the error appears on many sites at once, your AV/proxy certificate or system clock is the likely cause.

Why does it appear on only some devices?

Devices differ in trust stores, system clocks, and proxy settings. An error limited to one device is usually that device's local trust or clock issue, not the site itself.

Free SSL/TLS tools

Verify and inspect your certificates in seconds.

Related Certificate Info

Learn more about choosing and buying certificates.

Related articles