How to Fix the "Your Connection Is Not Private" Error

What the warning means

When you visit a site over HTTPS, your browser checks the site's SSL/TLS certificate before it encrypts anything. "Your connection is not private" is the browser's way of saying that check failed: the certificate is expired, invalid, or doesn't match the site you're trying to reach. Rather than send your data over a connection it can't verify, the browser blocks the page.

Chrome usually pairs the message with an error code underneath, such as:

• NET::ERR_CERT_DATE_INVALID: the certificate has expired, or isn't valid yet
• NET::ERR_CERT_COMMON_NAME_INVALID: the certificate doesn't match the domain
• NET::ERR_CERT_AUTHORITY_INVALID: the certificate isn't from a trusted authority

Those codes point at the specific problem, which makes the fix faster.

Why it happens

The warning almost always comes down to one of these:

• The certificate has expired. Every certificate has a validity period, and once it passes, browsers stop trusting it.
• The certificate isn't valid yet. If the server's clock is wrong, the browser can think a valid certificate is out of date.
• The certificate doesn't match the domain. A certificate issued for one hostname (or a wildcard) won't cover a different one.
• The certificate is self-signed. Self-signed certificates are fine for testing but aren't trusted by browsers.
• The certificate chain is incomplete. If the intermediate certificate is missing, the browser can't verify the chain.
• The certificate was issued by an untrusted authority.

How to fix it on your own site

If the site is yours, work through these in order:

1. Check the certificate's expiry date. Click the padlock in the address bar, or run an openssl command, to see when it expires.
2. Renew the certificate if it has expired. Your certificate authority or hosting provider has the renewal path, and most let you automate it.
3. Check the hostname matches. Make sure the certificate covers the exact domain, including the www or non-www version.
4. Install the full chain. Install the intermediate certificate alongside your main certificate so the browser can build the full trust chain.
5. Clear your cache and give it a moment. After fixing, some visitors may still see the old error until caches clear.

What to do as a visitor

If you're visiting a site and hit this warning, it's often worth ruling out problems on your own device first:

• Reload the page. A one-off glitch can trigger the warning once and clear on refresh.
• Check your device's date and time. If your clock is wrong, valid certificates can look expired.
• Try incognito or a private window. This rules out a cached page or a browser extension interfering.
• Check your antivirus. Some antivirus "HTTPS scanning" features can conflict with the browser's own checks.

If the warning persists, the problem is the site's certificate, and only the site owner can fix it. You can proceed anyway in Chrome by clicking "Advanced" then "Proceed to site", but only do that on a site you know and trust, and never enter passwords or payment details. If it's a site you rely on, the best move is to let its owner know their certificate needs attention.

Chrome, Safari and Firefox

The same problem shows up with slightly different wording in each browser:

• Chrome: "Your connection is not private", with a NET::ERR_CERT code.
• Safari: "This Connection Is Not Private".
• Firefox: "Warning: Potential Security Risk Ahead".

The fix is the same in every browser: renew or correct the certificate. Only the wording and the "proceed anyway" button differ.

When it's an expiry problem

If the error code is NET::ERR_CERT_DATE_INVALID, or the padlock shows an expiry date in the past, the cause is expiry. That's also the easiest one to prevent, because certificates expire on a known schedule. The whole problem disappears if you're warned before the date arrives.

Stop it happening again

What makes this warning frustrating is that it's almost always avoidable. Certificates expire on a schedule, but only if someone is watching the dates. SSL monitoring does that automatically: it tracks every certificate, tells you before one expires, and can even remind you after the fact if one slips through. Set a reminder and you'll never be caught out by this screen again.

FAQ

How do I bypass "your connection is not private"?

In Chrome, click "Advanced" then "Proceed to site". Only do this on sites you trust, and avoid entering sensitive information.

Is "your connection is not private" dangerous?

It means the connection can't be verified as private. On a site you don't trust, treat it as a warning and don't enter passwords or card details.

Why does my website say "your connection is not private"?

Usually an expired certificate, a domain mismatch, or a missing intermediate certificate. Work through the site-owner steps above.

How do I fix it on an iPhone or iPad?

The cause is the same and the fix is on the server. As a visitor you can proceed at your own risk, but the site owner has to renew or correct the certificate.

What's the difference between "your connection is not private" and "not secure"?

Both are browser warnings about HTTPS. "Not private" usually points at the certificate; "not secure" can also flag mixed content or a missing certificate.

Can this happen on a site with a valid certificate?

Yes. A wrong system clock, a domain mismatch, or an incomplete chain can all trigger it on an otherwise valid certificate.