Error for Renewal 2018-07-23 20:27 GMT Let’s Encrypt: POST to failed

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.

I am trying to renew one of our existing certificate with LE. The validation has finished but API call to get the certificate fails. The last failed attempt was today “2018-07-23 20:27 GMT Let’s Encrypt: POST to failed.” The request is for .mil domain. Is there a new restriction on these domains recently? We were able to renew similar domain last week.

There’s no current restriction on .mil.

More detailed logs are required from the ACME client, “POST to … failed” could be caused by practically anything.

1 Like

Agreed (Thanks @_az!). You may find some historical mention of a .mil restriction from when Let's Encrypt originally launched but that restriction was lifted over a year ago (if memory serves me).

@cpu @_az We were reached out by a different team at LE regarding this timeouts. It appears it was an issue with CAA query timeouts.

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