rename certificates with status 409 already revoked to .pem-revoked #121

Closed
opened 2025-12-29 00:25:17 +01:00 by adam · 1 comment
Owner

Originally created by @gertcuykens on GitHub (Jul 5, 2016).

Currently ./letsencrypt.sh -r cert.pem does not rename certificates that are already revoked by a ohter client.

Suggest to also rename with .pem-revoked them when you get the following error.

Revoking ..
  + ERROR: An error occurred while sending post-request to https://acme-staging.api.letsencrypt.org/acme/revoke-cert (Status 409)

Details:
{
  "type": "urn:acme:error:malformed",
  "detail": "Certificate already revoked",
  "status": 409
}
Originally created by @gertcuykens on GitHub (Jul 5, 2016). Currently `./letsencrypt.sh -r cert.pem` does not rename certificates that are already revoked by a ohter client. Suggest to also rename with `.pem-revoked` them when you get the following error. ``` Revoking .. + ERROR: An error occurred while sending post-request to https://acme-staging.api.letsencrypt.org/acme/revoke-cert (Status 409) Details: { "type": "urn:acme:error:malformed", "detail": "Certificate already revoked", "status": 409 } ```
adam added the enhancementhelp wanted labels 2025-12-29 00:25:17 +01:00
adam closed this issue 2025-12-29 00:25:17 +01:00
Author
Owner

@lukas2511 commented on GitHub (Jul 5, 2016):

Yes, this is because the error message isn't (yet) parsed in any way, and without any knowledge on why revocation failed it doesn't make sense to move certificates around.

@lukas2511 commented on GitHub (Jul 5, 2016): Yes, this is because the error message isn't (yet) parsed in any way, and without any knowledge on why revocation failed it doesn't make sense to move certificates around.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#121