Validation for domain fails with "timeout" error

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

curl -s -D - “” -o /dev/null

It produced this output:
HTTP/1.1 302 Moved Temporarily
Server: AkamaiGHost
Content-Length: 0
Date: Tue, 09 Jan 2018 17:22:55 GMT
Connection: keep-alive
My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):                       (unsigned)  599  CNAME           (unsigned)  600  CNAME        (unsigned)  300  CNAME  (unsigned)  30   A  (unsigned)  30   AAAA   2600:1480:2000:b0::

Oddly enough, i have trouble connecting to that over IPv6 too. Even though me and my nearest Akamai PoP are probably far away from the Let’s Encrypt validation systems.

(IPv4 works.)

You might need to contact Akamai?

I also get a “503”, “Service Unavailable - DNS” from (which is IPv4-only anyway) but that might be normal. (They probably deleted that validation file immediately after it failed.)

Edit: Akamai’s using anycast for those 2 IPs, and it looks like they’re returning the same 2 IPs regardless of location. Maybe it’s a routing issue specific to that address (range) rather than some sort of issue specific to one region.

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