ERR_CERT_AUTHORITY_INVALID explained

ERR_CERT_AUTHORITY_INVALID means the browser cannot build a chain to a trusted root—fix the bundle and renew if the leaf is also expired.

Teams sometimes chase expiry when the real issue is an unknown issuer or private CA on a public site. Still inspect dates after you fix the chain, because renewals often introduce both problems at once.

A freshly issued public cert with only the leaf installed triggers authority errors immediately, which can look like an outage even when notAfter is years away—or mask that the old leaf was expired.

First response

ERR_CERT_AUTHORITY_INVALID means the chain does not anchor to a trusted public CA. Separate expiry from issuer problems, fix the bundle, and renew if the leaf certificate is expired.

Search interest in ERR_CERT_AUTHORITY_INVALID rises when the leaf notAfter on the hostname customers type is already in the past. Clients cannot rewrite server certificate dates; they only accept chains that pass PKIX checks at handshake time.

For ERR_CERT_AUTHORITY_INVALID explained, prove the failure from outside your office VPN before you change application code, purge caches, or ask end users to reboot. Capture the broken serial number and notAfter, renew on the listener that actually terminates that name, reload every node in the path, then re-run the same OpenSSL and browser checks that opened the incident.

Escalations for err-cert-authority-invalid should cite fresh openssl issuer= lines compared against Mozilla trust store expectations output before anyone edits client code or blames Wi‑Fi. ERR_CERT_AUTHORITY_INVALID means the chain does not anchor to a trusted public CA. Separate expiry from issuer problems, fix the bundle, and renew if the leaf certificate is expired. When ERR_CERT_AUTHORITY_INVALID masking date errors clusters around Clients when issuer is untrusted, the expired material is usually bound to listeners presenting self-signed or private CA material on public DNS instead of a mysterious platform bug. Executive summaries need the public hostname and current notAfter, not screenshots from a VPN-split test laptop.

See also ERR_CERT_COMMON_NAME_INVALID hostname errors and Multi-domain SAN certificate: one name expired?.

What this error means

Chromium shows authority invalid when no path leads to a trusted root with valid signatures. Expired intermediates also produce trust failures even if the leaf dates look valid.

Separate symptoms: authority invalid from missing intermediates, date invalid from expiry. openssl -showcerts and -issuer lines clarify which you face.

Serve the CA full chain, renew expired material, reload terminators, and confirm the padlock shows a known public CA.

In PKIX terms, Clients when issuer is untrusted treat the TLS Certificate message as authoritative: signatures must verify, each link must be within notBefore/notAfter, and only then does name matching run against CN and SAN. When the leaf expired, ERR_CERT_AUTHORITY_INVALID masking date errors is expected even if the issuer is publicly trusted. Guides titled err cert authority invalid still require reading dates on every certificate the server sends, including forgotten cross-sign intermediates.

Triage for err cert authority invalid should reject quick myths: flushing DNS or rebooting laptops does not move server notAfter forward. It is not proof the whole internet is broken when other HTTPS sites load for Clients when issuer is untrusted. It is not interchangeable with registrar billing lapses unless revalidation fails later. It is not fixed by turning off TLS at the load balancer while marketing keeps publishing https:// links. Validated externally, openssl issuer= lines compared against Mozilla trust store expectations must show fresh dates on listeners presenting self-signed or private CA material on public DNS before you close the incident.

Common causes

These patterns appear often during ERR_CERT_AUTHORITY_INVALID incidents. They are not exhaustive, but they explain why renewal looked finished internally while strangers still received expired material.

Runbooks for err cert authority invalid most often break at handoff: certbot or a vendor portal issued new certs, but listeners presenting self-signed or private CA material on public DNS never received a reload. Teams tracked PEM files in git while production continued serving the previous listener binding. OV renewals waited on legal approvers until ERR_CERT_AUTHORITY_INVALID masking date errors became customer-visible. Inventory spreadsheets omitted the hostname that Clients when issuer is untrusted actually call during peak traffic.

