Created
May 27, 2016 06:38
-
-
Save jennimckinnon/6da2a3cd69cd779d391349ca76a29088 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
certbot revoke -d your-site.com -d your-site.net |
For the letsencrypt
command it works similarly:
letsencrypt revoke --cert-path /etc/letsencrypt/live/mydomainname.com/fullchain.pem
Why is there so many --x-path options, for revoke there seems to be a mismatch.
There is both --cert-path and --chain-path in options, but for revoke, we pass the fullchain.pem but we use the --cert-path option, why is that?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Little bit late, but here it is ))
./certbot-auto revoke --cert-path /etc/letsencrypt/live/your-domain.com/fullchain.pem
or
./certbot revoke --cert-path /etc/letsencrypt/live/your-domain.com/fullchain.pem
For me worked 1st one.
For sure u can add " -d your-site.com " in the middle.
Note !!!
Revoked serts still shown as valid in Chrome. Use Firefox )))
details below
https://community.letsencrypt.org/t/revoked-certs-not-showing-as-revoked-in-browsers/11531/7