NET::ERR_CERT_AUTHORITY_INVALID
This browser error means the SSL certificate was not issued by a trusted authority, or the chain is incomplete. Usually a self-signed certificate, a missing intermediate, or an untrusted CA.
- About the error
- Why do I see this error
- Solution
- Serve the full certificate chain
- Verify the chain
- Use a real certificate (not self-signed) in production
- Local development
- If only one device sees the error
About the error
Chrome shows NET::ERR_CERT_AUTHORITY_INVALID behind a "Your connection is not private" warning. The browser received a certificate it can't trace back to a Certificate Authority it trusts, so it refuses to proceed.
Why do I see this error
- A self-signed certificate (common in local dev and on staging).
- A missing intermediate certificate, the leaf is valid but the browser can't build the chain to a trusted root.
- A certificate from an untrusted or unknown CA.
- A certificate that doesn't match the domain, or has expired (often a slightly different error, but related).
Solution
Serve the full certificate chain
This is the most common production cause. nginx does not fetch intermediates for you, so ssl_certificate must point at the full chain (leaf + intermediates), not just your domain's certificate:
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
Using fullchain.pem (not cert.pem) is what fixes the "authority invalid" error for an otherwise valid Let's Encrypt certificate. Reload after changing it:
nginx -t && systemctl reload nginx
Verify the chain
Check what the server actually sends. A complete chain shows the intermediate; a broken one stops at your leaf:
openssl s_client -connect example.com:443 -servername example.com -showcerts
Use a real certificate (not self-signed) in production
If this is a public site, issue a free, trusted certificate with Certbot instead of a self-signed one:
sudo certbot --nginx -d example.com -d www.example.com
Local development
For a local self-signed certificate the warning is expected. Use a tool that installs a locally-trusted CA (such as Laravel Valet's TLS, or mkcert) rather than clicking through the warning every time.
If only one device sees the error
When the site loads fine for everyone else, the problem is local to that machine, not the server:
- Wrong date and time. Certificate validation depends on the system clock. Correct the date, time and timezone, then reload the page.
- Antivirus or firewall HTTPS scanning. Security software that inspects encrypted traffic substitutes its own certificate. Turn off HTTPS/SSL scanning in the tool, or let it install its trusted CA.
- A corporate proxy performing TLS interception. Your network administrator needs to deploy the proxy's root certificate to the device's trust store.
This is the browser-facing cousin of two server-side TLS errors: SSL handshake failed in nginx and curl (60) SSL certificate problem.