Received renewal email, certbot renew says none to renew

Please fill out the fields below so we can help you better.

My domain is:

I ran this command: certbot renew

It produced this output:
Cert not yet due for renewal

My operating system is (include version):
fedora 25

My web server is (include version):
cert created with certonly

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):

I used the follow command to create the cert:
certbot -d --manual --preferred-challenges dns certonly

How can I use certbot to renew a domain with this configuration? How can I use certbot to print out on the command-line the cert expiration times for all the certs I have created?

1 Like

Hi @gossamer

Managing certificates

To view a list of the certificates Certbot knows about, run the certificates subcommand:

certbot certificates

This returns information in the following format:

Found the following certs:
Certificate Name:
Expiry Date: 2017-02-19 19:53:00+00:00 (VALID: 30 days)
Certificate Path: /etc/letsencrypt/live/
Private Key Path: /etc/letsencrypt/live/


1 Like

I can see that you have a certificate issued for

By default certbot won’t renew certificates until they are close to expiry

You can review the renewal configuration from etc/letsencrypt/renewal folder


1 Like

I already received an email informing me it’s due for renewal. If it expires in nine days, when will I be able to renew it?

Is it possible to extend the time valid to more than 50 or 60 days? Or is this something I should expect to do every few months? With more than ten certs, this could become time-intensive.

Let's Encrypt checks whether your certificate has already been renewed, by checking if you've got a new certificate for the exact same set of domains. According to, your old certificate covered both and, while your new one covers only. (The covered domains for each certificate are listed under "X509v3 Subject Alternative Name"). This isn't considered to be a "renewal" as it's a certificate for a different set of domains, which is why the email was sent.

If you only wanted a certificate for you can safely ignore the email. If you wanted a renewed certificate for both domains, you can obtain one by running the certbot command again, but this time specifying the full list of domains you want covered, e.g.:

certbot -d -d --manual --preferred-challenges dns certonly

Let's Encrypt certificate are actually valid for 90 days, but can't be extended any longer than that. To avoid spending time on renewals, you could maybe try a different validation method (e.g. webroot), or perhaps a different client (e.g., so that you can more easily automate the renewal process.


Thanks so much for spending the time to put this together. I’ll recreate the cert instead for both domains.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.