clock SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

Certificate error caused by a wrong device clock (NET::ERR_CERT_DATE_INVALID, "your clock is ahead/behind")

The site's certificate is valid, but the computer's date or time is wrong, so the browser thinks it is expired or not yet valid.

Exact message you may see Your clock is aheadYour clock is behindNET::ERR_CERT_DATE_INVALID clockcertificate is not yet valid system date wrongthe date and time on your computer are incorrect
Seen on: Chrome Windows SSL

Meaning

Set the date, time and timezone to automatic, sync NTP (w32tm /resync, timedatectl), and fix a dead CMOS battery or a VM with a paused clock. After a fix, restart the browser.

Common causes

  • Device date/time wrong
  • Dead CMOS battery or reset BIOS clock
  • VM/snapshot resumed with an old clock
  • Timezone/NTP disabled
  • Certificate truly expired (check separately)

⚡ Quick fix

  1. Enable automatic date/time sync
  2. Run w32tm /resync or chronyc makestep
  3. Compare with the real validity dates

Detailed fix by platform

Shell

  1. bash
    timedatectl status
    openssl s_client -connect example.com:443 </dev/null 2>/dev/null | openssl x509 -noout -dates

How to diagnose

  1. Clock — Correct?
  2. NTP — Enabled?
  3. Cert dates — Valid?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

ACM region — CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia) (SSL / TLS)ACM regioncert mismatch — SMTP TLS certificate verification failed: hostname mismatch / unable to get local issuer (mail client or library) (Email / SMTP)cert mismatchCookie — Cookie expires immediately or never because of clock skew or a wrong Expires date (HTTP)CookieDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)DjangoERR_CERT_DATE_INVALID — NET::ERR_CERT_DATE_INVALID (certificate expired) (JavaScript)ERR_CERT_DATE_INVALIDerror 9 — openssl verify error:num=9:certificate is not yet valid (SSL / TLS)error 9expiry — Certificate expired unexpectedly — manual renewal missed or automation failing silently (SSL / TLS)expiryHTTPS scanning — Antivirus HTTPS/SSL scanning breaks certificates (Avast, Kaspersky, ESET, Bitdefender) (SSL / TLS)HTTPS scanningclock

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.