Your connection is not private on Chrome

Chrome caches HSTS state per domain, so once a site has failed it keeps refusing even after the certificate is fixed.

Why it happens on Chrome

Chrome caches HSTS state per domain, so once a site has failed it keeps refusing even after the certificate is fixed.

The fix on Chrome

Go to chrome://net-internals/#hsts, enter the domain under 'Delete domain security policies', then hard-reload. Never use the 'thisisunsafe' bypass on a site where you enter a password.

If that didn't fix it

Chrome has its own failure mode, but Your connection is not private has a wider set of causes. The most common one overall is: The certificate expired (NET::ERR_CERT_DATE_INVALID).

Renew the certificate and reload the web server.

Check your own domain

Running the check from outside your device separates a real certificate problem from a local clock or network issue in one step.

Frequently asked questions

Why does Your connection is not private happen on Chrome?

Chrome caches HSTS state per domain, so once a site has failed it keeps refusing even after the certificate is fixed.

How do I fix Your connection is not private on Chrome?

Go to chrome://net-internals/#hsts, enter the domain under 'Delete domain security policies', then hard-reload. Never use the 'thisisunsafe' bypass on a site where you enter a password.

What does Your connection is not private mean?

Chrome's full-page warning shown whenever certificate validation fails. It is not a single error — the real cause is the NET::ERR_CERT_* code printed underneath it, and that code tells you which of expiry, trust, or hostname is wrong.