"Your Connection Is Not Private": Every Cause and the Exact Fix

Fix "Your Connection Is Not Private": Every Cause and the Exact Fix
"Your connection is not private" is not one error — it is Chrome and Edge folding five distinct certificate problems into a single warning: an expired certificate, a hostname mismatch, an untrusted CA or missing intermediate, a self-signed certificate, and a wrong system clock. Site owners must fix the certificate itself (renew or redeploy the full chain); visitors should first check the date, network, and browser profile. Running openssl s_client reveals the exact reason in seconds via the "Verify return code". Match that code to the right fix below.
Five root causes map to five NET::ERR codes
Chrome distinguishes the causes with different codes: NET::ERR_CERT_DATE_INVALID (expired or wrong date), NET::ERR_CERT_COMMON_NAME_INVALID / SAN mismatch (certificate does not cover the hostname), NET::ERR_CERT_AUTHORITY_INVALID (untrusted CA or missing intermediate), NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM (weak hashes such as SHA-1), and certificate transparency (CT) errors. Each needs a different fix — there is no single remedy.
Read the verify return code with openssl
openssl s_client -connect host:443 -servername host prints "Verify return code" at the end. Code 10 means the certificate has expired, 18 means self-signed, 19 means an untrusted root (self-signed in chain), 20 means unable to get the local issuer (missing intermediate), and 62 means hostname mismatch. These numbers map directly to the five causes above. Once you have the code, apply the matching fix from the related guides.
Visitor-side vs owner-side responsibility
Owners must serve a valid, fully chained, trusted certificate; visitors can do little else. First confirm the system date and timezone are correct — a wrong clock makes every certificate look expired. Then try another network (corporate proxies that do TLS inspection trigger CA errors) or a clean browser profile. If a site you trust warns everywhere, it is the owner's misconfiguration — do not enter credentials until it is fixed.
Step 1: Check the system clock (visitors only)
Open the date/time settings and enable "set time automatically" with the correct timezone. A wrong clock is the most common visitor-side cause of false "certificate expired" reports and needs no change to the website.
Step 2: Locate the problem with the SSL Checker
Hand the URL to the SSL Checker; it reports whether the certificate is expired, the hostname matches, and the chain is complete. You can also use the Certificate Decoder to inspect the SANs and validity period.
Step 3: Renew or redeploy the certificate (owners)
If the check shows expiry or an incomplete chain, renew the certificate and deploy the full chain (leaf plus every intermediate, not the root). Use the Certificate & Key Matcher to confirm the deployed certificate and private key are a pair. Note that the CA/Browser Forum's SC-081v3 has shortened the maximum certificate lifetime to 200/100/47 days (phased in from 2026-03-15), so renewals happen more often — automate them.
Step 4: Reissue to cover the hostname when needed
If the error is a hostname mismatch (code 62), reissue the certificate for the exact hostnames you serve — including the www prefix — and write the correct SAN list, rather than masking it with server rewrites.
Troubleshooting checklist
| Browser prompt / return code | Likely cause | What to do |
|---|---|---|
| NET::ERR_CERT_DATE_INVALID / code 10 | Certificate expired or wrong clock | Owner renews; visitor calibrates clock |
| NET::ERR_CERT_COMMON_NAME_INVALID / code 62 | SAN does not cover the hostname | Reissue with the correct SAN list |
| NET::ERR_CERT_AUTHORITY_INVALID / code 19, 20 | Self-signed or missing intermediate | Deploy full chain; use a private CA internally |
| NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM | Forbidden algorithm such as SHA-1 | Reissue with SHA-256/RSA or ECDSA |
| CA errors on every device | TLS-inspecting proxy / broken chain | Check intermediates; install proxy root |
| Errors on only some devices | Different trust stores / clocks / proxies | Compare dates and CA bundles per device |
Tools & further reading
- SSL Checker: one-click check for expiry, hostname, and chain completeness
- Certificate & Key Matcher: confirm the deployed certificate and key are a pair
- Certificate Decoder: inspect SANs, validity, and issuer
- SSL certificate guide: complete tutorial from selection to deployment
- Related: Hostname Mismatch: SSL Common Name and SAN Errors, \, NET::ERR_CERT_AUTHORITY_INVALID: Complete Fix Guide
FAQ
Can I safely bypass the warning?
Only if you are certain of the site's identity and the cause is a clock or local configuration issue. On public Wi-Fi or unknown sites, never bypass it — that can expose you to a man-in-the-middle attack.
Why does the same site warn on only some devices?
Devices differ in trust stores, system clocks, and proxy settings. If your phone warns but your desktop does not, compare the dates and CA bundles first; devices on a corporate network may also sit behind a TLS-inspecting proxy.
The certificate is not expired, so why the expiry warning?
Most often the visitor's local clock is wrong; second, the certificate may be unexpired but missing its intermediate chain, which browsers treat as untrusted. The [SSL Checker](/check) shows the expiry date and chain status at a glance.
Does a self-signed certificate always trigger this warning?
Yes. A self-signed certificate is trusted by no store by default, so it always triggers. It is acceptable for local development, but public services should use a publicly trusted CA or an internal private CA (see [Fix Self-Signed Trust](/articles/fix-self-signed-trust)).
Free SSL/TLS tools
Verify and inspect your certificates in seconds.
Related Certificate Info
Learn more about choosing and buying certificates.