# Lets encrypt sends mail to refresh certs while this is already done

**URL:** <https://community.letsencrypt.org/t/lets-encrypt-sends-mail-to-refresh-certs-while-this-is-already-done/122585>\
**Category:** Help\
**Created:** [May 13, 2020, 8:24am UTC](https://community.letsencrypt.org/t/lets-encrypt-sends-mail-to-refresh-certs-while-this-is-already-done/122585 "2020-05-13T08:24:09Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Biggydeen](https://avatars.discourse-cdn.com/v4/letter/b/5e9695/32.png) [@Biggydeen](https://community.letsencrypt.org/u/Biggydeen)\
**Post date:** [May 13, 2020, 8:24am UTC](https://community.letsencrypt.org/t/lets-encrypt-sends-mail-to-refresh-certs-while-this-is-already-done/122585/1 "2020-05-13T08:24:09Z")

</div>

Hi,

Got a question about the lets encrypt mail that's being send when certs are due to renewal. I'm getting the following message:

> "Your certificate (or certificates) for the names listed below will expire in 20 days (on 01 Jun 20 17:18 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors"

This message is sent yesterday (12 may 2020). Let's encrypt mentions this affects all my domains (24). But when checking the current status of my certificates they are already renewed at 5 may and valid till august (checked with quallys SSL labs).

I also ran certbot-auto renew to be sure but it responds with "no certs are due for renewal"

Why am I getting this message while all certificates are already renewed a week ago?

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [May 13, 2020, 8:31am UTC](https://community.letsencrypt.org/t/lets-encrypt-sends-mail-to-refresh-certs-while-this-is-already-done/122585/2 "2020-05-13T08:31:36Z")

</div>

[Expiration Emails - Let's Encrypt](https://letsencrypt.org/docs/expiration-emails/#when-you-get-an-expiration-email) offers a possible explanation:

> If you’ve issued a new certificate that adds or removes a name relative to your old certificate, you will get expiration email about your old certificate

There are [plans](https://github.com/letsencrypt/boulder/issues/4702) to improve this behavior, but for now, you can just ignore this email (assuming the above explanation applies).

---

<div class="post-metadata">

**Author:** ![Biggydeen](https://avatars.discourse-cdn.com/v4/letter/b/5e9695/32.png) [@Biggydeen](https://community.letsencrypt.org/u/Biggydeen)\
**Post date:** [May 13, 2020, 9:05am UTC](https://community.letsencrypt.org/t/lets-encrypt-sends-mail-to-refresh-certs-while-this-is-already-done/122585/3 "2020-05-13T09:05:32Z")

</div>

Thanks for checking. I’ve not added or removed any names. Nothing has changed when getting the certificates for the first time. Funny thing is these domains are running on 4 seperate machines. So every machine gives the same message apparently.

---

<div class="post-metadata">

**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 13, 2020, 9:07am UTC](https://community.letsencrypt.org/t/lets-encrypt-sends-mail-to-refresh-certs-while-this-is-already-done/122585/4 "2020-05-13T09:07:10Z")

</div>

Hi @Biggydeen

> [@Biggydeen](#):
>
> I’ve not added or removed any names.

then share your domain name.

---

<div class="post-metadata">

**Author:** ![Biggydeen](https://avatars.discourse-cdn.com/v4/letter/b/5e9695/32.png) [@Biggydeen](https://community.letsencrypt.org/u/Biggydeen)\
**Post date:** [May 13, 2020, 9:09am UTC](https://community.letsencrypt.org/t/lets-encrypt-sends-mail-to-refresh-certs-while-this-is-already-done/122585/5 "2020-05-13T09:09:24Z")

</div>

penke.nl for example.

The 24 domain names are also on 4 different servers. So apparently all servers have the same “issue”. But since I did the same configuration of certbot on all servers that can be expected.

---

<div class="post-metadata">

**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 13, 2020, 9:13am UTC](https://community.letsencrypt.org/t/lets-encrypt-sends-mail-to-refresh-certs-while-this-is-already-done/122585/6 "2020-05-13T09:13:49Z")

</div>

> [@Biggydeen](#):
>
> penke.nl for example.

The mail is expected - see [https://check-your-website.server-daten.de/?q=penke.nl#ct-logs](https://check-your-website.server-daten.de/?q=penke.nl#ct-logs)

| Issuer | not before | not after | Domain names | LE-Duplicate | next LE |
| --- | --- | --- | --- | --- | --- |
| Let's Encrypt Authority X3 | 2020-05-06 | 2020-08-04 | financieelonafhankelijkworden.nl, hjwebdevelopment.nl, onlinemarketingblogs.nl, penke.nl, [penkedata.com](http://penkedata.com), www.financieelonafhankelijkworden.nl, www.hjwebdevelopment.nl, www.onlinemarketingblogs.nl, www.penke.nl, [www.penkedata.com](http://www.penkedata.com), www.zoekalleproducten.nl, zoekalleproducten.nl - 12 entries | duplicate nr. 1 | |
| Let's Encrypt Authority X3 | 2020-03-07 | 2020-06-05 | financieelonafhankelijkworden.nl, hjwebdevelopment.nl, onlinemarketingblogs.nl, penke.nl, [penkedata.com](http://penkedata.com), www.financieelonafhankelijkworden.nl, www.hjwebdevelopment.nl, www.onlinemarketingblogs.nl, www.penke.nl, [www.penkedata.com](http://www.penkedata.com), www.zoekalleproducten.nl, zoekalleproducten.nl - 12 entries | | |
| Let's Encrypt Authority X3 | 2020-03-03 | 2020-06-01 | dagaanbiedingen-overzicht.nl, deals.hjwebdevelopment.nl, harmjanbosscher.nl, [hjtoolbox.com](http://hjtoolbox.com), hjwebdevelopment.nl, manager.hjwebdevelopment.nl, onlinemarketingblogs.nl, penke.nl, vrijevakantiehuizen.nl, www.dagaanbiedingen-overzicht.nl, www.deals.hjwebdevelopment.nl, www.harmjanbosscher.nl, [www.hjtoolbox.com](http://www.hjtoolbox.com), www.hjwebdevelopment.nl, www.onlinemarketingblogs.nl, www.penke.nl, www.vrijevakantiehuizen.nl, www.zoekalleaanbiedingen.nl, www.zoekalleproducten.nl, www.zoekallevakanties.nl, zoekalleaanbiedingen.nl, zoekalleproducten.nl, zoekallevakanties.nl - 23 entries | | |

You have a certificate with 23 domain names, ending 2020-06-01. Now you have and use a certificate with 12 domain names. So the 23-certificate isn't renewed -\> that's the mail.

---

<div class="post-metadata">

**Author:** ![Biggydeen](https://avatars.discourse-cdn.com/v4/letter/b/5e9695/32.png) [@Biggydeen](https://community.letsencrypt.org/u/Biggydeen)\
**Post date:** [May 13, 2020, 9:22am UTC](https://community.letsencrypt.org/t/lets-encrypt-sends-mail-to-refresh-certs-while-this-is-already-done/122585/7 "2020-05-13T09:22:02Z")

</div>

The former server hosting all these domains is deleted. But the cert for these domains was still active. That makes sense.

Thanks for the help!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [June 12, 2020, 9:22am UTC](https://community.letsencrypt.org/t/lets-encrypt-sends-mail-to-refresh-certs-while-this-is-already-done/122585/8 "2020-06-12T09:22:05Z")

</div>

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