Revoke ssl but files are deleted

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:
sudo certbot delete --cert-name

certbot revoke --cert-path /etc/letsencrypt/archive/cheaptextbo

It produced this output:
certbot: error: argument --cert-path: No such file or directory
You have new mail in /var/mail/root

My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know):
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
certbot 0.31.0

That file path appears to have a space in it. What is the output of
ls -al /etc/letsencrypt/archive/

Hi @LinkOrchard

if you delete a certificate, there is no need to revoke it.

And you don’t need to revoke a certificate if the private key isn’t stolen.

1 Like

Hi @JuergenAuer ok that is good news! But the new host says the old cert is still there?
How do we check the SSL on

Read the output -

You have already created three certificates

Issuer not before not after Domain names LE-Duplicate next LE
Let’s Encrypt Authority X3 2019-08-13 2019-11-11
1 entries duplicate nr. 3
Let’s Encrypt Authority X3 2019-08-13 2019-11-11
1 entries duplicate nr. 2
Let’s Encrypt Authority X3 2019-08-12 2019-11-10
1 entries duplicate nr. 1
Let’s Encrypt Authority X3 2019-06-06 2019-09-04
1 entries

but you use a self signed certificate:
185 days expired,,,, - 5 entries

So install your new certificate. Hope you didn’t delete it, there is a rate limit.

This is the one at the new host. Is that still active? She kept on saying she could not put on the SSL because the old one was there.

I did not delete this ssl @JuergenAuer … is cert still there? Could you please also tell me what is the cert limit per domain.

Thank you!

That’s a self signed and expired certificate. And you have a loop, so it’s impossible to use your site.


1 Like

And you have a loop, so it’s impossible to use your site.

How do I get rid of this @JuergenAuer ?

Domain is propagating to a new host, hostgator, I am going to to do what I should of done and buy an SSL. Right now I am paying if anyone can help me fixit.

Please check the output of

There is a direct loop https + non-www -> https + non-www.

Thanks @Juergen – I think that issue of looping is caused by propagation issues. The domain was at networksolutions and I changed the nameservers to hostgator a few hours ago only.

The person in hostgator said they were able to set up new SSL, likewise also for

Thanks for your help, any further advice or help appreciated!

@Juergen the server was spitting out certs.

The loop is now fixed, that’s good.

Both domains have the same problem: There is only a certificate with the non-www version, the www-version isn’t included.

But you have www A records, so the www version isn’t secure -
expires in 89 days - 1 entry

Maybe a problem if users add www.

1 Like

Thank you again @JuergenAuer we are doing some work on this tonight, and hopefully we can fix this. Great news the loop is fixed.

I think at DigitalOcean we always force the www- website on to https:// using the virtual hosts – does this not fix the issue?

Best regards,


1 Like

That doesn’t help. A certificate with the www-domain name is required, so the redirect https + www -> https + non-www can work.

First comes the certificate, then the server is able to send the http status 301 - Redirect.