When I tried to renew my certificat I got a timeout error
MY config is in webroot
the message after ‘$ certbot renew --dryrun’ command is
-------------------------------------------------------------------------------
Processing /etc/letsencrypt/renewal/cos.gdts.eu.conf
-------------------------------------------------------------------------------
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for cos.gdts.eu
Waiting for verification...
Cleaning up challenges
Attempting to renew cert (cos.gdts.eu) from /etc/letsencrypt/renewal/cos.gdts.eu.conf produced an unexpected error: Failed authorization procedure. cos.gdts.eu (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://cos.gdts.eu/.well-known/acme-challenge/bBhpFw2i9UD6KZ3srby1SHlB4w8MajciSBHJpBdW_Gk: Timeout. Skipping.
- The following errors were reported by the server:
Domain: cos.gdts.eu
Type: connection
Detail: Fetching
http://cos.gdts.eu/.well-known/acme-challenge/bBhpFw2i9UD6KZ3srby1SHlB4w8MajciSBHJpBdW_Gk:
Timeout
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.
And In my web server I have an ok (200) answer.
66.133.109.36 - - [12/Nov/2017:21:19:22 +0100] t=0 v=www.gdts.eu V=cos.gdts.eu "GET /.well-known/acme-challenge/bBhpFw2i9UD6KZ3srby1SHlB4w8MajciSBHJpBdW_Gk HP/1.1" 200 87 "-" "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)"
13.58.30.69 - - [12/Nov/2017:21:19:22 +0100] t=0 v=www.gdts.eu V=cos.gdts.eu "GET /.well-known/acme-challenge/bBhpFw2i9UD6KZ3srby1SHlB4w8MajciSBHJpBdW_Gk HTT1.1" 200 87 "-" "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)"
I don’t understand why I have a bad dry-run renew certbot
It might be a routing glitch because the Let’s Encrypt server now tries checking from multiple different locations.
@cpu, could you take a look at this? The log files suggest that the challenge file was successfully downloaded from two locations, but there was still a Timeout error.
I try again, renew it’s not ok
I send you my log server
I don’t have any problem with file wih no type,
<location /.well-known/acme-challenge/ >
ForceType text/plain
Here’s what the Validation Authority (VA) logged from our side for this attempt at 28/11/17 21:14:50. Recall that we perform validations from multiple vantage points for the staging environment. There are three remote VAs and one primary VA. For this example we’ll call the remote instances RVA_1 through RVA_3 and PVA_1 for the primary instance.
21:15:12 - RVA_1 starts a HTTP-01 validation
21:15:12 - RVA_2 starts a HTTP-01 validation
21:15:12 - RVA_3 starts a HTTP-01 validation
21:15:12 - RVA_1 registers a successful validation
21:15:12.467314 - PVA_1 starts a HTTP-01 validation
21:15:17 - RVA_2 times out - note that 21:15:17 - 21:15:12 = 5 seconds - the expected timeout.
21:15:17 - RVA_3 times out
21:15:17.719444 - P_VA1 times out.
Since three of the four validations timed-out, the overall validation is declared a failure due to timeout.
There’s no mystery from my side - it seems definitive that your challenge server is timing out on some (if not all!) of the challenge requests.
I hope this information makes it possible for you to figure out the timeout.
