In short. This error means the browser does not recognise the organisation that issued your website's security certificate (its proof of identity, which makes the secure connection possible), or that the certificate is incomplete or signed by the site itself. Your visitors see a warning and may leave without entering your site. It is up to you, or to your hosting provider or web provider, to install a recognised certificate, often a free one. Usually allow a few minutes of configuration.
NET::ERR_CERT_AUTHORITY_INVALID means Chrome does not recognize the authority that signed the site's certificate. On the site side, two causes come up almost every time: a self-signed certificate (created by the server itself, not by a recognized authority), or an incomplete chain (the server does not send the intermediate certificates). The fix: install a certificate from a recognized authority, with its full chain.
Last verified: November 18, 2026, in the Chromium and Firefox source code.
What your visitors see
Chrome shows "Your connection is not private", with the code NET::ERR_CERT_AUTHORITY_INVALID. Under Advanced, its explanation reads as follows (Chromium text):
This server could not prove that it is your-domain.com; its security certificate is not trusted by Chrome. This may be caused by a misconfiguration or an attacker intercepting your connection.
Firefox shows "Warning: Potential Security Risk Ahead", with the code SEC_ERROR_UNKNOWN_ISSUER or MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT. Its text names the three possible causes: the certificate issuer is unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates.
Step 1: identify the cause
Run our free SSL certificate check, or open the certificate from the browser (padlock or warning, then certificate details).
- Issuer and subject are identical: the certificate is self-signed. This is common right after installing a server, an admin panel or a device (NAS, router): a temporary certificate is created until the real one arrives.
- The issuer is a known authority (Let's Encrypt, Sectigo, DigiCert, GlobalSign…) but the error persists: the chain is probably incomplete. Some browsers complete the missing chain themselves, others do not: the error may then appear on some devices only.
- The issuer is your company's name or an antivirus: the certificate comes from an internal authority or from software that inspects connections. It is only recognized on machines configured for it.
Step 2: install a recognized certificate
- Shared hosting: enable the free certificate offered by the host (often Let's Encrypt) for the domain concerned, in place of the default certificate.
- Server you manage: get a certificate from a recognized authority, for example for free with an ACME client such as certbot.
- Internal device or application: if the service is public, it needs a certificate from a recognized authority. If it is internal, it should not be exposed on the Internet.
Step 3: serve the full chain
The server must send the site's certificate and the authority's intermediate certificates. With Let's Encrypt and certbot, this means configuring the web server with the fullchain.pem file, not cert.pem alone. With a purchased certificate, the authority provides a chain file (often called bundle or chain) to install with the certificate.
Do not include the root certificate: it is already in browsers.
Step 4: check
- Run the free tool again: the chain should be complete and the issuer recognized.
- Test the site from several browsers and a phone: an incomplete chain sometimes passes on a computer and fails on a mobile.
Check your certificate for free. AttackScout reads your certificate from the Internet, like a browser, and spots an untrusted certificate or an incomplete chain. Check my domain
Frequently asked questions
The site works on my computer but not on a customer's phone. Why?
It is the typical sign of an incomplete chain: your browser may have already cached the missing intermediate, the customer's has not. Install the full chain.
Can I ask visitors to accept the certificate?
No. A visitor cannot tell your self-signed certificate from an attacker's: that is exactly what the warning protects against.
Is a free certificate less recognized than a paid one?
No. Browsers recognize Let's Encrypt like the paid authorities. The difference lies in the service and the type of validation, not in the warning.
Sources
Accessed on 11/18/2026.
- Chromium,
IDS_CERT_ERROR_AUTHORITY_INVALID_DETAILS(components/ssl_errors_strings.grdp) and its translations (components/strings/components_strings_<language>.xtb): https://github.com/chromium/chromium/tree/main/components - Firefox,
cert-error-trust-unknown-issuerandcert-error-trust-self-signed(certError.ftl);SEC_ERROR_UNKNOWN_ISSUERandMOZILLA_PKIX_ERROR_SELF_SIGNED_CERT(nsserrors.properties): https://github.com/mozilla-firefox/firefox - Let's Encrypt, certbot documentation (
fullchain.pem): https://eff-certbot.readthedocs.io/en/stable/using.html#where-are-my-certificates