My domain is: central.enzed.me I ran this command: certbot --nginx -d central.enzed.me It produced this output: Failed authorization procedure. central.enzed.me (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http:/…

Those IPs are all the secondary validation servers, the primary validation server’s request seems to be missing. See this thread: ACME v1/v2: Validating challenges from multiple network vantage points Check that you haven’t got any hosts blocked on your firewall.

We don’t have any hosts blocked at the firewall level. We can use certbot successfully with other domains on the same host, just this one particular domain is having an issue.

It could have just been a temporary network stall. When I test right now, no timeout occurs: https://acme-v02.api.letsencrypt.org/acme/authz-v3/4711744348 . You should see a hit from 66.133. or 64.78. in your access log, alongside the 3 hits from AWS. Have you tried again recently?

I just gave it another try and it worked. Seems like it was just one of those transient things. Certbot is great, not so good though when you’re migrating a site and want to have the SSL in place before you flick the switch on the IP in DNS.

Failed Authorization (Timeout) But LetsEncrypt was able to access the server?!?

Help

Topic		Replies	Views
Failed authorization procedure Help	2	615	August 23, 2021
Certbot - Failed authorization procedure Help	1	687	May 13, 2022
Could not issue certificate using certbot, authorization error Help	6	673	October 13, 2022
Failed authorization procedure Help	3	672	May 28, 2019
Timeout during connect Help	4	598	December 12, 2019

Failed Authorization (Timeout) But LetsEncrypt was able to access the server?!?

Related topics