OnChainScans
NET::ERR_CERT_AUTHORITY_INVALID•RFC 5280 / TLS 1.3 RFC 8446• LIVE SCANNER EMBEDDED

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.

Live Diagnostic Tool: SSL Certificate Chain ScannerFull Tool Page
Executive Answer & Impact Analysis

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

1Inspect the Live Certificate Chain

Run the SSL Chain Scanner above to check whether Tier 1 (Leaf), Tier 2 (Intermediate), and Tier 3 (Root) are properly linked.

2Download Full-Chain Bundle

Ensure you are using 'fullchain.pem' (or bundling your server certificate with the CA intermediate bundle) rather than serving only 'cert.pem'.

3Update Web Server Configuration

Point Nginx, Apache, or Caddy to the full certificate chain file and reload the service daemon.

Verification Command or Config Pattern

TERMINAL / CONFIGRFC RFC 5280 / TLS 1.3 RFC 8446
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.