.Well-known timeout on renewal

Help
1

My domain is:
cloud.spacedock.duckdns.org
dungeon.spacedock.duckdns.org

I have a certificate for both these subdomains

I ran this command:
certbot renew

It produced this output:

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

Processing /etc/letsencrypt/renewal/cloud.spacedock.duckdns.org.conf

Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for cloud.spacedock.duckdns.org
Waiting for verification...
Cleaning up challenges
Attempting to renew cert (cloud.spacedock.duckdns.org) from /etc/letsencrypt/renewal/cloud.spacedock.duckdns.org.conf produced an unexpected error: Failed authorization procedure. cloud.spacedock.duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: 88.177.21.61: Fetching http://cloud.spacedock.duckdns.org/.well-known/acme-challenge/bCy_Vwe4roi59aOXgifma7ZfZ_sB3rDANJQkx1Ti3xI: Timeout during connect (likely firewall problem). Skipping.

Processing /etc/letsencrypt/renewal/dungeon.spacedock.duckdns.org.conf

Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for dungeon.spacedock.duckdns.org
Waiting for verification...
Cleaning up challenges
Attempting to renew cert (dungeon.spacedock.duckdns.org) from /etc/letsencrypt/renewal/dungeon.spacedock.duckdns.org.conf produced an unexpected error: Failed authorization procedure. dungeon.spacedock.duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: 88.177.21.61: Fetching http://dungeon.spacedock.duckdns.org/.well-known/acme-challenge/YxcS8o5Lw9-DryCJ2aFnYc7Fni_R3uOSKHJ1cO0CrDY: Timeout during connect (likely firewall problem). Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/cloud.spacedock.duckdns.org/fullchain.pem (failure)
/etc/letsencrypt/live/dungeon.spacedock.duckdns.org/fullchain.pem (failure)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/cloud.spacedock.duckdns.org/fullchain.pem (failure)
/etc/letsencrypt/live/dungeon.spacedock.duckdns.org/fullchain.pem (failure)

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

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: cloud.spacedock.duckdns.org
    Type: connection
    Detail: 88.177.21.61: Fetching
    http://cloud.spacedock.duckdns.org/.well-known/acme-challenge/bCy_Vwe4roi59aOXgifma7ZfZ_sB3rDANJQkx1Ti3xI:
    Timeout during connect (likely firewall problem)

    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.

  • The following errors were reported by the server:

    Domain: dungeon.spacedock.duckdns.org
    Type: connection
    Detail: 88.177.21.61: Fetching
    http://dungeon.spacedock.duckdns.org/.well-known/acme-challenge/YxcS8o5Lw9-DryCJ2aFnYc7Fni_R3uOSKHJ1cO0CrDY:
    Timeout during connect (likely firewall problem)

    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.

My web server is (include version):
nginx-1.10.1

The operating system my web server runs on is (include version):
OSMC 2020.11-1 (which is based upon Debian Buster)

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

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

A cron ran it

Hello all, I've been using let's encrypt/certbot for years now without any problem on this small machine (an OSMC Vero) to host my small applications. It is very old now (as is most of the software on it) and I am in the process of replacing it and upgrading all my software (nginx included) to current versions. But, in the meantime, I need it to still work for a few months more as I can't immediately rebuild all my environment due to a busy schedule

Recently, I moved into a new house and was without any internet connection for three months. During this time, my certificates expired and now, when the command is run, I'm receiving a timeout error.

What is strange to me is that I can access the .well-known directory with a browser : I placed a small html file (called "a.htm" with just a short text, you can check it at http://cloud.spacedock.duckdns.org/.well-known/a.htm) and I didn't change anything at all : the machine has the exact same configuration that had worked for years, the router is the same (with ports forwarded, I can access the sites from outside my local network, but without SSL).
I just replugged the machine after several months without connection.

I am not aware of any firewall running on my server, and the router has ports forwarded (once again, the machine is unchanged from the time it worked).

Thanks for any help in this matter.

2

Well, I can't access it from my corner of the Internet. Perhaps it only works from your network, or your Internet provider's network, or your country? If it's a residential ISP, it may be blocking port 80.

3 Likes
3

That is very interesting. I kept the same ISP and don't know about any policy blocking 80 port.

I will be looking into this.

4

Be sure to use the certbot renew --dry-run option so test with the Let's Encrypt staging system. Too many failures against the production LE system will get you temporarily blocked making debugging harder :slight_smile:

Or, use Let's Debug which is helpful for comms problems

3 Likes
5

Thanks Petercooperjr and MikeMcq, turns out my ISP was doing something peculiar : they withdrew my full stack IP during my home switching but let the port forwarding configuration on the router (giving me the illusion of a working forwarding when in fact everything was blocked). Since they're also my mobile carrier, I also had the illusion of everything working from outside when I actually was still on their network.

I used the option to assign myself a full stack IP and everything is working now. Would never have imagined such a thing.

3 Likes
6

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