Skip to main content
Video tutorial · 1:03

Revoke a certificate

Revocation tells the Certificate Authority the cert is no longer trusted and should be published in CRL/OCSP as revoked. It is a one-way action — you cannot un-revoke, you can only issue a fresh cert. CertAutoPilot calls the issuing ACME CA, records the reason, emits the audit + notification events, and marks the cert as revoked.

Not available for imported certificates

Revocation calls the issuing CA. Imported (bring-your-own) certificates have no CA, so Revoke is rejected for them — use Delete to retire an imported certificate. If the external CA that issued it supports revocation, revoke it there.

When to revoke​

  • Key compromise — the private key has been exposed (bucket leak, HSM incident, lost laptop). Use reason keyCompromise. Browsers honour this with CRLSets / OneCRL escalation.
  • Ownership change — the domain is being transferred and the cert should not remain valid with the previous owner.
  • Decommission — the app is going away; you want to make the cert inert in case it leaks.
  • Subject problem — wrong identifiers, wrong organization details. Use cessationOfOperation or affiliationChanged.
  • Superseded — you reissued with different parameters and want the old cert withdrawn.
Revocation is not the same as deletion

The MongoDB record stays (for audit), the cert is marked revoked, and the CA publishes it in CRL/OCSP. Delete it from CertAutoPilot only after the CA's revocation propagation window has passed (typically 24 hours).

Prerequisites​

  • Revocation needs the operator role or higher. When the project's approval policy gates revocation for an operator, that operator's revocation becomes a request that a project admin approves in My Requests; otherwise operators revoke directly. Admins and owners always revoke directly.
  • For ACME certs the associated account key must still be loaded — it is used to sign the revocation request. Deleting the account before revoking its certs makes revocation impossible from CertAutoPilot.

Revoke​

  1. Go to the certificate detail page.
  2. Click Revoke (top-right actions). An expired certificate can still be revoked — revocation is what tells the CA the key is compromised, which matters regardless of expiry. The button is shown for a certificate that is active or expired, and for one whose renewal is waiting or has failed (renewal_pending, renewal_failed — it still holds its certificate; a queued renewal is cancelled by the revocation) — not for one that is already revoked or still pending, one that was imported rather than issued here, one that came from AD CS (MSCA), or one issued through a CA connector whose vendor cannot revoke through its API (a GlobalSign Atlas certificate can be revoked).
  3. Pick a reason (default Unspecified):
    • Key compromise (1) — the private key was exposed; browsers treat this as severe.
    • Affiliation changed (3) — the subject or organization changed.
    • Superseded (4) — a newer certificate replaces this one.
    • Cessation of operation (5) — the service or domain is retired.
    • Privilege withdrawn (9).
    • CA compromise (2), certificate hold (6), remove from CRL (8) and AA compromise (10) are listed too, but most public ACME CAs refuse them.
  4. Type REVOKE and confirm. A revoke_certificate job enqueues.

Revocation applies to ACME-issued certificates and to certificates from a CA connector whose vendor revokes through its API (GlobalSign Atlas — Atlas accepts key compromise, affiliation changed, cessation of operation and superseded; any other reason is sent as unspecified). Microsoft AD CS (MSCA) and imported certificates, and those of a connector vendor without a revoke call, cannot be revoked through CertAutoPilot — revoke those at the issuing CA directly. Through the API such a request is refused with HTTP 422 and "error": "ISSUER_UNSUPPORTED_OPERATION" (with issuer_type, operation and a message; for a connector also vendor); releases before 1.5.54 answered a plain 400.

What happens​

Before the revocation is queued, the certificate's queued issuance and renewal jobs (a re-issue waiting for its next attempt, a scheduled renewal) are cancelled, so no new certificate can outlive the revocation. While one of them is running, the revocation is refused with a conflict: revoke again once it has finished. A finalize job that has already stored the new certificate (the certificate shows Active again) and is only finishing its clean-up does not block it: the revocation is queued and runs as soon as that job is done. Until the revocation completes, Re-issue and Renew are refused the same way. DNS cleanup and distribution jobs are not touched.

