# How to Fix the NET::ERR_CERT_AUTHORITY_INVALID Error

> Canonical: https://jethost.com/kb/how-to-fix-err-cert-authority-invalid/ · Last modified: 2026-10-31T13:35:51+00:00

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

1. Check your device’s date and time. A wrong clock makes valid certificates look untrusted. Set it to update automatically.
2. Open the site in Incognito. If it works, clear your browser cache and disable extensions.
3. Check your antivirus or firewall for an “HTTPS scanning” option. It can replace the real certificate with its own – switch it off and retry.
4. Update your browser and operating system so their list of trusted authorities is current.

## If the website is yours

1. 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](https://jethost.com/kb/lets-encrypt-ssl/). Don’t use a self-signed certificate in production.
2. Include the full chain. A missing intermediate certificate makes some browsers distrust an otherwise valid one, so install the CA bundle too.
3. 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](https://jethost.com/kb/how-to-fix-err-ssl-protocol-error/); to weigh options, see [whether you need a paid SSL certificate](https://jethost.com/kb/do-i-need-a-paid-ssl/).

## 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

**Is it safe to click through the warning?**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.

**Why do other people not see it?**A wrong clock, an outdated browser, or antivirus HTTPS scanning on one device can cause it while everyone else loads the site fine.

**I installed a certificate but still see it. Why?**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](https://jethost.com/web-hosting/ "Web hosting with free SSH access") 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.