What’s causing the NET_CERT_SYMANTEC_LEGACY error?
Fixing the NET CERT SYMANTEC LEGACY Error
1. Changing the date & time
As it’s been documented by several affected users, one of the most end-user causes that might end up causing the NET_CERT_SYMANTEC_LEGACY error is an incorrect time & date. If the time & date is way off, the security certificate will not be validated and you will be prevented from accessing the website, even if the Symantec certificate is actually valid. In most cases, the browser requests will fail due to a bad timestamp and the connection will be prevented from being established. If this happens, the only viable fix is to change the date, time and timezone to the appropriate values so that the Symantec security certificate is accepted. Here’s what you need to do: In case you’re still encountering the NET_CERT_SYMANTEC_LEGACY error even after changing the date & time to the appropriate values (or this method wasn’t applicable), move down to the next potential fix below.
2. Downgrade to an older Chrome version
Another potential fix that will allow you to visit websites validated by outdated Symantec security certificates is to downgrade to an earlier version of Chrome – one that does not include the same changes that make the certificate invalid. This might leave your system vulnerable to certain browser explored, but it will help you resolve the issue if you are keen on using Google Chrome. Keep in mind that this change was only enforced with build version 66. So, if you manage to downgrade your version to version 66 or older, Chrome will no longer consider this legacy Symantec certificates are unsafe due to the cipher. Here’ a quick guide on how to downgrade to an older Chrome version in order to resolve the Neterr_Cert_Symantec_Legacy error: In case the same error message is persisting, move down to the next potential fix below.
3. Using a different browser
Keep in mind that Chrome is the main initiator of this error. This happens because starting with Chrome version 66, the browser is configured to automatically distrust Legacy Symantec certificates. If you weren’t comfortable with downgrading Chrome o an older version that is not configured to reject legacy Symantec certificates automatically, the end-point fix you have available is to migrate to a browser that doesn’t have the same security settings. Here are several alternatives that you should consider. When put against Chrome, there aren’t that strict with legacy Symantec certificates and will allow you to visit the same websites without encountering the NET_CERT_SYMANTEC_LEGACY error:
Mozilla FirefoxBrave BrowserOperaVivaldi
4. Contacting the Webmaster
Since the issue originates from a certificate inconsistency, there is a limited number that you can do to circumvent the issue from the end-user point of view. If your date/time isn’t off and you’re not willing to use an older Chrome version (or migrate to a more lenient browser), the only chance of ever accessing that webpage using your current browser is to contact the website administrator and ask him/her to update the security certificate.
Check the Google Chrome Version and the Last Time Chrome UpdatedFix Google Chrome Update Error (Error Code - 7 : 0x80040801)How to Fix Error Code: HTTP Error 431 on Google Chrome?How to Fix ‘Sub-process /usr/bin/dpkg returned an error code (1)’ Error while…
