# Action required: Let's Encrypt certificate renewals

**URL:** <https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83008>\
**Category:** Help\
**Created:** [January 18, 2019, 1:03pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83008 "2019-01-18T13:03:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![panambi](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@panambi](https://community.letsencrypt.org/u/panambi)\
**Post date:** [January 18, 2019, 1:03pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83008/1 "2019-01-18T13:03:35Z")

</div>

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: [sgainacirsa.ddns.net](http://sgainacirsa.ddns.net)

I ran this command:  
certbot --version  
certbot 0.14.2

certbot renew --dry-run

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

* * *

## Processing /etc/letsencrypt/renewal/sgainacirsa.ddns.net.conf

Cert not due for renewal, but simulating renewal for dry run  
Renewing an existing certificate  
Performing the following challenges:  
tls-sni-01 challenge for [sgainacirsa.ddns.net](http://sgainacirsa.ddns.net)  
Waiting for verification…  
Cleaning up challenges

* * *

## new certificate deployed with reload of apache server; fullchain is /etc/letsencrypt/live/sgainacirsa.ddns.net/fullchain.pem

\*\* DRY RUN: simulating ‘certbot renew’ close to cert expiry  
\*\* (The test certificates below have not been saved.)

Congratulations, all renewals succeeded. The following certs have been renewed:  
/etc/letsencrypt/live/sgainacirsa.ddns.net/fullchain.pem (success)  
\*\* DRY RUN: simulating ‘certbot renew’ close to cert expiry  
\*\* (The test certificates above have not been saved.)

My web server is (include version): Apache/2.4.7

The operating system my web server runs on is (include version): Ubuntu 14.04

My hosting provider, if applicable, is:

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

Should I update Certbot?  
Thanks!

---

<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:** [January 18, 2019, 1:07pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83008/2 "2019-01-18T13:07:50Z")

</div>

Hi @panambi

first update your certbot.

Then

> [@panambi](#):
>
> certbot renew --dry-run

add `--preferred-challenges http` to switch to http - validation.

Your main configuration ( [sgainacirsa.ddns.net - Make your website better - DNS, redirects, mixed content, certificates](https://check-your-website.server-daten.de/?q=sgainacirsa.ddns.net) )

| Domainname | Http-Status | redirect | Sec. | G |
| --- | --- | --- | --- | --- |
| • [http://sgainacirsa.ddns.net/](http://sgainacirsa.ddns.net/) | | | | |
| 186.137.46.7 | 302 | [SGA - Sistema de Gestión de Amenazas](http://sgainacirsa.ddns.net/cirsa/) | 0.540 | D |
| | | | | |
| • [SGA - Sistema de Gestión de Amenazas](http://sgainacirsa.ddns.net/cirsa/) | 200 | | 2.406 | H |
| | | | | |
| • [https://sgainacirsa.ddns.net/](https://sgainacirsa.ddns.net/) | | | | |
| 186.137.46.7 | 302 | [SGA - Sistema de Gestión de Amenazas](https://sgainacirsa.ddns.net/cirsa/) | 4.057 | B |
| | | | | |
| • [SGA - Sistema de Gestión de Amenazas](https://sgainacirsa.ddns.net/cirsa/) | 200 | | 5.363 | B |
| | | | | |
| • [http://sgainacirsa.ddns.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://sgainacirsa.ddns.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | |
| 186.137.46.7 | 404 | | 0.540 | A |
| No Encontrado | | | | |

looks ok, because /.well-known/acme-challenge is there, port 80 is open and there is the expected http status 404 (file not found, because it's a not existing file).

---

<div class="post-metadata">

**Author:** ![panambi](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@panambi](https://community.letsencrypt.org/u/panambi)\
**Post date:** [January 18, 2019, 4:43pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83008/3 "2019-01-18T16:43:44Z")

</div>

I’ll try that. 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:** [February 17, 2019, 4:43pm UTC](https://community.letsencrypt.org/t/action-required-lets-encrypt-certificate-renewals/83008/4 "2019-02-17T16:43:45Z")

</div>

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