NET::ERR_CERT_REVOKED Browser Origin: On your device Last updated 15 Oct 2026

Chrome: Your connection is not private — NET::ERR_CERT_REVOKED (the certificate was revoked)

The site’s TLS certificate has been revoked by the certificate authority, so browsers refuse to trust it.

Exact message you may see certificate has been revokedThe certificate for this site was revoked
Explore the map of this error Full error map →
Seen on: Chrome Edge

Meaning

Revocation happens when a private key leaks, the certificate was issued wrongly, or the owner asked for it. Visitors cannot safely proceed. Owners must issue a new certificate (new key) and install it everywhere (web server, load balancer, CDN origin).

Common causes

  • Private key compromised and certificate revoked
  • Certificate mis-issued and revoked by the CA
  • Old certificate still installed after a replacement
  • Intercepting proxy using a revoked intermediate

⚡ Quick fix

  1. Owners: reissue the certificate with a new private key and install the full chain
  2. Visitors: do not bypass the warning; contact the site owner
  3. Check the certificate status with an online SSL checker

Detailed fix by platform

Linux

  1. openssl s_client -connect example.com:443 -servername example.com </dev/null | openssl x509 -noout -serial -dates -issuer then check the serial on the CA's revocation page
  2. With Let's Encrypt: sudo certbot renew --force-renewal

How to diagnose

  1. Certificate — Which serial and issuer?
  2. Install — Is the new chain deployed on every endpoint?
  3. Key — Was the old key rotated?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

525 — Cloudflare Error 525: SSL Handshake Failed (Cloudflare)525526 — Cloudflare Error 526: Invalid SSL Certificate (Cloudflare)526A TLS error caused the secure connection to fail — Safari: Safari Can’t Open the Page — A TLS error caused the secure connection to fail (Browser)A TLS error caused th…Challenge failed for domain — Let’s Encrypt / Certbot: Challenge failed for domain example.com — Invalid response from http://example.com/.well-known/acme-challenge/x: 404 (SSL / TLS)Challenge failed for …ERR_CERT_AUTHORITY_INVALID — NET::ERR_CERT_AUTHORITY_INVALID (Your connection is not private) (JavaScript)ERR_CERT_AUTHORITY_IN…ERR_CERT_DATE_INVALID — NET::ERR_CERT_DATE_INVALID (certificate expired) (JavaScript)ERR_CERT_DATE_INVALIDERR_CONNECTION_CLOSED — Chrome: This site can’t be reached — example.com unexpectedly closed the connection. ERR_CONNECTION_CLOSED (Browser)ERR_CONNECTION_CLOSEDERR_SSL_OBSOLETE_VERSION — Chrome: Connection not secure — ERR_SSL_OBSOLETE_VERSION (old TLS 1.0/1.1) (Browser)ERR_SSL_OBSOLETE_VERS…NET::ERR_…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.