How to Fix Chrome Certificate Error
Chrome certificate errors can block access to trusted websites when the browser cannot verify a site’s SSL/TLS certificate.
This guide explains the most common causes and the safest ways to fix the problem without weakening your security.
What a Chrome certificate error means
A certificate error in Google Chrome usually means the browser cannot confirm that a website is authentic and encrypted.
Chrome checks the site certificate, the issuing certificate authority, the encryption chain, and the date and time on your device before allowing a secure connection.
When any part of that trust chain fails, Chrome may show warnings such as NET::ERR_CERT_DATE_INVALID, NET::ERR_CERT_COMMON_NAME_INVALID, or ERR_CERT_AUTHORITY_INVALID.
The exact code helps narrow down the cause.
Common causes of certificate errors in Chrome
- Incorrect system date and time on Windows, macOS, Linux, Android, or iOS
- Expired website certificate or misconfigured renewal
- Outdated root certificates on the operating system
- Antivirus or firewall SSL inspection interfering with traffic
- Captive portals on public Wi-Fi that redirect secure traffic
- Browser cache or cookies causing stale security data
- VPN, proxy, or enterprise network policies modifying certificates
- Local development certificates not trusted by Chrome
How to fix Chrome certificate error on your device
1. Check your system date, time, and time zone
An incorrect clock is one of the most common causes of certificate problems because certificates have strict validity windows.
Open your device’s date and time settings and enable automatic time synchronization if possible.
- On Windows, turn on Set time automatically and Set time zone automatically
- On macOS, enable Set date and time automatically in System Settings
- On Android and iPhone, enable automatic date and time in the device settings
2. Reload the page and verify the website address
Simple typing mistakes can lead to a certificate mismatch if you land on the wrong hostname.
Confirm the URL uses https:// and that the domain is spelled correctly, including subdomains such as www.
3. Clear Chrome cache and cookies
Old cached responses can sometimes preserve broken redirects or stale certificate-related data.
In Chrome, go to settings, clear cached images and files, and, if necessary, remove cookies for the affected site.
If you only want to test whether cached data is the problem, open the site in an Incognito window first.
If the warning disappears there, cached browser data is a likely factor.
4. Update Chrome to the latest version
Chrome includes updated security rules, root store behavior, and certificate validation fixes over time.
Open Settings > About Chrome to trigger an update, then restart the browser.
Keeping Chrome current is especially important for sites that use modern encryption standards such as TLS 1.2 and TLS 1.3.
5. Update your operating system
Chrome relies on the operating system for many trusted certificate authorities and security components.
Install pending system updates on Windows Update, macOS Software Update, or your Linux distribution’s package manager.
Older systems may lack current root certificates, which can cause errors even when the website is correctly configured.
6. Disable antivirus SSL scanning temporarily
Some antivirus suites inspect HTTPS traffic by inserting their own certificates.
If that feature is misconfigured or outdated, Chrome may reject the connection.
- Look for settings such as HTTPS scanning, SSL inspection, or encrypted connection scanning
- Disable the feature briefly to test whether it is causing the issue
- If the problem disappears, update the antivirus software or adjust its HTTPS inspection settings
7. Check VPN and proxy settings
VPN clients and proxies can rewrite traffic, force certificate interception, or route you through networks that present untrusted certificates.
Disconnect from the VPN and retry the page.
On managed devices, inspect system proxy settings and confirm that no corporate proxy is injecting a certificate that Chrome does not trust.
8. Sign in to public Wi-Fi portals
On airports, hotels, and cafes, a captive portal may intercept your first request before allowing full internet access.
This can trigger certificate warnings because Chrome expects an encrypted connection but receives a redirect page instead.
Open a plain HTTP page such as a news site or the network’s own login page to complete the captive portal sign-in, then return to the HTTPS site.
9. Inspect the certificate details
Chrome lets you view certificate information from the warning page or the padlock area when the site loads.
Review the issuer, expiration date, and hostname to understand the mismatch.
- Expired certificate usually means the website owner must renew it
- Hostname mismatch means the certificate does not cover the exact domain
- Untrusted issuer may point to a private certificate or missing root CA
10. Reset network settings if local networking is corrupt
Damaged DNS caches, misconfigured adapters, or network stack issues can contribute to loading the wrong certificate or reaching the wrong server.
Restarting your router and resetting network settings can help.
- Flush DNS on your device if supported
- Restart the router or modem
- Reconnect to the network and test again
How to handle Chrome certificate error on a site you own
If you manage the website, the fix usually happens on the server side.
Check the certificate chain, domain coverage, and renewal automation in your hosting control panel or certificate manager.
Server-side checks that matter most
- Confirm the certificate is not expired
- Verify the certificate covers the exact domain and subdomains you use
- Install the full intermediate chain from your CA
- Redirect all HTTP traffic to HTTPS properly
- Test the site with SSL Labs or a similar certificate scanner
Popular certificate providers such as Let’s Encrypt, DigiCert, GlobalSign, and Sectigo each provide renewal guidance, but the core goal is the same: present a complete and trusted TLS chain to the browser.
When it is safe to bypass the warning
In most cases, it is better to fix the cause than click through the warning.
A bypass may be acceptable in a private development environment using a self-signed certificate, but it should not be used for banking, email, or any site that handles sensitive data.
If you are testing a local app, consider adding your development certificate to the system trust store or using a trusted local CA tool instead of ignoring the warning.
How to reduce future certificate errors
- Keep Chrome updated on all devices
- Enable automatic system time synchronization
- Renew website certificates before expiration
- Use reputable certificate authorities
- Monitor certificate expiration with alerts
- Review antivirus, proxy, and VPN settings after software changes
Good certificate hygiene prevents most browser trust issues and makes HTTPS connections more reliable across desktop and mobile devices.