How to Fix NET::ERR_CERT_DATE_INVALID (Google Chrome)
Quick Answer: The NET::ERR_CERT_DATE_INVALID error indicates that Google Chrome detected an SSL/TLS certificate with an expired or future validity date. The most likely cause is an incorrect system date and time on your local machine. Immediately verify your computer's date, time, and timezone settings are accurate via your OS settings. Correcting these settings should resolve the error, allowing Chrome to establish a secure connection to the website.
What Causes This Error
- Client-side system clock skew: Your computer's date and time are significantly out of sync with Network Time Protocol (NTP) servers, making valid certificates appear expired or not yet valid.
- Expired or invalid SSL/TLS certificate on the web server: The website's certificate has genuinely passed its 'Valid To' date or has a 'Valid From' date in the future.
- Outdated Root Certificates or Certificate Revocation Lists (CRLs): Your operating system or browser's trust store lacks the latest root certificates or has stale CRLs, preventing proper validation.
- Interference from security software: Antivirus, firewall, or proxy software performing SSL inspection (HTTPS interception) might present its own certificate with an incorrect date.
- Misconfigured Virtual Machine (VM) clock: If accessing from a VM, its internal clock might not be synchronized with the host or NTP, leading to time discrepancies.
Step-by-Step Fixes
Fix 1: Synchronize System Date and Time
For Windows: Go to 'Settings' > 'Time & Language' > 'Date & Time'. Ensure 'Set time automatically' and 'Set time zone automatically' are toggled ON. Click 'Sync now' under 'Synchronize your clock'.,For macOS: Go to 'System Settings' > 'General' > 'Date & Time'. Ensure 'Set date and time automatically' and 'Set time zone automatically using your current location' are checked.,For Linux (GNOME): Go to 'Settings' > 'Date & Time'. Enable 'Automatic Date & Time' and 'Automatic Time Zone'.,Restart your browser (Chrome) and attempt to access the website again.
Fix 2: Clear Chrome's SSL State and Cache
Open Chrome and navigate to 'Settings' > 'Privacy and security' > 'Clear browsing data'.,Select 'All time' for the time range. Check 'Cached images and files' and 'Cookies and other site data'. Click 'Clear data'.,For Windows: Open 'Internet Properties' by searching 'inetcpl.cpl' in the Start menu. Go to the 'Content' tab and click 'Clear SSL state'.,Restart Chrome and re-test the website connection.
Fix 3: Temporarily Disable Security Software SSL Inspection
Identify any active antivirus, firewall, or VPN software that performs HTTPS scanning or SSL inspection (e.g., Avast, Kaspersky, corporate proxies).,Access the settings of the identified security software. Locate and temporarily disable features like 'HTTPS scanning', 'SSL inspection', or 'Web Shield'.,Attempt to access the website. If the error is resolved, re-enable the feature and consider adding an exception for the specific website if possible, or consult the software vendor's documentation for permanent configuration.,Remember to re-enable security features after testing if the issue persists elsewhere.
Fix 4: Update Google Chrome and Operating System
Update Chrome: Open Chrome, click the three-dot menu, go to 'Help' > 'About Google Chrome'. Chrome will automatically check for and install updates. Relaunch if prompted.,Update Operating System: For Windows, go to 'Settings' > 'Windows Update' and check for updates. For macOS, go to 'System Settings' > 'General' > 'Software Update'. For Linux, use your distribution's package manager (e.g., `sudo apt update && sudo apt upgrade`).,Outdated OS versions may have outdated root certificate stores, leading to validation failures.,After all updates are applied and systems restarted, re-check the website.
Advanced Fixes
Advanced Fix 1: Verify Certificate Chain and Server Time via OpenSSL
Open a terminal or command prompt. Use the `openssl` command to inspect the website's certificate chain and validity dates directly from the server: `openssl s_client -servername [hostname] -connect [hostname]:443 | openssl x509 -noout -dates` (replace `[hostname]` with the actual domain).,Examine the `notBefore` and `notAfter` dates. Compare these to your system's current date and time. If the certificate is genuinely expired or not yet valid, the issue lies with the server.,You can also check the server's reported time using `curl -v --head https://[hostname]` and look for the `Date:` header in the response. Significant discrepancies between server time and your local time (after accounting for time zones) can indicate a problem.
FAQs
Q: Why does my computer's date and time affect website security?
A: SSL/TLS certificates have specific validity periods defined by 'Valid From' and 'Valid To' dates. Your browser compares these dates against your system's clock. If your clock is incorrect, a perfectly valid certificate might appear expired or not yet active, causing Chrome to block the connection to prevent potential security risks.
Q: Is it safe to bypass this error by clicking 'Proceed anyway'?
A: No, it is generally NOT safe. Bypassing this error ('Proceed anyway' or similar options) instructs your browser to ignore a fundamental security warning. This could expose you to man-in-the-middle attacks, where an attacker could intercept or tamper with your data (passwords, credit card numbers) without you knowing. Only proceed if you are absolutely certain of the website's authenticity and the reason for the error (e.g., a known internal server with a self-signed certificate you trust).
Q: Can a VPN or proxy cause NET::ERR_CERT_DATE_INVALID?
A: Yes, potentially. Some VPNs or corporate proxies perform SSL inspection, where they decrypt and re-encrypt HTTPS traffic. If their internal certificate authority or the certificates they issue have incorrect date/time settings, or if your system doesn't trust their root certificate, it can trigger this error. Temporarily disabling the VPN/proxy or checking its settings might help diagnose the issue.
Q: What if the website itself has an expired certificate?
A: If the website's SSL/TLS certificate is genuinely expired, there is nothing you can do on your end to fix it. The website administrator must renew their certificate. In this scenario, the error is legitimate, and accessing the site would mean connecting over an unencrypted or untrusted channel, which is a security risk. Contact the website owner to inform them of the issue.