NET::ERR_CERT_REVOKED: why your certificate was revoked and how to replace it

Chrome shows ERR_CERT_REVOKED when a certificate was cancelled before it expired. Find out why it happens, how to check, and how to reissue a clean one.

· 5 min read · By the Spot Downtime team

NET::ERR_CERT_REVOKED means the certificate on the site was cancelled by the authority that issued it, before its expiry date. The dates can look fine and the name can match, but the issuer has said: don't trust this one any more. Firefox words it as SEC_ERROR_REVOKED_CERTIFICATE.

That makes it different from the other certificate errors. An expired certificate needs renewing. An untrusted issuer needs a better chain. A revoked certificate has to be replaced, and renewing the same certificate with the same key won't help.

Why certificates get revoked

The private key may be compromised

If a private key leaks, anyone who has it can impersonate the site. Owners revoke the certificate through their CA to limit the damage. Keys end up in public repositories, backups, old servers and support tickets more often than you'd expect.

The owner revoked it by mistake or during a migration

Someone cleaned up old certificates and revoked one that was still in use, or reissued a certificate and revoked the previous one before every server had the new one. The result is a site that works on some servers and fails on others.

The CA revoked it

Certificate authorities must revoke certificates that were issued incorrectly, even when the site owner did nothing wrong. This can hit many certificates at once: Let's Encrypt revoked millions of certificates in March 2020 after finding a bug in how it re-checked CAA records. Check your email for a notice from the CA, and your certbot or ACME client logs.

An intermediate was revoked

Rarely, the intermediate certificate in your chain is the revoked one. Every site using that chain breaks at once, and the fix is to install the replacement chain from your CA.

How browsers know

Revocation is checked in different ways. Some browsers use pre-compiled revocation lists pushed to the browser, others query the CA with OCSP, and servers can attach a fresh OCSP response themselves (stapling). Because of that, a revoked certificate can show an error in one browser and load fine in another for a while. Don't treat "it works in Safari" as proof that the certificate is fine.

Confirm that revocation is the problem

SSL certificate checkerInspect the certificate and chain a site serves, from outside your network.

From a terminal you can ask the server for its stapled OCSP response:

bash
openssl s_client -connect example.com:443 -servername example.com -status </dev/null 2>/dev/null \
  | grep -A 12 "OCSP response"
# Look for "Cert Status: revoked" (or "good" / "unknown")

If there is no stapled response, query the OCSP URL listed in the certificate, or look the serial number up in your CA's dashboard. Many CAs show the revocation reason there.

Fix: issue a new certificate with a new key

  1. Generate a new private key. If the old one may be compromised, a certificate reissued with the same key is still exposed. Many clients reuse keys only if you ask them to.
  2. Request a new certificate. With certbot, force an immediate reissue:
bash
sudo certbot renew --force-renewal
sudo systemctl reload nginx   # or apache2, caddy, your load balancer
  1. Deploy it everywhere. Servers, load balancers, CDNs, mail servers and any other service that used the old certificate or key. A forgotten server keeps serving the revoked one.
  2. Serve the full chain (fullchain.pem with Let's Encrypt), and verify from outside after the reload.
  3. Find out why it happened. If the key leaked, remove it from wherever it was exposed and rotate other secrets stored next to it.

Visitors can't click through reliably

Some browsers offer a "proceed anyway" link and others, especially for sites with HSTS, don't. Either way, ask visitors not to bypass it. The only real fix is on the server.

Prevent a repeat

  • Keep private keys out of repositories, tickets and chat. Store them with tight file permissions, readable only by the service that needs them.
  • Automate issuance and renewal so replacing a certificate is routine and takes minutes, not an emergency project.
  • Keep an inventory of where each certificate is deployed, so a replacement reaches every server, load balancer and CDN.
  • Make sure the CA can reach you: use a monitored contact address for ACME account and certificate notices.

If you are a visitor

  • Check that your device date and time are right. A wrong clock causes many certificate errors, though it's an unlikely cause of a revoked one.
  • Try another network and browser. If the error disappears, an antivirus or proxy intercepting HTTPS may be involved.
  • Don't enter passwords or payment details on a site with a revoked certificate. Tell the owner instead.

Catch it before customers do

A revoked certificate can strike without warning, so expiry reminders alone won't catch it. A monitor that connects over HTTPS like a browser will fail the check when the connection errors, and tell you within the check interval. Spot Downtime's SSL monitoring also tracks certificate expiry so the boring failures never reach production.

Get new guides by email

Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.

Unsubscribe from any email with one click. See our privacy policy.

Keep reading