# Bug on email with certificate expiration date

**URL:** <https://community.letsencrypt.org/t/bug-on-email-with-certificate-expiration-date/23372>\
**Category:** Feature Requests\
**Created:** [November 30, 2016, 10:55am UTC](https://community.letsencrypt.org/t/bug-on-email-with-certificate-expiration-date/23372 "2016-11-30T10:55:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcsellier](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/marcsellier/32/9749_2.png) [@marcsellier](https://community.letsencrypt.org/u/marcsellier)\
**Post date:** [November 30, 2016, 10:55am UTC](https://community.letsencrypt.org/t/bug-on-email-with-certificate-expiration-date/23372/1 "2016-11-30T10:55:53Z")

</div>

Hello,

I just received an email from Let’s Encrypt with this message: “Your certificate (or certificates) for the names listed below will expire in 19 days (on 17 Dec 16 21:36 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors.”

Domain: [twinable.com](http://twinable.com)  
My certificate will expire on Sunday, 19 February 2017. Have you a bug on your certification mailer?

Thank you  
Marc

---

<div class="post-metadata">

**Author:** ![tialaramex](https://avatars.discourse-cdn.com/v4/letter/t/f08c70/32.png) [@tialaramex](https://community.letsencrypt.org/u/tialaramex)\
**Post date:** [November 30, 2016, 11:52am UTC](https://community.letsencrypt.org/t/bug-on-email-with-certificate-expiration-date/23372/2 "2016-11-30T11:52:32Z")

</div>

Back in September, when you first obtained a certificate for [twintable.com](http://twintable.com) you actually almost immediately then asked for another, separate, certificate for both [twintable.com](http://twintable.com) and [www.twintable.com](http://www.twintable.com), which you have subsequently renewed. Probably you just didn’t realise you would need both the names, and once you realised you asked for another certificate, that’s fine.

The warning is about the first certificate, just for [twintable.com](http://twintable.com), which most likely you are no longer using, and so it is fine to just ignore expiry warnings for this certificate. Let’s Encrypt can’t be entirely sure whether you need the certificate just for the one name, so that’s why you get warnings.

---

<div class="post-metadata">

**Author:** ![marcsellier](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/marcsellier/32/9749_2.png) [@marcsellier](https://community.letsencrypt.org/u/marcsellier)\
**Post date:** [November 30, 2016, 1:03pm UTC](https://community.letsencrypt.org/t/bug-on-email-with-certificate-expiration-date/23372/3 "2016-11-30T13:03:04Z")

</div>

Ok, thank you very much for your reply!

---

<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:** [December 30, 2016, 1:03pm UTC](https://community.letsencrypt.org/t/bug-on-email-with-certificate-expiration-date/23372/4 "2016-12-30T13:03:15Z")

</div>

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