ERR_CERT_DATE_INVALID means Chrome thinks the website certificate is outside its accepted date range. The device clock may be wrong, or the website certificate may have expired or may not be valid yet. Check the clock first, then compare the same site on another updated device. Do not bypass the privacy warning to sign in, pay, or enter personal information.
Start with the pattern, not a long list of resets. If several familiar secure sites fail on one device, check that device. If one correctly typed public site fails on updated devices and separate trusted networks, contact the website owner. Those comparisons narrow the cause; they do not certify that a connection is safe.
What ERR_CERT_DATE_INVALID means
HTTPS is the encrypted connection used by websites for tasks such as signing in and paying. A certificate helps the browser verify the website’s identity and has a start and an end date. Chrome compares that validity window with the date and time reported by your device. A clock too far ahead can make a current certificate look expired. A clock too far behind can make it look as though it has not started yet.
The site’s certificate can also be genuinely outside its validity window. Visitors cannot renew or replace a public website certificate from the browser.
Read the full warning before changing anything
Chrome may pair this code with Your clock is ahead or Your clock is behind. Google’s Chrome certificate-date error guidance tells users with these messages to check the device date and time.
Check the exact URL too. A lookalike domain, old bookmark, or outdated subdomain can have a different certificate. Type the organization’s known home page yourself or use a bookmark you already trust.
Set the device clock correctly
- Compare the displayed date with today’s date.
- Check the time, including AM or PM on a 12-hour clock.
- Confirm the time zone and daylight-saving setting.
- Turn on automatic date and time from the operating system.
- Restart the browser after the clock is correct.
On Windows, find Settings > Time & language > Date & time and enable automatic time. Microsoft’s date and time instructions also explain the time-zone and daylight-saving controls. If automatic time-zone detection is unavailable, select your actual zone.
On a current Mac, open System Settings > General > Date & Time and enable automatic date and time, following Apple’s Mac clock settings guide. On a phone, search Settings for date and time; names vary by manufacturer. If a work or school device prevents changes, ask its administrator rather than overriding the policy.
Use the actual local time. Do not move the clock backward or forward just to make the warning disappear. That hides the comparison instead of establishing that the site certificate is valid now.
Find out whether the clock keeps changing
If the time becomes wrong again after a restart, the browser is reporting a symptom of a device problem. Check whether automatic time synchronization is enabled and whether the operating system can reach its time service. Install current system updates.
A computer that repeatedly loses its clock after being powered off may need manufacturer support. Do not open the computer or replace an internal battery unless the maker’s documentation says the repair is user serviceable.
Compare one website with several websites
Open two familiar HTTPS websites in new tabs. If many secure sites show date or privacy errors on the same device, check its clock, updates, VPN, proxy, and security software. If those sites work and one correct domain fails, the affected website deserves attention.
Do not clear every cookie or reset the router for a one-site certificate-date error. Those actions do not renew the certificate presented by the website.
Try the same site on another updated device
Use another phone or computer on the same WiFi. Confirm that its clock and operating system are current. If the second device opens the exact URL, focus on the first device. If both show the same date warning, compare a separate trusted network.
A second device is more useful than repeatedly reloading the page. It changes the clock, browser installation, certificate store, and security software while keeping the website constant.
Compare home WiFi with a trusted hotspot
If your mobile plan permits tethering and you have data available, open the same public page through your own phone hotspot. A second trusted connection can also work. If the error occurs only on one network, check for a guest portal, security filter, proxy, or provider page that may be presenting a different certificate.
This comparison does not prove that the WiFi signal is weak. A device can have full WiFi bars while a portal or inspection service changes the secure path.
Complete a public WiFi sign-in safely
Hotels, cafes, airports, and guest networks may require a portal before secure sites load normally. A portal is the venue’s internet-access sign-in page; it is not a fix for an expired public website certificate.
Confirm the network name with the venue and use its official sign-in prompt. Never enter a bank, email, or work password into a page that appeared after a certificate warning. If the portal will not load, ask the venue for help or use your own trusted connection. Do not click through the warning to reach a sensitive account.
Update an old device before blaming the website
An old operating system may carry an outdated certificate store. Install supported operating-system and browser updates, then restart the device. Use a supported device for sensitive services if the old one no longer receives security updates.
Moving to an older browser is not a safe workaround. A browser that ignores a warning has not made the certificate valid.
Review VPN, proxy, antivirus, and parental controls
Some security products inspect HTTPS by creating a local certificate chain. A stale or expired inspection certificate can produce date errors on one device or managed network. A VPN or parental-control tool can create a similar pattern.
Keep antivirus, firewall, browser protection and HTTPS inspection protections enabled. Check the product’s update status and use its vendor’s documented repair process. Contact the administrator for a work or school device instead of removing managed software or certificates. Compare a second trusted device or network to gather evidence without switching security off.
Treat router and NAS login pages separately
A local router, NAS, printer, or camera page may use a self-signed or factory certificate with an old date. Use the vendor’s current app, hostname, or supported local access method and install firmware through its documented interface.
Do not install a root certificate from a forum or expose the administration page to the internet. A local address does not make every certificate safe.
If the warning names a different code, follow that code instead: ERR_CERT_COMMON_NAME_INVALID concerns a website-name mismatch, while ERR_CERT_AUTHORITY_INVALID concerns the certificate issuer’s trust. Correcting the clock is not a universal cure for those errors.
Know when the website owner must fix it
If the correct public URL shows ERR_CERT_DATE_INVALID on updated devices with correct clocks and on separate trusted networks, report it to the operator. This is a reason to investigate the site, not complete proof of a server fault. DigiCert’s certificate browser-error guide explains that an expired certificate or an old certificate still served by a server, firewall or load balancer can cause date errors.
Send the public hostname, error code, time, time zone and your comparison results through the organization’s known support channel. Leave out account details, private work hostnames and any URL token. Crop personal information out of screenshots. The operator should check certificate dates, renewal and deployment rather than asking visitors to ignore the warning.
Skip fixes that hide the date problem
- Do not continue to a login or payment page.
- Do not change the clock to fit the certificate.
- Do not install an unknown certificate.
- Do not replace HTTPS with HTTP for a sensitive site.
- Do not disable certificate checks or browser protection.
- Do not copy a random DNS address or edit the hosts file.
Clearing all browsing data can sign you out without changing the device clock or website certificate. Keep each test tied to evidence from the site, device, or network comparison.
Match the repair to the pattern
| What you find | Next useful step |
|---|---|
| Several sites fail on one device | Correct its clock, update supported software and review vendor repair guidance. |
| One public site fails on current devices and separate trusted networks | Contact the website owner with the code and comparison results. |
| Only one network fails | Check its official portal or ask the network administrator about filtering. |
| A local router or NAS page fails | Use the manufacturer’s documented secure access method. |
| The clock becomes wrong after shutdown | Check automatic time settings and contact the device maker if it keeps happening. |
If otherwise working sites fail on one computer, use the one-device WiFi checklist. If every home device loses normal access, use the WiFi or internet outage comparison. Keep the warning in place until the current date falls inside a certificate chain that Chrome can trust.
