# Expiry emails from letsencrypt not reflecting updated expiry dates

**URL:** <https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398>\
**Category:** Issuance Policy\
**Created:** [September 29, 2016, 8:16am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398 "2016-09-29T08:16:15Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![markdesilva](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@markdesilva](https://community.letsencrypt.org/u/markdesilva)\
**Post date:** [September 29, 2016, 8:16am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/1 "2016-09-29T08:16:15Z")

</div>

Not sure if this is the right category to put this, but the expiry emails seem to reflect the old expiry dates.

For eg: my certs are were set to expiry say 1st Sept 2016. I renew all certs on the 25th of August 2016. However I still get emails from letsencrypt stating that my cert will expire 1st Sept.

I check the actual expiry of the cert and its correctly dated 25th Nov 2016, which is 3 months from the 25th of August.

Is this a bug in the auto notifier? Or is it just meant to be this way?

Other than that letsencrypt is working great for me and all my domains.

Thank you.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [September 29, 2016, 9:19am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/2 "2016-09-29T09:19:26Z")

</div>

As far as I know, the auto notifier doesn’t have a clue you’ve already renewed your certificates. So you can ignore the extra e-mails if all is renewed properly.

---

<div class="post-metadata">

**Author:** ![ahaw021](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ahaw021/32/14882_2.png) [@ahaw021](https://community.letsencrypt.org/u/ahaw021)\
**Post date:** [September 29, 2016, 9:19am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/3 "2016-09-29T09:19:37Z")

</div>

Hi Mark

Use [http://crt.sh/](http://crt.sh/) and your domain

This will show you all certificates that have been registered for your domains

You may find you have multiple certificates hence the expiry dates.

Andrei

---

<div class="post-metadata">

**Author:** ![markdesilva](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@markdesilva](https://community.letsencrypt.org/u/markdesilva)\
**Post date:** [September 29, 2016, 9:35am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/4 "2016-09-29T09:35:26Z")

</div>

Thanks! Would be nice if the notifier does check so we have an accurate  
notice but it’s no big deal.

- Mark

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [September 29, 2016, 9:39am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/5 "2016-09-29T09:39:14Z")

</div>

It should check for “identical” renewals. However if your new cert has an additional domain ( perhaps a www subdomain on it) then it won’t recognise it as a direct replacement.

If your list of domains on the new cert is identical to the list on the old cert, it’s probably a bug 😉

---

<div class="post-metadata">

**Author:** ![markdesilva](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@markdesilva](https://community.letsencrypt.org/u/markdesilva)\
**Post date:** [September 29, 2016, 9:51am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/6 "2016-09-29T09:51:55Z")

</div>

Think it’s a bug then because notices for certs for a single domain (with  
no change) give the old renewal date.

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [September 29, 2016, 9:53am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/7 "2016-09-29T09:53:21Z")

</div>

Are you happy to provide the domain name, so that can be chased though ?

---

<div class="post-metadata">

**Author:** ![markdesilva](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@markdesilva](https://community.letsencrypt.org/u/markdesilva)\
**Post date:** [September 29, 2016, 10:22am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/8 "2016-09-29T10:22:19Z")

</div>

Well lets take [cherokee.chrysler.org.sg](http://cherokee.chrysler.org.sg). It has 2 domains under it:

[cherokee.chrysler.org.sg](http://cherokee.chrysler.org.sg)  
[weblogs.chrysler.org.sg](http://weblogs.chrysler.org.sg)

Original expiry was 21st Sept 2016. I renewed on 29th August 2016, but on  
12th Sept, I still got this mail which shows the original expiry of 21st  
Sept 2016:

\*expiry@letsencrypt.org [expiry@letsencrypt.org](mailto:expiry@letsencrypt.org) \*[expiry@letsencrypt.org](mailto:expiry@letsencrypt.org)Mon,  
Sep 12, 2016 at 5:13 AM  
Hello,

Your certificate (or certificates) for the names listed below will expire  
in 10 days (on 21 Sep 16 21:15 +0000). Please make sure to renew your  
certificate before then, or visitors to your website will encounter errors.

[cherokee.chrysler.org.sg](http://cherokee.chrysler.org.sg)  
[weblogs.chrysler.org.sg](http://weblogs.chrysler.org.sg)

For any questions or support, please visit [https://community.letsencrypt](https://community.letsencrypt).  
org/. Unfortunately, we can’t provide support by email.

If you are receiving this email in error, unsubscribe at  
[http://mandrillapp.com/track/unsub.php?u=30850198&id=](http://mandrillapp.com/track/unsub.php?u=30850198&id=)  
729543c4be984e78bf370db489d5d2e6.3qo59wzl%2FGgC5YlMwvVdIsP26o8%3D&r=  
https%3A%2F%[2Fmandrillapp.com](http://2Fmandrillapp.com)%2Funsub%3Fmd\_email%3Dmark%[2540chrysler.org.sg](http://2540chrysler.org.sg)  
(HTTP link, we know. We’re working on it!)

Regards,  
The Let’s Encrypt Team

Its not only this domain by the way, I have a few, the expiry notice for  
all of them have the same issues.

Thanks.

---

<div class="post-metadata">

**Author:** ![cool110](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cool110/32/8583_2.png) [@cool110](https://community.letsencrypt.org/u/cool110)\
**Post date:** [September 29, 2016, 10:29am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/9 "2016-09-29T10:29:27Z")

</div>

You originally obtained separate certs for [cherokee.chrysler.org.sg](http://cherokee.chrysler.org.sg) and [weblogs.chrysler.org.sg](http://weblogs.chrysler.org.sg) on the 22nd of June which were both renewed the day after. Also on the 23rd you obtained a cert for both names which was renewed on the 31st of August.

The email you received refers to the 2 separate certs that you have presumably abandoned in favour of the single cert for both.

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [September 29, 2016, 10:32am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/10 "2016-09-29T10:32:19Z")

</div>

on Jun 23 21:15:00 2016 GMT you obtained a cert for just [cherokee.chrysler.org.sg](http://cherokee.chrysler.org.sg) - [https://crt.sh/?id=22859572](https://crt.sh/?id=22859572)

on Jun 23 21:15:00 2016 GMT you separately obtained a cert for [weblogs.chrysler.org.sg](http://weblogs.chrysler.org.sg) - [https://crt.sh/?id=22961237](https://crt.sh/?id=22961237)

later on Jun 23 21:54:00 2016 GMT you obtained a cert for both cherokee and weblogs - [https://crt.sh/?id=22962436](https://crt.sh/?id=22962436)

You then renewed the cert containing both names on Aug 31 16:15:00 2016 GMT - [https://crt.sh/?id=30426444](https://crt.sh/?id=30426444)

Since you have renewed the cert containing both names, you shouldn’t get an alert for that. You haven’t renewed the certs for the separate domain names though - hence you will have received an alert for that.

Does that make sense ?

---

<div class="post-metadata">

**Author:** ![markdesilva](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@markdesilva](https://community.letsencrypt.org/u/markdesilva)\
**Post date:** [September 29, 2016, 11:08am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/11 "2016-09-29T11:08:55Z")

</div>

Ummm a little confused still and apologize I didn’t realize I created  
separate certs for that.

You mentioned I shouldn’t get alerts for the combined cert because I  
renewed that? But I am getting alerts for the combined cert but not for the  
separate certs which were not renewed.

Maybe I’ll just ride through all the old expiry dates and after the next  
renewal (I renew about 5 - 10 days before expiry) I will monitor to see if  
I get alerts for the last expiry date

Thanks!

---

<div class="post-metadata">

**Author:** ![markdesilva](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@markdesilva](https://community.letsencrypt.org/u/markdesilva)\
**Post date:** [September 29, 2016, 11:12am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/12 "2016-09-29T11:12:56Z")

</div>

So does that mean that when the expiry email comes with the two FQDNs it’s  
actually referring to 2 separate certs under my email which expiry on the  
same date? I always thought it referred to the combined cert for the FQDNs  
listed under it.

Thank you.

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [September 29, 2016, 11:13am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/13 "2016-09-29T11:13:59Z")

</div>

I think there is probably confusion because you have a single email with both domains listed in it.

It does say "Your certificate (or certificates) "… and in this case it’s certificates 😉

If you look at the dates on the links I provided above, the two separate, single domain, certs are the ones that expire at Sep 21 21:15:00 2016 GMT - so those are the ones that the email refers to (not the combined cert.

---

<div class="post-metadata">

**Author:** ![markdesilva](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@markdesilva](https://community.letsencrypt.org/u/markdesilva)\
**Post date:** [September 29, 2016, 11:27am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/14 "2016-09-29T11:27:45Z")

</div>

Ah that explains it. Thanks!

---

<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:** [October 29, 2016, 11:36am UTC](https://community.letsencrypt.org/t/expiry-emails-from-letsencrypt-not-reflecting-updated-expiry-dates/20398/15 "2016-10-29T11:36:47Z")

</div>

Closed on October 29, 2016, 11:36am UTC

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