How to Fix the NET::ERR_CERT_AUTHORITY_INVALID Error
NET::ERR_CERT_AUTHORITY_INVALID means the browser does not trust the site’s SSL certificate, because it was not signed by a recognised authority. You see a “Your connection is not private” warning. The cause is usually a self-signed or misconfigured certificate, a wrong device clock, or security software swapping the certificate. Here is how to fix it.
What the error means
Browsers only trust certificates signed by a known certificate authority. When a site presents one that isn’t – self-signed, incomplete, or for the wrong name – the browser blocks it and shows this warning to protect you. It is about trust in the certificate, not a virus or a hack.
Quick fixes to try first
- Check your device’s date and time. A wrong clock makes valid certificates look untrusted. Set it to update automatically.
- Open the site in Incognito. If it works, clear your browser cache and disable extensions.
- Check your antivirus or firewall for an “HTTPS scanning” option. It can replace the real certificate with its own – switch it off and retry.
- Update your browser and operating system so their list of trusted authorities is current.
If the website is yours
- Install a certificate from a trusted authority. On JetHost, run AutoSSL to get a free Let’s Encrypt certificate – see free Let’s Encrypt SSL. Don’t use a self-signed certificate in production.
- Include the full chain. A missing intermediate certificate makes some browsers distrust an otherwise valid one, so install the CA bundle too.
- Match the certificate to the name. It must cover the exact address, including www and any subdomains.
On JetHost hosting
On JetHost shared hosting, AutoSSL installs and renews a trusted free certificate, so this warning is rare once it has run. If it persists after a certificate is in place, open a ticket and we’ll check the certificate and its chain. For a related warning, see ERR_SSL_PROTOCOL_ERROR; to weigh options, see whether you need a paid SSL certificate.
JetHost Experts Tip
If one visitor sees the warning but others don’t, suspect their clock or their antivirus – not your certificate. A wrong system date is the most common false alarm here.
Frequently asked questions
Be careful. On a site you don’t control, the warning means the connection can’t be verified. Only proceed if it’s your own site and you know why the certificate is untrusted.
A wrong clock, an outdated browser, or antivirus HTTPS scanning on one device can cause it while everyone else loads the site fine.
Usually a missing intermediate certificate. Install the full CA chain, or run AutoSSL to issue a complete, trusted certificate.
New Hosting Plan with 80% OFF
Upgrade your website’s home without the heavy bill. Get new hosting plan with a huge 80% discount. Get free SSL, email accounts, and a control panel to manage your site. Enjoy fast performance, secure environment, and 24/7 support – all in one affordable package.
Need more help?
Still seeing the certificate warning on a site you host with us? Open a ticket through Client Area → Support Tickets and we’ll check the certificate and its chain.


