How to Fix “Your Clock Is Ahead” or “Your Clock Is Behind” in Google Chrome

While attempting to visit secure websites in Google Chrome, you may suddenly be blocked by an alarming red warning screen displaying the error message “Your clock is ahead” or “Your clock is behind”, alongside the technical error code NET::ERR_CERT_DATE_INVALID. Chrome warns that a private connection cannot be established because your computer’s date and time are inaccurate.

Every secure website relies on SSL/TLS digital certificates that possess strict cryptographic start and expiry timestamps. If your operating system clock is skewed from coordinated universal time by even a few minutes, Chrome calculates that the website’s certificate has either expired or is not yet valid. This tutorial details how to resynchronise your system clock across Windows and macOS to resolve this error immediately.

Method 1: Force Time Synchronisation in Windows 11

In most instances on Windows PCs, the background Windows Time service (W32Time) has stalled or failed to reach its default network time protocol (NTP) server.

1. Right-click the clock in the bottom-right corner of your Windows taskbar and select Adjust date and time.
2. In the Settings window, verify that both Set time automatically and Set time zone automatically are toggled on.
3. Scroll down to the Additional settings section and locate Sync now.
4. Click the Sync now button. A small checkmark will confirm that your clock was successfully synchronised with time.windows.com.
5. Close Google Chrome completely, reopen it, and reload the blocked webpage.

Method 2: Switch to a Reliable NTP Time Server in Windows

If clicking “Sync now” returns a time synchronisation error, Microsoft’s default time server may be experiencing regional downtime or packet loss.

1. Press Windows + R to open the Run dialogue box.
2. Type timedate.cpl and press Enter to launch the classic Date and Time control panel.
3. Click on the Internet Time tab.
4. Click the Change settings… button (administrator privileges required).
5. Ensure Synchronize with an Internet time server is ticked.
6. In the Server field, replace time.windows.com with Google’s public NTP server:

   time.google.com

   or the Cloudflare time server:

   time.cloudflare.com

7. Click Update now. When the status confirms successful synchronization, click OK.

Method 3: Restart the Windows Time Service via Command Prompt

If the time synchronization service is suspended in memory, restarting the daemon cleanly restores automatic time retrieval.

1. Click Start, type cmd, right-click Command Prompt, and select Run as administrator.
2. Unregister and re-register the time service by running:

   net stop w32time
   w32tm /unregister
   w32tm /register
   net start w32time
   w32tm /resync /force

3. The terminal will confirm: “The command completed successfully.”
4. Restart Chrome and test your browsing access.

Method 4: Fix Clock Synchronisation on Mac (macOS)

On Apple Mac computers running macOS Sonoma, Ventura, or Sequoia, synchronisation settings are managed within Apple’s system configuration.

1. Click the Apple menu in the top-left corner and select System Settings.
2. Click General in the left sidebar, then select Date & Time.
3. Toggle on Set time and date automatically.
4. Confirm that the Source is set to time.apple.com.
5. If the switch is already active but the time is wrong, toggle it off, wait 5 seconds, and toggle it back on.
6. Verify that your Time Zone matches your true location.

Chrome SSL Date Error Diagnostics Reference Table

The table below provides a troubleshooting reference for common SSL timestamp errors in Google Chrome:

Displayed Message	Underlying Cause	Immediate Action
“Your clock is behind”	System clock set prior to certificate validity date	Sync clock via Settings > Time & Language > Sync now
“Your clock is ahead”	System clock set past certificate expiration date	Correct system year/month and select automatic NTP
Time resets after every reboot	Depleted CR2032 CMOS battery on motherboard	Replace motherboard coin-cell battery
Clock is correct but error persists	Corrupted Chrome SSL socket cache	Visit chrome://net-internals/#sockets > Flush socket pools

Preventing Recurring Clock Desynchronisation

If your desktop PC repeatedly loses its correct time whenever it is powered off at the wall socket, the internal CR2032 CMOS coin battery on your motherboard has expired and requires physical replacement. On laptops, keeping the operating system connected to Wi-Fi ensures that background NTP services maintain microsecond-level accuracy automatically.