Timeout during connect (likely firewall problem)

I experience the same problem as in this post:

Version: certbot 0.31.0

When running: sudo certbot renew --dry-run
I get:

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


Processing /etc/letsencrypt/renewal/shufflemix.com.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 shufflemix.com
http-01 challenge for shufflemix.de
http-01 challenge for shufflemix.nl
http-01 challenge for www.shufflemix.com
http-01 challenge for www.shufflemix.de
http-01 challenge for www.shufflemix.nl
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (shufflemix.com) from /etc/letsencrypt/renewal/shufflemix.com.conf produced an unexpected error: Failed authorization procedure. www.shufflemix.de (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://www.shufflemix.de/.well-known/acme-challenge/3cg2dKI85X-eJr7EGVMxELKYtCj5MeD5tTa5EQ13fC4: Error getting validation data. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/shufflemix.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/shufflemix.com/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: www.shufflemix.de
    Type: connection
    Detail: Fetching
    https://www.shufflemix.de/.well-known/acme-challenge/3cg2dKI85X-eJr7EGVMxELKYtCj5MeD5tTa5EQ13fC4:
    Error getting validation data

    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.

Timeout during connect (likely firewall problem) Is the main problem. But All domains are ok. No firewall applied. Using Fail2ban.

How to deal with this. Since the certs need to be renewed by tomorrow (its a clients site).

Are you getting any “Timeout during connect” errors? The error in your post is something else.

“Error getting validation data” is a bit of a generic error message – it can happen for multiple reasons (though I can only think of one right now).

For me, connecting to http://www.shufflemix.de/ over IPv6 times out.

Connecting to https://www.shufflemix.de/ over IPv6 gets a “No route to host” error.

Are you sure the IP address in your DNS records, network configuration and firewall settings are correct?

The CA software can fall back to IPv4 in some circumstances, but not always. You need to fix your site.

When running again: sudo certbot renew --dry-run

I get the same result saying the .nl is the problem? Attempting to renew cert (shufflemix.com) from /etc/letsencrypt/renewal/shufflemix.com.conf produced an unexpected error: Failed authorization procedure. www.shufflemix.nl (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://www.shufflemix.nl/.well-known/acme-challenge/RL-PV-iOBcWpmrTJsOBJBVNU2FnlwPSO3gvcYFQugNo: Error getting validation data. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/shufflemix.com/fullchain.pem (failure)

I will have a look at the DNS settings again. But seems a bit strange to me, that after just a few months when I first generated the certs the IPv6 is causing this? I know I added an AAA record for all the domains.
I referred to the other topic since there also was this “behaviour of random domain” giving the error.

Something probably changed since you last validated the names.

If you added the IPv6 IP to your DNS after last time, that would explain it, of course.

Or if your IPv6 connectivity was working before and only broke recently.

If the website didn’t used to redirect to HTTPS, that could explain it. Redirecting to HTTPS is fine, but redirecting to a broken destination won’t validate reliably, if at all. Let’s Encrypt will try to work around some issues for the first request, but less so – or not at all? – for subsequent requests. (Also, I don’t think there’s any fallback attempt for “no route to host” errors.)

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