Fix "Your Connection Is Not Private" Errors

This warning (NET::ERR_CERT_*) means the browser can't verify your certificate is valid for this exact connection. In rough order of likelihood:

1. Expired certificate — check the expiry date; this is the most common cause by far.
2. Domain mismatch — the certificate covers example.com but the site is loading www.example.com, or vice versa.
3. Missing intermediate certificates — the CA bundle wasn't installed, so some browsers/devices can't build the trust chain.
4. Self-signed certificate — fine for local development, always a warning in production.
5. Clock skew — the visitor's device date/time is wrong, so a valid certificate looks not-yet-valid or expired to them.
6. Outdated cached certificate — you renewed, but the old certificate is still cached at a CDN or proxy layer.

Run your domain through an SSL checker (see our Free SSL Tools) — it will usually tell you exactly which of these it is within seconds.

Reading the specific error code, not just the general warning

Chrome, Firefox, and Safari all display a version of this same generic warning, but each reveals a more specific underlying code if you look — in Chrome, clicking "Advanced" shows something like NET::ERR_CERT_AUTHORITY_INVALID or NET::ERR_CERT_DATE_INVALID, which points at one of the five causes above rather than leaving you to guess. Firefox and Safari surface similarly specific detail behind their own "Advanced" or "Show Details" links.

What to do as a visitor versus as the site owner

If you're a visitor encountering this on someone else's site, there's no fix available on your end beyond correcting your own system clock if that's the actual cause — clicking through the warning on a site you don't control and don't have independent reason to trust is genuinely risky, not just an inconvenience to route around. If you're the site owner receiving reports of this from visitors, treat it as urgent: every visitor seeing this warning is one who's being actively discouraged from continuing, and the underlying cause (expired certificate, incomplete chain) doesn't fix itself.