# Let's Encrypt Renew Certificate Issues

**URL:** <https://community.letsencrypt.org/t/lets-encrypt-renew-certificate-issues/94542>\
**Category:** Help\
**Created:** [May 27, 2019, 8:52am UTC](https://community.letsencrypt.org/t/lets-encrypt-renew-certificate-issues/94542 "2019-05-27T08:52:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ridgejason](https://avatars.discourse-cdn.com/v4/letter/r/ebca7d/32.png) [@ridgejason](https://community.letsencrypt.org/u/ridgejason)\
**Post date:** [May 27, 2019, 8:52am UTC](https://community.letsencrypt.org/t/lets-encrypt-renew-certificate-issues/94542/1 "2019-05-27T08:52:56Z")

</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: [www.thechemicalhut.org](http://www.thechemicalhut.org)

I ran this command: sudo certbot renew --dry-run

It produced this output:

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

* * *

Processing /etc/letsencrypt/renewal/www.thechemicalhut.org.conf

* * *

Cert is due for renewal, auto-renewing…  
Plugins selected: Authenticator apache, Installer apache  
Starting new HTTPS connection (1): [acme-staging-v02.api.letsencrypt.org](http://acme-staging-v02.api.letsencrypt.org)  
Renewing an existing certificate  
Performing the following challenges:  
http-01 challenge for [www.thechemicalhut.org](http://www.thechemicalhut.org)  
Waiting for verification…  
Cleaning up challenges  
Attempting to renew cert ([www.thechemicalhut.org](http://www.thechemicalhut.org)) from /etc/letsencrypt/renewal/www.thechemicalhut.org.conf produced an unexpected error: Failed authorization procedure. [www.thechemicalhut.org](http://www.thechemicalhut.org) (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [http://www.thechemicalhut.org/.well-known/acme-challenge/dGWtG0y6OgI8dRjapdyjGTEeZfHq8eB0ys6kfRf-pjw:](http://www.thechemicalhut.org/.well-known/acme-challenge/dGWtG0y6OgI8dRjapdyjGTEeZfHq8eB0ys6kfRf-pjw:) Timeout during connect (likely firewall problem). Skipping.  
All renewal attempts failed. The following certs could not be renewed:  
/etc/letsencrypt/live/www.thechemicalhut.org/fullchain.pem (failure)

* * *

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

All renewal attempts failed. The following certs could not be renewed:  
/etc/letsencrypt/live/www.thechemicalhut.org/fullchain.pem (failure)  
\*\* DRY RUN: simulating ‘certbot renew’ close to cert expiry  
\*\* (The test certificates above have not been saved.)

* * *

1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

- The following errors were reported by the server:

My web server is (include version): nginx/1.15.3

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

My hosting provider, if applicable, is: digitalocean

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):

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot):

---

<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 27, 2019, 9:12am UTC](https://community.letsencrypt.org/t/lets-encrypt-renew-certificate-issues/94542/2 "2019-05-27T09:12:55Z")

</div>

It looks like you probably have a firewall installed on your Ubuntu setup.

Try:

```
ufw allow http

```

Also check in the DigitalOcean control panel that you haven’t accidentally enabled the firewall without permitting port 80.

---

<div class="post-metadata">

**Author:** ![ridgejason](https://avatars.discourse-cdn.com/v4/letter/r/ebca7d/32.png) [@ridgejason](https://community.letsencrypt.org/u/ridgejason)\
**Post date:** [May 27, 2019, 10:42am UTC](https://community.letsencrypt.org/t/lets-encrypt-renew-certificate-issues/94542/3 "2019-05-27T10:42:14Z")

</div>

Thanks.

Sorted it was the firewall from digitalocean that was the issue.

J

---

<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 26, 2019, 10:45am UTC](https://community.letsencrypt.org/t/lets-encrypt-renew-certificate-issues/94542/4 "2019-06-26T10:45:38Z")

</div>

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