How to Fix NET::ERR_CERT_AUTHORITY_INVALID SSL Handshake Errors
Repair broken intermediate certificate bundles and establish a trusted X.509 chain of trust.
NET::ERR_CERT_AUTHORITY_INVALID occurs when a client browser cannot establish a cryptographic chain of trust from your web server's leaf certificate to a recognized root Certificate Authority. It is typically caused by a missing intermediate CA bundle or an untrusted self-signed certificate.
Root Cause Analysis
Web servers must serve the leaf certificate alongside all intermediate CA certificates. While desktop browsers may cache intermediates, mobile browsers and API clients strictly reject incomplete chains with authority invalid errors.
Step-by-Step Resolution Procedure
Run the SSL Chain Scanner above to check whether Tier 1 (Leaf), Tier 2 (Intermediate), and Tier 3 (Root) are properly linked.
Ensure you are using 'fullchain.pem' (or bundling your server certificate with the CA intermediate bundle) rather than serving only 'cert.pem'.
Point Nginx, Apache, or Caddy to the full certificate chain file and reload the service daemon.
Verification Command or Config Pattern
server {
listen 443 ssl http2;
server_name example.com;
# MUST point to fullchain.pem (includes leaf + intermediate CAs)
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers HIGH:!aNULL:!MD5;
}Frequently Asked Remediation Questions
Why does my site work on desktop but fail on mobile?
Desktop browsers frequently cache intermediate certificates from previous visits. Mobile browsers and curl command-line tools start with a cold cache and will fail immediately if the server omits intermediate certificates.
What is the difference between cert.pem and fullchain.pem?
'cert.pem' contains only the server leaf certificate. 'fullchain.pem' concatenates your leaf certificate followed by the intermediate CA certificates required by clients to trace trust to the root.
Can self-signed certificates be used in production?
No. Modern browsers automatically block self-signed certificates with security warnings because they cannot be verified against pre-installed OS root trust stores.
How do I verify certificate chain completeness?
Use the SSL Certificate Chain Scanner on OnChainScans to execute a direct TLS 1.3 socket handshake and inspect all certificate tiers in real time.
Complementary Diagnostic Scanners
All 34 toolsWCAG Accessibility & Contrast Scanner
Audits foreground/background luminosity contrast ratios against WCAG 2.2 AA (4.5:1) and AAA (7:1) thresholds, detecting missing alt attributes and keyboard traps.
Robots.txt & Sitemap.xml Scanner
Verifies syntax of robots.txt files, parses nested sitemap_index.xml structures, and audits for broken URLs, conflicting directives, and 404 indexing errors.
Website Font, Color & Asset Scanner
Crawls live stylesheets to extract distinct hex color palettes, webfont load methods (WOFF2/FOUT metrics), and total uncompressed asset payload distribution.
Related Troubleshooting & RFC Playbooks
How to Fix SPF PermError: 'Too Many DNS Lookups' (RFC 7208)
Resolve the 10-lookup limit that causes receiving mail servers (Gmail, Outlook) to reject your emails.
How to Fix ERR_TOO_MANY_REDIRECTS & Circular Redirect Loops
Diagnose infinite HTTP 301/302 redirects between Cloudflare Flexible SSL, Nginx, and CMS canonical rules.
How to Fix 'No Access-Control-Allow-Origin Header is Present' CORS Errors
Configure cross-origin preflight responses and secure credential sharing across APIs and single-page apps.