Attempting to renew cert / produced an unexpected error: Failed authorization procedure

Help
1

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), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: esquiroldespert.com

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/esquiroldespert.com-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 esquiroldespert.com
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (esquiroldespert.com-0001) from /etc/letsencrypt/renewal/esquiroldespert.com-0001.conf produced an unexpected error: Failed authorization procedure. esquiroldespert.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://esquiroldespert.com/.well-known/acme-challenge/_MxLIYgMECJjGD2_IujGNlp_yFL_35zX5Cq_fJuRLD0: Timeout during connect (likely firewall problem). Skipping.

Processing /etc/letsencrypt/renewal/esquiroldespert.com.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 esquiroldespert.com
http-01 challenge for www.esquiroldespert.com
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (esquiroldespert.com) from /etc/letsencrypt/renewal/esquiroldespert.com.conf produced an unexpected error: Failed authorization procedure. esquiroldespert.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://esquiroldespert.com/.well-known/acme-challenge/yJ677OVAbMbv9zVqmhi6YXaAKobG-1_CrM_f7_rQJrA: Timeout during connect (likely firewall problem). Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/esquiroldespert.com-0001/fullchain.pem (failure)
/etc/letsencrypt/live/esquiroldespert.com/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/esquiroldespert.com-0001/fullchain.pem (failure)
/etc/letsencrypt/live/esquiroldespert.com/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)

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

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: esquiroldespert.com
    Type: connection
    Detail: Fetching
    http://esquiroldespert.com/.well-known/acme-challenge/_MxLIYgMECJjGD2_IujGNlp_yFL_35zX5Cq_fJuRLD0:
    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: esquiroldespert.com
    Type: connection
    Detail: Fetching
    http://esquiroldespert.com/.well-known/acme-challenge/yJ677OVAbMbv9zVqmhi6YXaAKobG-1_CrM_f7_rQJrA:
    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): Apache version 2.4.29

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

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

2

I can’t reach those URL’s either. Are you blocking the HTTP port (80) somehow? Firewall? Missing router portmap? If so, please read https://letsencrypt.org/docs/allow-port-80/

Edit: well, I can’t reach your site with HTTPS (port 443) either… Seems to me your site is completely down. You don’t have an AAAA record, so it isn’t an IPv6 issue…

Also: why do you have an extra (the top) certificate which only has the base domain name while your second (the bottom one) has the www subdomain as wel as the base domain? Is the first cert used in your Apache configuration at all? If not, you might want to choose to delete it.

3

Hi Osiris, thank you for the answer. If I try to reach the URL esquiroldespert.com from another computer connected to internet through my mobilephone I can reach it. And I can see
Success! The esquiroldespert.com server block is working!

4

I can’t access it either.

Are you blocking any sort of traffic?

Foreign countries? Server ISPs?

1 Like
5

If 2 users on a forum aren't enough, you can use sites like https://downforeveryoneorjustme.com/esquiroldespert.com

Which says:

Is esquiroldespert.com down right now?
It's not just you! esquiroldespert.com is down.

6

Thank you both, so it’s obvious that there is something wrong. I’m not aware that I’m blocking nothing and I’m have the suspect that the problem is my router that was changed 3 months ago. It is a ZTE F680 and I thought it is right configured but it seems not. Do you thing that the router could be the problem or do you think the problem is the server?

7

Could be the problem the DDNS I have?

8

Timeouts are more likely to be caused by misconfigured routers or firewalls.

Could be indeed, if the IP address resolved by your domain is incorrect (i.e., old) and not updated correctly to your current IP address. Currently, it seems to resolve to 62.99.47.105.

9

This command gives this answer
jsanchez@PCJSG:~$ sudo ufw status
[sudo] contrasenya per a jsanchez:
Status: active

A Acció Des de

OpenSSH ALLOW Anywhere
Anywhere ALLOW 192.168.1.0/24
Apache Full ALLOW Anywhere
8069 ALLOW Anywhere
OpenSSH (v6) ALLOW Anywhere (v6)
Apache Full (v6) ALLOW Anywhere (v6)
8069 (v6) ALLOW Anywhere (v6)

And the DDNS updates very quickly if there is any change in the external IP. What I don’t know is that if standard DNS knows this changes also.

10

run this command:

curl ifconfig.me

if it says anything other than 62.99.47.105, your dns has a problem.

anyhow, that ip does not respond to pings and there is nothing responding and/or firewall in the way:

% sudo nmap -Pn -sSU esquiroldespert.com -p 22,80,443,8069
Starting Nmap 7.80 ( https://nmap.org ) at 2020-03-06 11:10 CET
Nmap scan report for esquiroldespert.com (62.99.47.105)
Host is up.
rDNS record for 62.99.47.105: 105.62-99-47.dynamic.clientes.euskaltel.es

PORT     STATE         SERVICE
22/tcp   filtered      ssh
80/tcp   filtered      http
443/tcp  filtered      https
8069/tcp filtered      unknown
22/udp   open|filtered ssh
80/udp   open|filtered http
443/udp  open|filtered https
8069/udp open|filtered unknown

Nmap done: 1 IP address (1 host up) scanned in 6.22 seconds
11

jsanchez@PCJSG:~$ curl ifconfig.me
62.99.29.77

And it is the correct one, it is the same I get if I visit www.miip.es

12

jsanchez@PCJSG:~$ sudo nmap -Pn -sSU esquiroldespert.com -p 22,80,443,8069
[sudo] contrasenya per a jsanchez:

Starting Nmap 7.60 ( https://nmap.org ) at 2020-03-06 11:47 CET
Nmap scan report for esquiroldespert.com (62.99.47.105)
Host is up.
rDNS record for 62.99.47.105: 105.62-99-47.dynamic.clientes.euskaltel.es

PORT STATE SERVICE
22/tcp filtered ssh
80/tcp filtered http
443/tcp filtered https
8069/tcp filtered unknown
22/udp open|filtered ssh
80/udp open|filtered http
443/udp open|filtered https
8069/udp open|filtered unknown

Nmap done: 1 IP address (1 host up) scanned in 11.33 seconds

but here, I don’t know why talk about 62.99.47.105 because this is not my current IP

13

because it's the ip your dns gives when asked for esquiroldespert.com

% for ns in `dig +short ns esquiroldespert.com`; do dig +short @$ns esquiroldespert.com a; done
62.99.47.105
62.99.47.105
62.99.47.105
62.99.47.105
62.99.47.105

Are you hosting at home? I suppose you are.

14

So, is this the origin of the problem? How can I fix it?

15

Your dynamic dns is not up to date. Update it.

16

Yes, I’m hosting at home.

17

I understand then that CDMON.COM is not updating the DNS with my current IP, amb I right?

But apparently, if I connect with CDMON dynamic IP DNS manager, it seems they have the correct IP
A esquiroldespert.com jsanchez 62.99.29.77

18

They are not updating it, but I don’t know if they are just slow, or if they expect you to do something to update it.

19

My computer has a cron job that checks and updates the information. The line that I show you:
A esquiroldespert.com jsanchez 62.99.29.77
is copied from their webpage.

20

then they are slow. start considering other dns providers. :smiley:

1 Like