How to Fix the ERR_CERT_VALIDITY_TOO_LONG Error (Quick Guide)

The ERR_CERT_VALIDITY_TOO_LONG error in Chrome appears when an SSL certificate exceeds the maximum allowed validity period. Since September 2020, most browsers limit certificate lifespan to 398 days. Anything beyond that will trigger a net::err_cert_validity_too_long or certificate validity too long error.

This guide shows you how to fix or avoid the issue in both local setups and live websites.

What Causes the Certificate Validity Too Long Error?

• Browser Policy Change: Modern browsers like Chrome and Safari now enforce stricter certificate policies. Any SSL certificate valid for more than 13 months (398 days) is rejected.
• Misconfigured SSL Certificates: Some web hosts or self-signed certs may still use 2–3 year durations by default.
• Local Development with Long Expiry: When generating certificates for local environments (using OpenSSL or mkcert), devs often use long-term validity by mistake.

How can I fix the Chrome certificate validity too long error? 

1. Update your system time

If the clock on your computer is not in sync with the server, it could result in a wrong certificate expiration date. Once Chrome detects your computer’s clock is incorrect, it will display an error message. 

This may have happened if you have traveled recently and not reset your time and date settings to your current time zone. You can manually do so through the control panel.

2. Update your OS/browser

This is probably the easiest solution, but if you haven’t updated your operating system in a while, it might be time to do so. Using an older version of Windows or macOS may bring up bugs and errors with third-party software such as Chrome. 

If you’ve updated your OS and still have issues with Chrome not loading websites properly, it might be time for another update — specifically for Chrome itself. 

This can happen if there are bugs in the browser code itself or if security updates are needed to ensure that users’ data remains safe from hackers trying to steal login information and other sensitive data.

3. Clear SSL cache 

1. Hit the Windows key, type Control Panel in the search bar and click Open.

   

2. Navigate to Network and Internet.

   

3. Click on Internet Options.

   

4. Go to the Content tab and hit the Clear SSL state button.

   

5. Retry your site again.

Read more about this topic

• Chrome Emergency Update Fixes Actively Exploited Zero-Day Vulnerability
• VoidStealer Malware Exploits Chrome Memory to Extract Encryption Keys
• Google Patches Two Chrome Zero-Day Vulnerabilities in Emergency Security Update
• Google Expands Gemini-Powered Chrome Features to India, Canada, and New Zealand
• Google Chrome Doubles Its Release Pace With a Two-Week Cycle

How to disable certificate check in Chrome?

The SSL certificate check is a security feature that helps protect people who visit your website. It prevents your website from being impersonated and encrypts information sent between you and your visitors.

However, it can easily become a nuisance if it continuously blocks websites that are not harmful. You can disable this feature for development purposes or during testing to allow any site to open in Chrome.

Disabling the certificate check will allow you to access blocked sites and download otherwise inaccessible content. To do so, follow the steps below:

1. Find the Google Chrome shortcut on your Desktop, right-click on it and select Properties.

   

2. Navigate to the Target string and add the following string at the end: --ignore-certificate-errors

   

3. Press OK to effect the changes.

Hopefully, you have been able to resolve the Chrome validity certificate too long error with one of our recommended solutions.

You may also experience certificate errors in Microsoft Edge, but you can refer to our detailed guide on how to bypass the issue.

If you have the time, you can also create a self-signed certificate which will go a long way in helping you avoid similar problems in the future.

Let us know of any other solution not mentioned above that may have helped you resolve this issue in the comment section below.