A drifted system clock or a stale Windows certificate store makes valid certificates fail validation across every browser at once.
A drifted system clock or a stale Windows certificate store makes valid certificates fail validation across every browser at once.
Settings → Time & language → set time automatically, then run `certutil -urlcache * delete` in an elevated prompt to clear cached revocation data and restart the browser.
Windows 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.
Running the check from outside your device separates a real certificate problem from a local clock or network issue in one step.
A drifted system clock or a stale Windows certificate store makes valid certificates fail validation across every browser at once.
Settings → Time & language → set time automatically, then run `certutil -urlcache * delete` in an elevated prompt to clear cached revocation data and restart the browser.
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.