If the CA had already issued a renewal or a re-issue that CertAutoPilot has not stored (a store that failed, or a re-issue cancelled after the CA issued it), that certificate is revoked too, before the certificate in use; a renewal's carries the same key. The revocation only reports success once the CA has revoked both. If the CA refuses the unstored one, the certificate in use is left untouched and the revocation fails with the CA's reason. A revocation that finds the certificate held by another job is re-queued and tried again later.

  1. The worker loads the cert + private key + account.
  2. It signs a revocation request against the CA using the ACME account key.
  3. The CA returns success; the cert state flips to revoked.
  4. A cert.revoked event is written to the timeline and notification rules fire.
  5. Active distributions are NOT automatically rolled back. If the cert is live on an HTTPS endpoint, that endpoint still presents it — you must distribute a replacement cert or explicitly rollback the distribution.
Revocation does not remove the cert from your servers

Browsers eventually learn the cert is revoked (via CRL/OCSP) and refuse to trust it, breaking HTTPS. Always issue + distribute a replacement cert BEFORE revoking the old one, unless you are deliberately taking the service down.

Verify​

  • Detail page shows status: revoked and the reason.

  • Timeline has a cert.revoked event; the audit log records who revoked it and with which reason.

  • Third-party check (several minutes post-revocation):

    openssl ocsp -issuer chain.pem -cert cert.pem \
    -url $(openssl x509 -in cert.pem -ocsp_uri -noout)

    Expected: Cert Status: revoked.

Troubleshooting​

"account key not loaded"​

The ACME account was deleted from CertAutoPilot before its certs were revoked. Recreate an account on the same CA and attach it to the cert (Settings → Certificate Authorities → ACME Accounts → the new one), then try again. Some CAs also accept revocation by presenting the cert's own private key without the account — this path is not currently wired in the UI but is doable via the API.

"already revoked"​

The CA says it is already revoked but CertAutoPilot thinks it is active. Happens if someone revoked via the CA portal directly. There is no Refresh from CA button — an hourly sweep checks certificates against OCSP and then CRL and reconciles the status itself, so leave it and it corrects within the hour.

Revoking one retained version​

Revocation normally applies to the whole certificate. You can instead revoke a single retained historical version: open the certificate's Certificates tab (its version history) and click Revoke on that version's row (the same reason picker and confirmation apply; the row of the version currently served opens the whole-certificate dialog instead). Through the API, pass the version's artifact id:

POST /api/v1/projects/{project}/certificates/{id}/revoke
{ "reason": 1, "artifact_id": "<version id>" } // reason is the NUMERIC RFC 5280 code (1 = keyCompromise); a string is rejected

That version is revoked at the CA and marked revoked in the history, while the certificate itself stays active — useful when an older key leaked but the current one is sound. A revoked version also drops out of rollback eligibility, so nothing can redeploy it. Naming the current version instead falls through to the normal whole-certificate path. A revoked version shows a Revoked tag in the Certificates tab.

An unknown version, a version of another certificate or an already revoked one is refused before anything is queued. A certificate that is not active, expired, renewal_pending or renewal_failed (for example still pending) is refused the same way.

When an operator's revocation needs approval, the request keeps its scope: My Requests shows Revoke scope: Version vN · serial … (or Whole certificate) and the reason, and approving it revokes exactly that. Only one revoke request per certificate can be open at a time.

Revocation detected out of band​

An hourly sweep re-checks certificates against the CA (OCSP first, then CRL). If one was revoked outside CertAutoPilot, the status is reconciled automatically and a notification fires. Retained previous versions are checked too, at most every 24 hours each and 20 per certificate per cycle; a previous version found revoked is marked as such and raises a warning without touching the live certificate.

Revoke opened a request instead of revoking​

The project's approval policy gates revocation for you (you are an operator, listed directly or through a group, or the rule covers all operators). The request is in My Requests; a project admin approves it there, and then you (or the admin) execute it. An admin cannot approve their own request.

See also​

Video tutorial

Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →

Revoke One Certificate Version or the Whole CertificateYouTube ↗