NET::ERR_CERT_DATE_INVALID exception: NET::ERR_CERT_DATE_INVALID exception
Sites that support HTTPS (with SSL certificates installed) are more comfortable to use. When the browser reminds you of the NET::ERR_CERT_DATE_INVALID error, it indicates that there is a problem with the certificate and the browser blocks the user from accessing the site. So we need to fix that.
In general, this is a frustrating problem for both site owners and users.
Fortunately, the NET::ERR_CERT_DATE_INVALID problem is very common, and there are many alternative solutions to choose from, and after trying one by one, the problem is usually solved.
In this article, we’ll explain what NET::ERR_CERT_DATE_INVALID is and how it might be rendered in different browsers. Then we’ll give you solutions to try. Finally, two more specific cases.
Now let’s get down to business.
What is theNET::ERR_CERT_DATE_INVALIDThe mistake?
NET::ERR_CERT_DATE_INVALID errors are usually associated with your connection not being private, which is basically the main prompt we see when we encounter this problem. For example, Chrome will display this prompt, but some browsers will display a different prompt, such as Firefox:
In most cases, this error doesn’t really prevent us from visiting the site, we can accept the risk and continue to visit, but it’s not recommended.
Although the NET::ERR_CERT_DATE_INVALID error is not uncommon and can be easily fixed, it indicates a possible threat to the site currently visited.
There are several common reasons for this error:
- Users have problems with their computers, such as computer Settings, anti-virus software or Internet connections.
- There is a problem with the browser used to access the site, either because of a setup problem or because the browser is incompatible with the SSL certificate being used.
- There may also be a problem with the certificate itself, for example, the certificate has expired.
No matter what the cause, this problem affects usage, so you’ll want to fix it quickly. Seeing this error may also make users wonder if your site is secure.
NET::ERR_CERT_DATE_INVALIDTips in different browsers
In Chrome, we usually get error messages like NET::ERR_CERT_DATE_INVALID. In addition, other browsers have different error messages. And different operating systems may see different prompts.
Let’s look at some examples of error messages.
Google Chrome
Chrome will indicate that your connection is not private. You can choose to continue to the site by clicking Advanced, but there is a risk:
There are other SSL certificate related errors in Chrome, as follows:
- NET::ERR_CERT_AUTHORITY_INVALID
- NET::ERR_CERT_COMMON_NAME_INVALID
- NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM
- NTE::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
- SSL CERTIFICATE ERROR
When we see this type of error, we should at least know that it is probably related to SSL certificates. Specific error codes help us locate specific problems.
Firefox
A bright yellow border prompts security warnings in Firefox. As with Chrome, we can ignore the prompt, accept the risk and continue by clicking the advanced button.
Clicking advanced will also give you more information about the error, such as SEC_ERROR_EXPIRED_CERTIFICATE in the picture, which may be one of the following:
- SEC_ERROR_UNKNOWN_ISSUER
- SSL_ERROR_RX_MALFORMED_HANDSHAKE
- MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE
- SEC_ERROR_REUSED_ISSUER_AND_SERIAL
This warning contains specific error codes so that we can locate the root problem more quickly.
Microsoft’s Edge browser
The errors in the Edge browser are essentially the same as those shown in Chrome. However, errors under Edge may include how long the SSL certificate has expired:
Note: Chrome also has an indication of how long it will expire.
In addition to errors in the problem set, you may also have the following prompts:
- DLG_FLAGS_SEC_CERTDATE_INVALID
- DLG_FLAGS_INVALID_CA
- DLG_FLAGS_SEC_CERT_CN_INVALID
- NET::ERR_CERT_COMMON_NAME_INVALID
- ERROR CODE: O
Similarly, Edge can choose to continue access. In some cases, though, the Edge browser may force a resolution that would otherwise be inaccessible.
Note: Some Windows screenshots are not replaced, please forgive me.
Safari
In Safari, the warning is a pop-up box instead of a full-screen prompt. Again, you can click through to potentially threatening sites:
The popover itself doesn’t have much information, but if you want to see more detailed error information, you can click Show Certificate to see more detailed information to diagnose the cause of the problem.
Note: The actual test may have some differences, may be the version of the problem, the effect is shown below.
How do I fix the NET::ERR_CERT_DATE_INVALID error
Previously, we saw the error display of NET::ERR_CERT_DATE_INVALID in different browsers. So let’s fix it.
There are many reasons for this error, and we’ve rounded up 10 possible ones:
- Reload the page
- Don’t use public WIFI
- Check local date and time
- Check whether the certificate has expired
- Upgrade the operating system and browser
- Disable antivirus software
- Checking browser extensions
- Clear caches and cookies
- Clearing SSL Cache
- Modifying a DNS Server
1. Reload the page
Let’s start with the simplest way: refresh the page, or try restarting the browser.
Sometimes the site is just temporarily abnormal, it is recommended to try a quick fix, rather than unnecessary troubleshooting. Although the probability is low, it is possible that the owner of the site is just updating the SSL certificate.
2. Don’t use public WIFI
If the page is still inaccessible after reloading, check the network connection. If you’re using public WIFI, it’s possible that the connection isn’t private. To be safe, disconnect public WIFI connections.
You can use your mobile hotspot to try to access the site again. If the problem is solved, it’s WIFI.
In addition, virtual private networks (VPNS) may be the culprit to this problem, if not, try to use them to see if the error still exists. If you were using a VPN when you encountered this problem in the first place, try turning it off.
3. Check the local date and time
This is also very simple. The browser uses the computer’s local time to verify that the certificate is expired. This error can also occur if the time is incorrectly set.
Even if the time on your computer is set to be automatically synchronized, there can be problems with being out of sync.
For example, if you’ve just traveled across time zones, your computer may not have had time to update. So check to make sure your computer’s date and time are correct, then restart your browser and try to see if you can fix the problem.
4. Check whether the certificate has expired
When this error occurs, it is possible that the SSL certificate of the site does expire and the certificate needs to be updated.
You can view it in the following ways in Chrome: Click the three dots in the upper right corner and choose More Tools > Developer Tools.
Switch to the Security TAB to see if the certificate is valid. Click View Certificate to View more information, such as expiration date:
We can also use Qualys to check whether the certificate is valid. Enter the domain name and submit the query.
The test will take several minutes. The result report returned includes a comprehensive analysis of the SSL certificate configuration and gives letter levels. We need to pay special attention to the expiration date of the SSL certificate.
It is worth mentioning that this method can detect the SSL certificate status of other sites. But even if the certificate expires, there’s no way to notify the site owner. If your site certificate has expired, you need to update the certificate. The web server provider may be able to help with this and may need to update it yourself via the control panel.
Some server providers do not provide a control panel to update the certificate, which can only be done from the command line, in which case we can use Certbot.
First, we need to get Certbot up and running. It automatically updates the free SSL certificate before it expires:
No matter how you update your certificate, it’s a good idea to have a reminder on your calendar so that you can update your certificate before it expires.
5. Update the operating system and browser
In general, it is best to keep our operating system versions up to date, as some older versions may be obsolete. And some SSL certificates no longer work on older operating systems.
If you are using an older version of the operation, you will encounter NET::ERR_CERT_DATE_INVALID more and more times over time.
The same goes for older browsers. If you haven’t updated your browser in a while, try updating your browser to solve the problem. Sometimes, even if the browser is up to date, uninstalling and installing may solve the problem.
6. Disable antivirus software
Sometimes, certain configurations of antivirus software can cause problems. So, when this problem occurs, try disabling the antivirus software before visiting the site. Remember to force a browser refresh.
If the problem is detected, you can try to upgrade the antivirus software first. If the problem persists, contact the antivirus software support team.
7. Check browser extensions
Third-party extensions to Chrome also often cause design problems. This approach takes some time because testing depends on the number of plug-ins installed.
Disable the plug-ins one by one, then revisit the site to test. If the plug-in that triggered the error is found, it is good to remove the plug-in.
8. Clear the cache and cookies
Clearing the cache may also take some time to try. To determine if clearing the cache helps, you can try a few things first.
First, try stealth mode. If that doesn’t work, try another browser. If other options work, clearing the browser cache will mostly solve the problem.
For details about how to clear the cache in different browsers, see the following links:
- Clear browser cache in Chrome
- Clear the browser cache in Firefox
- Safari clears the browser cache
- Clear the browser cache in Internet Explorer
- Clear browser cache under Edge
- Clear browser cache under Opera
After clearing the cache and cookies, try restarting the browser again and accessing the page to see if this works.
9. Clear SSL cache
If clearing the browser cache doesn’t work, try clearing the SSL cache. The SSL cache stores the certificates of visited sites so that the next visit is faster.
However, this can also result in the browser reading from the cache when the certificate is updated and not getting the latest certificate.
To clear THE SSL cache on Windows, open the Control Panel and select Internet options. Once opened, the button to clear SSL status can be found in the Content panel.
Restart the browser again and try again. If that doesn’t solve the problem, then the last option is left.
If you are using macOS, you will need to delete SSL certificates previously accepted on insecure sites. You can open Access first and then click Go > Use Tools > Keystring Access.
Then click the type of certificates, untrusted certificates will be marked with a Red Cross, and click Edit > Delete.
10. Modify the DNS server
You may want to adjust your DNS server based on the current configuration by referring to Google Open DNS. However, you are advised to save the current configuration in case you need to change it back.
To change the DNS server in Windows, open the control panel first. Click Internet Options > Network and Sharing Center, and then click Change Adapter Settings. Right-click on the connection information and select Properties.
Then, select IP V4/V6 and click the Properties button. Select specify DNS server address:
If you are using Google Open DNS, enter 8.8.8.8 and 8.8.4.4. Close the window, restart the browser, and view the effect. If not, try Cloudflare DNS with 1.1.1.1 and 1.0.0.1.
If you’re using a MAC, the process is similar, with a few slight differences.
First, open system preferences and click On Networks.
Click the Advanced button on your network connection, then switch to the DNS TAB. Click the (+) button next to the IPv4 or IPv6 address.
Then enter DNS server, click OK, and then click Apply.
If you already use Google Open DNS, you can also try using your network provider’s DNS server. Simply remove Google DNS and select Automatically get DNS server.
WordPressNET::ERR_CERT_DATE_INVALIDerror
If you run into a setup error on WordPress and none of the above 10 methods can solve it, you can try the following methods:
- If the SSL certificate is installed by the server provider, contact them to resolve the issue.
- If you installed your SSL certificate yourself, try reinstalling it.
- Ensure that HTTPS configuration for the site is enabled.
- Make sure the URL you visit is up to date.
If you can’t, don’t hesitate to go to the WordPress community for help. There is also a wealth of documentation to find in the community.
If you can’t find a solution, contact the certificate issuer, who should be able to help you figure out what the problem is.
Let ‘s EncryptNET::ERR_CERT_DATE_INVALIDerror
Let’s Encrypt provides free SSL certificates that can be applied for by anyone who has a domain name. However, the certificate is only valid for 90 days. Therefore, your certificate is more likely to expire than if you use an advanced certificate obtained elsewhere.
When the Let’s Encrypt certificate expires, the operation of the update is dependent on the server provider.
If you are using Kinsta, you can easily install the free Let’s Encrypt certificate on the dashboard. Updates tend to happen automatically without the user having to worry about them.
Some platforms do not have access to Let’s Encrypt, so you need to update it manually. Although Let’s Encrypt has no official support team, we can always check the community forums for help. There will be plenty of information and knowledgeable volunteers to help us research possible solutions.
conclusion
NET::ERR_CERT_DATE_INVALID Errors have many potential causes, and troubleshooting is often cumbersome. However, it is vital to deal with the problem quickly. If we ourselves see this error on our own site, then others may also encounter this error.
Since there are many reasons for this error, we’ve provided you with 10 solutions to try. Try refreshing the site and correcting the local time first. Then try something more, such as clearing SSL caches or testing browser plug-ins.
If you like, please scan the code to follow my public account. I will accompany you to read regularly and share some other front-end knowledge.