If you see a “Your connection is not private” or “NET::ERR_CERT_DATE_INVALID” warning in Google Chrome, the fix is usually to check your system clock, clear your browser cache, or install the correct security certificate. This guide walks you through the most common causes and step-by-step solutions, from simple refreshes to advanced certificate management.
What Causes a Certificate Error in Chrome?
Chrome displays a security certificate error when it cannot verify that the website you are visiting is genuinely the site it claims to be. This verification relies on a chain of trust: your browser checks the site’s SSL/TLS certificate against a list of trusted Certificate Authorities (CAs). If anything in that chain is broken, expired, or mismatched, Chrome blocks the page to protect you from potential man-in-the-middle attacks.
Common triggers include:
- Expired certificate: The website’s SSL certificate has passed its validity date.
- System clock is wrong: Your computer’s date or time is set incorrectly, making a valid certificate appear expired.
- Outdated browser: Older Chrome versions may not recognize newer certificate formats or CAs.
- Corporate or antivirus interception: Security software or a company proxy may be inspecting encrypted traffic with its own certificate.
- Corrupted cache or DNS: Stored data or a bad DNS resolution can point you to the wrong server.
Understanding the specific error code (like NET::ERR_CERT_DATE_INVALID or NET::ERR_CERT_AUTHORITY_INVALID) helps narrow down the fix.
First Steps: Quick Fixes That Often Work
Before diving into advanced settings, try these simple actions. They resolve a surprising number of cases.
- Refresh the page: Press Ctrl+F5 (or Cmd+Shift+R on Mac) to force a full reload, bypassing cached content.
- Check your system date and time: Right-click the clock in your taskbar, select “Adjust date/time,” and enable automatic time and time zone. If it is already on, turn it off and on again to force a re-sync.
- Try Incognito mode: Open a new Incognito window (Ctrl+Shift+N). If the error disappears, the problem is likely cached data or an extension.
- Restart Chrome: Fully close all Chrome windows and reopen the browser.
- Test another browser: If the site loads in Firefox or Edge, the issue is Chrome-specific, not the website itself.
If none of these work, proceed to the more targeted fixes below.
Clear Chrome’s Cache and SSL State
Chrome stores a local cache of certificates and page data. Over time, this can become corrupted or outdated, triggering false errors.
To clear the cache:
- Click the three-dot menu (top-right), go to Settings > Privacy and security > Clear browsing data.
- Choose “All time” for the time range.
- Check “Cached images and files” and “Cookies and other site data.” (You can leave browsing history unchecked if you want to keep it.)
- Click “Clear data.”
If the error persists, also clear the SSL state at the operating system level. On Windows, open Internet Options (search for it in the Start menu), go to the Content tab, and click “Clear SSL state.” This does not affect your personal certificates—it only removes cached copies of site certificates. On macOS, you can reset the certificate trust store via Keychain Access > System Roots > right-click > “Reset” (though this is rarely needed).
Check for Interfering Antivirus or VPN Software
Many antivirus suites (like Norton, McAfee, or Kaspersky) and some VPN clients perform “SSL scanning” or “HTTPS filtering.” They intercept encrypted traffic, decrypt it, inspect it, and re-encrypt it with their own certificate. If that certificate is not properly installed or has expired, Chrome will see an untrusted authority.
To test this:
- Temporarily disable the antivirus’s web protection or SSL scanning feature (do not disable the whole product).
- If the error goes away, re-enable the feature and instead update the antivirus software or reinstall its certificate.
- For VPNs, disconnect and try the site again. If it works, the VPN’s certificate is the culprit—update the VPN client.
Corporate networks often use similar interception. If you are on a work computer, contact your IT department rather than trying to bypass the warning.
Manually Install or Update the Website’s Certificate
If the error is specifically NET::ERR_CERT_AUTHORITY_INVALID or NET::ERR_CERT_COMMON_NAME_INVALID, the site’s certificate may be misconfigured or self-signed. This is common on internal tools, test servers, or some local network devices.
To view the certificate details:
- Click the padlock icon (or “Not secure”) in the address bar.
- Select “Certificate is not valid” or “Connection is not secure” > “Certificate information.”
- Check the “Issued to” and “Issued by” fields. If the issuer is not a recognized CA, you have three options:
- Add the certificate to your trusted store: Export the certificate (usually a .cer or .crt file) and import it into Chrome’s trust store. On Windows, go to Settings > Privacy and security > Security > Manage certificates, then import under “Trusted Root Certification Authorities.” On macOS, use Keychain Access.
- Contact the site administrator: If the certificate is expired or misconfigured, only the site owner can fix it. You should not proceed past the warning.
- Use a different URL: Sometimes the site is accessible via
https://www.example.cominstead ofhttps://example.com—the certificate may only cover one variant.
Only install certificates from sources you trust. Installing a malicious certificate gives the owner full access to your encrypted traffic.
Reset Chrome Flags and Disable Extensions
Chrome flags (experimental features) and extensions can sometimes interfere with certificate validation. A misbehaving extension might block or redirect certificate checks.
To test extensions:
- Open Chrome’s menu > Extensions > Manage extensions.
- Disable all extensions, then reload the page with the error.
- If it works, re-enable extensions one by one to find the culprit.
To reset flags:
- Type
chrome://flagsin the address bar. - Click “Reset all” at the top-right.
- Relaunch Chrome.
Note that resetting flags does not affect your bookmarks or passwords.
When to Proceed Anyway: Understanding the Risks
Chrome allows you to click “Advanced” and then “Proceed to [site] (unsafe)” on some errors. This is almost never a good idea, but there are rare exceptions:
- You are on a trusted internal network and the site uses a self-signed certificate that you have verified with your IT team.
- You are testing a development server you control.
- The error is clearly a clock issue that you have already fixed but the page hasn’t refreshed.
In all other cases, especially on public websites, leaving the page is the correct action. The warning exists because your data could be intercepted or the site could be impersonating a legitimate one. If you see the error on a site you frequently use (like Google, banking, or email), it is more likely a problem on your device than on the site itself.
Frequently Asked Questions
Why does Chrome keep saying my connection is not private?
This usually means the website’s certificate is expired, your system clock is wrong, or an antivirus/VPN is intercepting traffic. Start by checking the date and time, then clear your cache, and finally test with antivirus/VPN disabled.
Can I permanently ignore a certificate error for a specific site?
Chrome does not offer a built-in “ignore for this site” option for security errors. You can either install the site’s certificate in your trusted store (if you control the site) or use a third-party extension that bypasses warnings, but doing so is risky and not recommended for public sites.
What does NET::ERR_CERT_DATE_INVALID mean?
This error specifically means the certificate’s validity period does not match your system’s current date. The most common fix is to correct your computer’s clock and time zone. If the clock is correct, the website’s certificate is genuinely expired.
Is it safe to click “Proceed to site”?
Generally no. You lose the encryption guarantee that protects your data from eavesdropping. Only do it if you are absolutely certain the site is legitimate and you understand the risk, such as on a personal internal server.
How do I update Chrome to fix certificate errors?
Chrome updates automatically in the background. To check manually, go to the three-dot menu > Help > About Google Chrome. Chrome will check for updates and install them, then ask you to relaunch.
Why does the error only happen on one website?
If only one site fails, the problem is almost certainly on the website’s side—its certificate is expired, misconfigured, or the domain name doesn’t match. Contact the site administrator. If it happens on many sites, the problem is on your device (clock, cache, antivirus).
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix 0x80070005 DISM Error & the 0x800070005 Typo
- Fix Access Denied Adding Shared Printer in Windows 10
- How to Play Minesweeper: Rules, Tips, and Winning Strategy
- Browser SQL Sandbox for Games: Build Guide
- Snapchat Face Swap: Step-by-Step Guide
- Fix a Computer Chair Height Adjuster: Step-by-Step