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
}
```
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @gertcuykens on GitHub (Jul 5, 2016).
Currently
./letsencrypt.sh -r cert.pemdoes not rename certificates that are already revoked by a ohter client.Suggest to also rename with
.pem-revokedthem when you get the following error.@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.