# Letsencrypt renewal informations data **URL:** \ **Category:** Help\ **Created:** [May 8, 2019, 9:46am UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067 "2019-05-08T09:46:10Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![danjde](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danjde/32/8575_2.png) [@danjde](https://community.letsencrypt.org/u/danjde)\ **Post date:** [May 8, 2019, 9:46am UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/1 "2019-05-08T09:46:10Z")
Hi Friends, I am receiving on 05/05/2019 22:39 e-mail from Letsencrypt where notify me the expiration certificate for domain [3x1t.org](http://3x1t.org), but in the meantime certbot+cron has already renewed it. I’ve seen a lot of post around this issue, but excuse me for my difficulty in understanding, but I would to know if is it possible to customize this behaviour, maybe to receiving these emails only if the renewal is not successful within the last 10/15 days validity? Also, could you suggest me a trick to check on the fly if and when certbot+cron did the renewal correctly (for my heart… 😛 )? Thanks thanks!! Davide ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [May 8, 2019, 10:46am UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/2 "2019-05-08T10:46:23Z")
Hi @danjde > [@danjde](#): > > maybe to receiving these emails only if the renewal is not successful within the last 10/15 days validity? checking your active certificates there are a lot ( [https://check-your-website.server-daten.de/?q=3x1t.org#ct-logs](https://check-your-website.server-daten.de/?q=3x1t.org#ct-logs) ): | Issuer | not before | not after | Domain names | LE-Duplicate | next LE | | --- | --- | --- | --- | --- | --- | | | CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-04-10 10:02:47 | 2019-07-09 10:02:47 | [3x1t.org](http://3x1t.org), [autoconfig.3x1t.org](http://autoconfig.3x1t.org), [autodiscover.3x1t.org](http://autodiscover.3x1t.org), [converse.3x1t.org](http://converse.3x1t.org), [lists.3x1t.org](http://lists.3x1t.org), [mail.3x1t.org](http://mail.3x1t.org), [server.3x1t.org](http://server.3x1t.org), [smtp.3x1t.org](http://smtp.3x1t.org), [upload.3x1t.org](http://upload.3x1t.org), [upload.server.3x1t.org](http://upload.server.3x1t.org), [www.3x1t.org](http://www.3x1t.org), [www.converse.3x1t.org](http://www.converse.3x1t.org) | | | 12 entries | | | | | | | | CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-04-06 07:15:48 | 2019-07-05 07:15:48 | [3x1t.org](http://3x1t.org), [autoconfig.server.3x1t.org](http://autoconfig.server.3x1t.org), [autodiscover.server.3x1t.org](http://autodiscover.server.3x1t.org), [converse.3x1t.org](http://converse.3x1t.org), [lists.3x1t.org](http://lists.3x1t.org), [mail.3x1t.org](http://mail.3x1t.org), [server.3x1t.org](http://server.3x1t.org), [smtp.3x1t.org](http://smtp.3x1t.org), [upload.3x1t.org](http://upload.3x1t.org), [upload.server.3x1t.org](http://upload.server.3x1t.org), [www.3x1t.org](http://www.3x1t.org), [www.converse.3x1t.org](http://www.converse.3x1t.org) | | | 12 entries | | | | | | | | CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-03-26 20:12:33 | 2019-06-24 20:12:33 | [3x1t.org](http://3x1t.org), [autoconfig.server.3x1t.org](http://autoconfig.server.3x1t.org), [autodiscover.server.3x1t.org](http://autodiscover.server.3x1t.org), [lists.3x1t.org](http://lists.3x1t.org), [mail.3x1t.org](http://mail.3x1t.org), [server.3x1t.org](http://server.3x1t.org), [smtp.3x1t.org](http://smtp.3x1t.org), [upload.3x1t.org](http://upload.3x1t.org), [upload.server.3x1t.org](http://upload.server.3x1t.org), [www.3x1t.org](http://www.3x1t.org) | | | 10 entries | | | | | | | | CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-03-08 20:23:38 | 2019-06-06 20:23:38 | [3x1t.org](http://3x1t.org), [autoconfig.3x1t.org](http://autoconfig.3x1t.org), [autodiscover.3x1t.org](http://autodiscover.3x1t.org), [conference.3x1t.org](http://conference.3x1t.org), [conference.server.3x1t.org](http://conference.server.3x1t.org), [lists.3x1t.org](http://lists.3x1t.org), [mail.3x1t.org](http://mail.3x1t.org), [server.3x1t.org](http://server.3x1t.org), [smtp.3x1t.org](http://smtp.3x1t.org), [www.3x1t.org](http://www.3x1t.org) | | | 10 entries | | | | | | | | CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-03-08 19:52:35 | 2019-06-06 19:52:35 | [3x1t.org](http://3x1t.org), [autoconfig.server.3x1t.org](http://autoconfig.server.3x1t.org), [autodiscover.server.3x1t.org](http://autodiscover.server.3x1t.org), [conference.3x1t.org](http://conference.3x1t.org), [conference.server.3x1t.org](http://conference.server.3x1t.org), [lists.3x1t.org](http://lists.3x1t.org), [mail.3x1t.org](http://mail.3x1t.org), [server.3x1t.org](http://server.3x1t.org), [smtp.3x1t.org](http://smtp.3x1t.org), [www.3x1t.org](http://www.3x1t.org) | | | 10 entries | | | | | | | | CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-03-01 10:12:10 | 2019-05-30 10:12:10 | [3x1t.org](http://3x1t.org), [conference.3x1t.org](http://conference.3x1t.org), [conference.server.3x1t.org](http://conference.server.3x1t.org), [lists.3x1t.org](http://lists.3x1t.org), [mail.3x1t.org](http://mail.3x1t.org), [server.3x1t.org](http://server.3x1t.org), [smtp.3x1t.org](http://smtp.3x1t.org), [www.3x1t.org](http://www.3x1t.org) | | | 8 entries | | | | | | | | CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-02-24 20:36:59 | 2019-05-25 20:36:59 | [3x1t.org](http://3x1t.org), [conference.3x1t.org](http://conference.3x1t.org), [conference.server.3x1t.org](http://conference.server.3x1t.org), [lists.3x1t.org](http://lists.3x1t.org), [server.3x1t.org](http://server.3x1t.org), [www.3x1t.org](http://www.3x1t.org) | | | 6 entries | | | | | | | | CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-02-16 15:59:51 | 2019-05-17 15:59:51 | [3x1t.org](http://3x1t.org), [conference.3x1t.org](http://conference.3x1t.org), [conference.server.3x1t.org](http://conference.server.3x1t.org), [server.3x1t.org](http://server.3x1t.org), [www.3x1t.org](http://www.3x1t.org) | | | 5 entries | | | | | | 12 entries, 10 entries, 8 entries etc. Letsencrypt doesn't know which certificate you use. If a certificate isn't renewed (newer certificate with the same set of domain names), a mail is sent. So if you change the set of domain names -\> you will have a mail. ---
**Author:** ![danjde](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danjde/32/8575_2.png) [@danjde](https://community.letsencrypt.org/u/danjde)\ **Post date:** [May 9, 2019, 8:28pm UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/3 "2019-05-09T20:28:17Z")
Thanks [JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer) for your kind explanation! Now it’s more clear for me 😜 Anyway, in general, perhaps for the first year should be disabled the email warning, since several changes are made, at least in my case… Thanks again! Davide ---
**Author:** ![danjde](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danjde/32/8575_2.png) [@danjde](https://community.letsencrypt.org/u/danjde)\ **Post date:** [May 20, 2019, 10:59am UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/4 "2019-05-20T10:59:28Z")
Sorry if I return to the subject, but two thing I would like to understand better: 1. Is it correct that I have these active certificates or should I revoke the obsolete ones (which became obsolete as a result of the addition of domains)? 2. Is it correct the way I add domains or should I run a different command that somehow avoids generating a new certificate every time? Thanks again! Davide ---
**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\ **Post date:** [May 20, 2019, 11:08am UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/5 "2019-05-20T11:08:39Z")
> [@danjde](#): > > should I revoke the obsolete ones The only reason for you to revoke a certificate is if you believe the private key has been compromised. > [@danjde](#): > > should I run a different command that somehow avoids generating a new certificate every time? Once created, certificates are immutable. Thus, the only way to "change" them (add or remove domains, etc.) is to generate a new cert. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [May 20, 2019, 1:15pm UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/6 "2019-05-20T13:15:43Z")
> [@danjde](#): > > Is it correct that I have these active certificates You can delete these not longer used certificates. ```nohighlight certbot certificates ``` then ```nohighlight certbot delete [certificatename] ``` ---
**Author:** ![danjde](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danjde/32/8575_2.png) [@danjde](https://community.letsencrypt.org/u/danjde)\ **Post date:** [May 21, 2019, 8:28am UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/7 "2019-05-21T08:28:05Z")
> [@JuergenAuer](#): > > You can delete these not longer used certificates. > > ```nohighlight > certbot certificates > > ``` Well, but if I run ```nohighlight certbot certificates ``` obtain only one certificate, and not all listed by "[check-your-website.server-daten.de](http://check-your-website.server-daten.de)" is it right this? Thanks again! Davide ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [May 21, 2019, 9:09am UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/8 "2019-05-21T09:09:30Z")
> [@danjde](#): > > Well, but if I run > > ```nohighlight > certbot certificates > > ``` > > obtain only one certificate Your certificates ```nohighlight 3x1t.org, autoconfig.3x1t.org, autodiscover.3x1t.org, converse.3x1t.org, lists.3x1t.org, mail.3x1t.org, server.3x1t.org, smtp.3x1t.org, upload.3x1t.org, upload.server.3x1t.org, www.3x1t.org, www.converse.3x1t.org 12 entries ``` are looking like they are not created manual. Looks like a control-panel generated certificate. If you see only one certificate, then it's ok. Olders may be in the archive folder or --expand or something else was used. ---
**Author:** ![danjde](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danjde/32/8575_2.png) [@danjde](https://community.letsencrypt.org/u/danjde)\ **Post date:** [May 22, 2019, 7:32pm UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/9 "2019-05-22T19:32:44Z")
This certificate (with 12 entries) was created automatically by my own cron daemon, using the following code: `certbot certonly --cert-name server.3x1t.org --webroot -w /var/www/letsencrypt --email 3x1t@3x1t.org --deploy-hook /usr/local/bin/certbot-deploy-hook --expand -d server.3x1t.org -d 3x1t.org -d www.3x1t.org -d lists.3x1t.org -d smtp.3x1t.org -d mail.3x1t.org -d autodiscover.server.3x1t.org -d autoconfig.server.3x1t.org -d upload.server.3x1t.org -d upload.3x1t.org -d www.converse.3x1t.org -d converse.3x1t.org -d _xmpp-server._tcp.conference.3x1t.org -d _xmpp-server._tcp.conference.3x1t.org -d _xmpp-server._tcp.conference.server.3x1t.org -d _xmpp-server._tcp.conference.server.3x1t.org` > [@JuergenAuer](#): > > If you see only one certificate, then it’s ok. Olders may be in the archive folder or [..] Yes, but why Letsencrypt email reminder send my notification expiry about certificates that I cannot see using " certbot certificates"? And Eventually can I "purge" Letsencrypt email reminder for those obsolete certificates (that I cannot see)? Many thanks again!! 🙂 Davide ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [May 22, 2019, 7:34pm UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/10 "2019-05-22T19:34:39Z")
> [@danjde](#): > > Yes, but why Letsencrypt email reminder send my notification expiry about certificates that I cannot see using " certbot certificates"? That's simple. You use the `--expand` parameter, so Certbot overrides the existing configuration. But Letsencrypt doesn't know what your client is doing. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [June 21, 2019, 7:34pm UTC](https://community.letsencrypt.org/t/letsencrypt-renewal-informations-data/93067/11 "2019-06-21T19:34:48Z")
Closed on June 21, 2019, 7:34pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.