# Action required: Let's Encrypt certificate renewals

**URL:** <https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594>\
**Category:** Help\
**Created:** [January 22, 2019, 12:26pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594 "2019-01-22T12:26:08Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![lroslundh](https://avatars.discourse-cdn.com/v4/letter/l/9fc348/32.png) [@lroslundh](https://community.letsencrypt.org/u/lroslundh)\
**Post date:** [January 22, 2019, 12:26pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594/1 "2019-01-22T12:26:08Z")

</div>

I too received the following mail:

Hello,

**Action is required to prevent your Let's Encrypt certificate renewals from breaking.**

Your Let’s Encrypt client used ACME TLS-SNI-01 domain validation to issue a certificate in the past 60 days.

TLS-SNI-01 validation is reaching end-of-life and will stop working on **February 13th, 2019.**

You need to update your ACME client to use an alternative validation method (HTTP-01, DNS-01 or TLS-ALPN-01) before this date or your certificate renewals will break and existing certificates will start to expire.

If you need help updating your ACME client, please open a new topic in the Help category of the Let's Encrypt community forum:

[Help - Let's Encrypt Community Support](https://community.letsencrypt.org/c/help)

Please answer all of the questions in the topic template so we can help you.

For more information about the TLS-SNI-01 end-of-life please see our API announcement:

> [@March 13, 2019: End-of-Life for All TLS-SNI-01 Validation Support](https://community.letsencrypt.org/t/february-13-2019-end-of-life-for-all-tls-sni-01-validation-support/74209):
>
> L…

## Thank you, Let's Encrypt Staff

I ran this command:  
**./certbot-auto --dry-run**  
It produced this output:  
**Succeded on all domains.**  
My web server is (include version):  
**Apache/2.4.7 (Ubuntu)**  
The operating system my web server runs on is (include version):  
**Ubuntu 14.04.4 LTS**  
My hosting provider, if applicable, is:  
**Hetzner**  
I can login to a root shell on my machine (yes or no, or I don't know):  
**Yes**  
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):  
**No**  
The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot):  
**certbot 0.30.0**

---

<div class="post-metadata">

**Author:** ![lroslundh](https://avatars.discourse-cdn.com/v4/letter/l/9fc348/32.png) [@lroslundh](https://community.letsencrypt.org/u/lroslundh)\
**Post date:** [January 22, 2019, 12:30pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594/2 "2019-01-22T12:30:05Z")

</div>

I was able to run the command ./certbot-auto --dry-run and it succeeded on all the domains.  
In the process i see that certbot was updated from 0.21.0 to 0.30.0.

Just to clarify i need to know if that is sufficient in terms of updating the ACME client.  
I have not done anything else. Do i need to upgrade any packages as well or am i good to go?

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [January 22, 2019, 12:41pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594/3 "2019-01-22T12:41:21Z")

</div>

You should be good to go 🙂

---

<div class="post-metadata">

**Author:** ![lroslundh](https://avatars.discourse-cdn.com/v4/letter/l/9fc348/32.png) [@lroslundh](https://community.letsencrypt.org/u/lroslundh)\
**Post date:** [January 22, 2019, 12:43pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594/4 "2019-01-22T12:43:24Z")

</div>

Thank you very much!  
Thought it was a way bigger process than this 🙂

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [January 22, 2019, 12:48pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594/5 "2019-01-22T12:48:08Z")

</div>

To be 100% sure: Double check the logs to see it says “http-01” in the challenges - which is should.

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [January 22, 2019, 1:09pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594/6 "2019-01-22T13:09:33Z")

</div>

> [@lroslundh](#):
>
> ./certbot-auto --dry-run

`./certbot-auto renew --dry-run`?

---

<div class="post-metadata">

**Author:** ![lroslundh](https://avatars.discourse-cdn.com/v4/letter/l/9fc348/32.png) [@lroslundh](https://community.letsencrypt.org/u/lroslundh)\
**Post date:** [January 22, 2019, 1:13pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594/7 "2019-01-22T13:13:33Z")

</div>

Yes of course ./certbot-auto renew --dry-run

Wrote it from memory - my bad!

---

<div class="post-metadata">

**Author:** ![lroslundh](https://avatars.discourse-cdn.com/v4/letter/l/9fc348/32.png) [@lroslundh](https://community.letsencrypt.org/u/lroslundh)\
**Post date:** [January 22, 2019, 1:14pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594/8 "2019-01-22T13:14:44Z")

</div>

Great! Logs says http-01 challenge for \<[my.domain.com](http://my.domain.com)\>

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [January 22, 2019, 1:15pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594/9 "2019-01-22T13:15:19Z")

</div>

Then we are good to go!!!

---

<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:** [February 21, 2019, 1:16pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83594/10 "2019-02-21T13:16:31Z")

</div>

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