Architecture amplifies err cert authority invalid: multiple regions, canary pools, or blue/green deploys can leave one ASG member presenting yesterday's fullchain. Shared IP default certificates silently terminate vanity hostnames without dedicated SNI rules. Mounted TLS secrets updated on disk while Envoy or nginx workers kept the old chain until signaled. ERR_CERT_AUTHORITY_INVALID means the chain does not anchor to a trusted public CA becomes harder to debug when only a fraction of Clients when issuer is untrusted hit the stale anycast node.

Measurement gaps complete the story for err cert authority invalid. Synthetic monitors that disable certificate verification greenlit deploys that fail for real Clients when issuer is untrusted. Redirect maps hid which hop expired until operators ran openssl issuer= lines compared against Mozilla trust store expectations per hostname. Dashboards celebrated TCP uptime while notAfter crossed midnight UTC without a page. Post-mortems should ask whether CT logs or stapled OCSP would have warned days earlier.

Confirm from the outside

OpenSSL

echo | openssl s_client -connect HOST:443 -servername HOST 2>/dev/null | openssl x509 -noout -dates -subject -issuer

Check both chain depth and whether any returned cert has past notAfter.

How to read the output

Start with openssl issuer= lines compared against Mozilla trust store expectations against the live customer hostname, capturing the leaf presented after SNI selection. Interpret notBefore= and notAfter= first: past notAfter guarantees failure for ERR_CERT_AUTHORITY_INVALID masking date errors regardless of pretty issuer branding. Next read subject= and any X509v3 Subject Alternative Name extension for alignment with the URL bar. Finally note issuer= so you know whether renewal changed intermediates; record serial numbers in the ticket for post-deploy diffing.

curl

curl -vI --connect-timeout 10 https://HOST/ 2>&1 | grep -Ei 'expire|SSL certificate|subject:|issuer:'

curl may say unable to get local issuer certificate; compare with browser authority error.

Browser spot-check

Certificate viewer shows which issuer is untrusted; note if leaf dates are expired too.

Fix checklist

Work this list in order for err_cert_authority_invalid explained. Each step should produce evidence (command output, timestamps, serial numbers) you can paste into the incident ticket.

1. Capture -showcerts output externally.
2. Install CA-provided fullchain on listener.
3. Replace expired intermediates if any.
4. Renew leaf if notAfter is past.
5. Remove old private CA files from public listeners.
6. Reload web servers and ingress controllers.
7. Validate in clean browser profile.
8. Document correct bundle path in IaC.

Roll out and verify

Procurement for err cert authority invalid begins with a reissue that lists every hostname Clients when issuer is untrusted need, including forgotten admin and callback URLs. Validate CSR/key pairs, download CA bundles, and schedule work on listeners presenting self-signed or private CA material on public DNS during a staffed change window. If automation handles ACME, prove challenges use the same DNS names customers resolve publicly, not internal-only labels.

Installation for err cert authority invalid means concatenating leaf and required intermediates the way your stack documents, then touching every node that terminates the name. Reload web servers, recycle ingress pods, or update cloud listener objects so data planes read new bytes. For load balancers, sync default and per-host certificates so SNI cannot fall back to expired defaults. Repeat openssl issuer= lines compared against Mozilla trust store expectations until fingerprints or serials change everywhere responders tested earlier.

Verification for err cert authority invalid must mimic strangers: external synthetics, mobile carriers, and CI jobs without corporate trust roots. Confirm ERR_CERT_AUTHORITY_INVALID masking date errors disappeared for Clients when issuer is untrusted on flows heavier than GET /. Restore any strict TLS, HSTS, or CDN SSL modes relaxed during firefighting. Feed the hostname into continuous notAfter monitoring with thresholds well before the next CA-enforced renewal cliff.

What to automate

Certificate files on disk lie. Automate live TLS checks on the exact hostname and port users hit, including redirects and the certificate presented after TLS terminates on a load balancer or CDN. Pair certificate notAfter with RDAP domain registration expiry so re-validation is not blocked by a lapsed registrar.

Alert when issuer DN changes without planned deployment. Schedule alerts at 30, 14, 7, and 1 day before expiry so on-call has runway for ACME failures, manual OV revalidation, or change windows. Services such as ssldays can run external checks and renewal reminders without replacing your CA workflow.