# Certbot renew error while using the renew command-connection refused

**URL:** <https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222>\
**Category:** Help\
**Created:** [October 1, 2019, 2:36pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222 "2019-10-01T14:36:26Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![nmacwan](https://avatars.discourse-cdn.com/v4/letter/n/f14d63/32.png) [@nmacwan](https://community.letsencrypt.org/u/nmacwan)\
**Post date:** [October 1, 2019, 2:36pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/1 "2019-10-01T14:36:26Z")

</div>

Hi  
My domain is:exrcloud.exr.ca

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

It produced this output:  
Domain: exrcloud.exr.ca  
Type: connection  
Detail: Fetching  
[http://exrcloud.exr.ca/.well-known/acme-challenge/R8UNO4VtBW7Ju9Nv\_trm6GeLgVizw8HviOhwbiFuX1Q:](http://exrcloud.exr.ca/.well-known/acme-challenge/R8UNO4VtBW7Ju9Nv_trm6GeLgVizw8HviOhwbiFuX1Q:)  
Connection refused

My web server is (include version):Apache2

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

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

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

Please help  
I tried to renew the cert using the command but it gives me error regarding connection refused.  
it worked the last time when i created the new certificate 2 months ago

---

<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:** [October 1, 2019, 2:43pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/2 "2019-10-01T14:43:40Z")

</div>

Hi @nmacwan

> [@nmacwan](#):
>
> Domain: exrcloud.exr.ca  
> Type: connection  
> Detail: Fetching  
> [http://exrcloud.exr.ca/.well-known/acme-challenge/R8UNO4VtBW7Ju9Nv\_trm6GeLgVizw8HviOhwbiFuX1Q:](http://exrcloud.exr.ca/.well-known/acme-challenge/R8UNO4VtBW7Ju9Nv_trm6GeLgVizw8HviOhwbiFuX1Q:)  
> Connection refused

looks like a firewall or another blocking instance.

Works http internal?

What says

```nohighlight
curl http://exrcloud.exr.ca/.well-known/acme-challenge/1234

curl http://exrcloud.exr.ca/

```

What's the server software you use? `apachectl -S` or `nginx -T`?

---

<div class="post-metadata">

**Author:** ![nmacwan](https://avatars.discourse-cdn.com/v4/letter/n/f14d63/32.png) [@nmacwan](https://community.letsencrypt.org/u/nmacwan)\
**Post date:** [October 1, 2019, 2:47pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/3 "2019-10-01T14:47:07Z")

</div>

Works http internal?  
Yes it works internally.

What says  
curl [http://exrcloud.exr.ca/.well-known/acme-challenge/1234](http://exrcloud.exr.ca/.well-known/acme-challenge/1234)  
curl [http://exrcloud.exr.ca/](http://exrcloud.exr.ca/)

but since the configuration is set to redirect http to https it directly goes to [https://exrcloud.exr.ca](https://exrcloud.exr.ca)

What’s the server software you use? apachectl -S or nginx -T?  
we uses apachectl

---

<div class="post-metadata">

**Author:** ![nmacwan](https://avatars.discourse-cdn.com/v4/letter/n/f14d63/32.png) [@nmacwan](https://community.letsencrypt.org/u/nmacwan)\
**Post date:** [October 1, 2019, 2:49pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/4 "2019-10-01T14:49:27Z")

</div>

WE have set the port for https to 4445 so that it can be accessed outside  
since 443 is already being used  
but i dont think this might create any issue.  
Since when i created the cert the port and redirect was already setup before the cert registration

---

<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:** [October 1, 2019, 2:50pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/5 "2019-10-01T14:50:58Z")

</div>

Your port 80 must answer.

You can redirect to port 443 (extern), but port 80 refused -\> renew doesn’t work.

---

<div class="post-metadata">

**Author:** ![nmacwan](https://avatars.discourse-cdn.com/v4/letter/n/f14d63/32.png) [@nmacwan](https://community.letsencrypt.org/u/nmacwan)\
**Post date:** [October 1, 2019, 3:09pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/6 "2019-10-01T15:09:12Z")

</div>

What should i change for 80 to Answer??  
Port 80 is set to listen in Apache and is not blocked either.

---

<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:** [October 1, 2019, 3:22pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/7 "2019-10-01T15:22:22Z")

</div>

> [@nmacwan](#):
>
> Port 80 is set to listen in Apache and is not blocked either.

It is blocked:

> **[EXRCloud](http://exrcloud.exr.ca/.well-known/acme-challenge/R8UNO4VtBW7Ju9Nv_trm6GeLgVizw8HviOhwbiFuX1Q)**
>
> a safe home for all your data

There is no answer. If if works internal, you have a blocking instance.

A http status 404 - Not Found or a redirect is expected.

---

<div class="post-metadata">

**Author:** ![nmacwan](https://avatars.discourse-cdn.com/v4/letter/n/f14d63/32.png) [@nmacwan](https://community.letsencrypt.org/u/nmacwan)\
**Post date:** [October 1, 2019, 3:45pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/8 "2019-10-01T15:45:53Z")

</div>

The Above link when opened internally  
redirects to the following link  
[https://exrcloud.exr.ca/](https://exrcloud.exr.ca/)

---

<div class="post-metadata">

**Author:** ![nmacwan](https://avatars.discourse-cdn.com/v4/letter/n/f14d63/32.png) [@nmacwan](https://community.letsencrypt.org/u/nmacwan)\
**Post date:** [October 1, 2019, 3:47pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/9 "2019-10-01T15:47:25Z")

</div>

This is the whole error i am getting:  
Processing /etc/letsencrypt/renewal/exrcloud.exr.ca-0001.conf

* * *

Cert is due for renewal, auto-renewing…  
Plugins selected: Authenticator apache, Installer apache  
Renewing an existing certificate  
Performing the following challenges:  
http-01 challenge for exrcloud.exr.ca  
Waiting for verification…  
Cleaning up challenges  
Attempting to renew cert (exrcloud.exr.ca-0001) from /etc/letsencrypt/renewal/exrcloud.exr.ca-0001.conf produced an unexpected error: Failed authorization procedure. exrcloud.exr.ca (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [http://exrcloud.exr.ca/.well-known/acme-challenge/zSpg6MQIzm-4Wbl2XnC79cFiu1cJbPI0szYJPU7fgnY:](http://exrcloud.exr.ca/.well-known/acme-challenge/zSpg6MQIzm-4Wbl2XnC79cFiu1cJbPI0szYJPU7fgnY:) Connection refused. Skipping.  
All renewal attempts failed. The following certs could not be renewed:  
/etc/letsencrypt/live/exrcloud.exr.ca-0001/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/exrcloud.exr.ca-0001/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:

---

<div class="post-metadata">

**Author:** ![nmacwan](https://avatars.discourse-cdn.com/v4/letter/n/f14d63/32.png) [@nmacwan](https://community.letsencrypt.org/u/nmacwan)\
**Post date:** [October 1, 2019, 4:23pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/10 "2019-10-01T16:23:52Z")

</div>

I hope this my help

 ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/f/3/f38628e5a1766b4307c31359f04308bd9c46804a.png)

---

<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:** [October 1, 2019, 5:17pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/11 "2019-10-01T17:17:57Z")

</div>

> [@nmacwan](#):
>
> The Above link when opened internally

That's not relevant, if an extern check doesn't work. Checking your domain online via [https://check-your-website.server-daten.de/?q=exrcloud.exr.ca](https://check-your-website.server-daten.de/?q=exrcloud.exr.ca) there is no answer.

So Letsencrypt can't connect your domain and can't validate the domain name -\> no certificate.

---

<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:** [October 1, 2019, 5:19pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/12 "2019-10-01T17:19:11Z")

</div>

> [@nmacwan](#):
>
> I hope this my help

If it works internal, it's not a problem of your Apache. It's a blocking instance. Or a wrong port forward.

---

<div class="post-metadata">

**Author:** ![nmacwan](https://avatars.discourse-cdn.com/v4/letter/n/f14d63/32.png) [@nmacwan](https://community.letsencrypt.org/u/nmacwan)\
**Post date:** [October 1, 2019, 6:42pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/13 "2019-10-01T18:42:36Z")

</div>

Thanks ,  
i tried to solve the port 80 for connection refuse.  
the following command works fine now.  
sudo certbot renew --dry-run(no errors and runs successful)

but when i try to run the actual renew command it gives me the following error.  
Attempting to renew cert (exrcloud.exr.ca-0001) from /etc/letsencrypt/renewal/exrcloud.exr.ca-0001.conf produced an unexpected error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see [https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/). Skipping.  
All renewal attempts failed. The following certs could not be renewed:  
/etc/letsencrypt/live/exrcloud.exr.ca-0001/fullchain.pem (failure)

---

<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 31, 2019, 6:42pm UTC](https://community.letsencrypt.org/t/certbot-renew-error-while-using-the-renew-command-connection-refused/103222/14 "2019-10-31T18:42:46Z")

</div>

Closed on October 31, 2019, 6:42pm UTC

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