Certbot renew error while using the renew command-connection refused

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

Hi @nmacwan

looks like a firewall or another blocking instance.

Works http internal?

What says

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?

Works http internal?
Yes it works internally.

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

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

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

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

Your port 80 must answer.

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

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

It is blocked:

http://exrcloud.exr.ca/.well-known/acme-challenge/R8UNO4VtBW7Ju9Nv_trm6GeLgVizw8HviOhwbiFuX1Q

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

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

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

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

    Domain: exrcloud.exr.ca
    Type: connection
    Detail: Fetching
    http://exrcloud.exr.ca/.well-known/acme-challenge/zSpg6MQIzm-4Wbl2XnC79cFiu1cJbPI0szYJPU7fgnY:
    Connection refused

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

I hope this my help

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 there is no answer.

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

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

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/. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/exrcloud.exr.ca-0001/fullchain.pem (failure)

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