Was trying to verify that my segfault from https://github.com/icing/mod_md/issues/68 was actually fixed... I could not get a certificate issuance to succeed. > [md_acme_drive.c:317 err][22(Invalid argument)] beastie.csc.warwick.ac.uk: unexpected AUTHZ state 3 at https://acme-v01.api.letsencrypt.org/acme/authz/ After a few tries I looked at the URL that's reported by a2md and noticed that the validation call from LetsEncrypt had timed out > "challenges": [ > { > "type": "http-01", > "status": "invalid", > "error": { > "type": "urn:acme:error:connection", > "detail": "Fetching http://beastie.csc.warwick.ac.uk/.well-known/<snip>: Timeout", > "status": 400 seems to make sense to add this kind of error report to the log output to speed up figuring out what's going on. The actual issue seems to be in this case that LetsEncrypt is having issues validating over IPv6.