NET::ERR_CERT_AUTHORITY_INVALID (Your connection is not private)
The site’s certificate isn’t signed by a CA the browser trusts — self-signed, missing intermediates, or intercepted by a proxy.
Exact message you may see
Your connection is not private
Seen on:
JavaScript
Meaning
Self-signed certs in development, servers missing the intermediate chain, and corporate/antivirus HTTPS inspection all show this warning.
Common causes
- Self-signed certificate
- Server not sending the intermediate chain
- Corporate proxy / antivirus HTTPS interception
⚡ Quick fix
- Install a certificate from a public CA (Let’s Encrypt)
- Serve fullchain.pem
- For local dev use mkcert to create a trusted local CA
Detailed fix by platform
Linux
mkcert -install && mkcert localhost 127.0.0.1
How to diagnose
- Chain — Does SSL Labs/openssl show a complete chain?
- Network — Proxy intercepting?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in JavaScript
- TypeError TypeError: Cannot read properties of undefined (reading 'x')
- Failed to fetch TypeError: Failed to fetch / NetworkError when attempting to fetch resource
- module MIME type Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html"
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 11 Oct 2026