Over the last month letsencrypt client takes almost one hour to create a new certificate (I think I have the same behavior for renewal).
I run this command on my server : ./letsencypt-auto certonly --agree-tos --standalone -d summer-beach-party.fr
With the debug flag I noticed that time is spent at these points : “Starting new HTTPS conenction”.
My server is hosted at online.net. It is configured to run over ipv4 and ipv6.
I’ve seen similar behaviour in the past (not specifically with letsencrypt) with servers that had IPv6 configured but not properly working, i.e. traffic being blocked by a firewall, etc. Maybe the client waits for a timeout and then falls back to IPv4. Can you confirm that something like
Possibly! I’d suggest filing an issue at https://github.com/letsencrypt/letsencrypt/. It probably doesn’t make sense to try and specifically detect IPv6 issues in the client, but there should probably be a timeout when making connections to the ACME server. The error message for those timeouts could suggest something like “please check the connectivity from your server to the outside Internet.”