Does the staging API have a problem at the moment? It just responds with an 500 internal server error when I issue the command
certbot-auto renew --dry-run -v. The
/acme/new-nonce calls deliver a code of 200 but the
/acme/new-order call shows:
https://acme-staging-v02.api.letsencrypt.org:443 "POST /acme/new-order HTTP/1.1" 500 114
Expires: Tue, 09 Jul 2019 14:00:56 GMT
Cache-Control: max-age=0, no-cache, no-store
Date: Tue, 09 Jul 2019 14:00:56 GMT
"detail": "Error creating new order",
Hi @dennisjac, welcome to the community forum.
Apologies, this appears to be a side-effect of a change that was activated in the staging environment and subsequently reverted. It looks like orders created during the affected period for a set of names will return 500 errors when creating a new order with the same set of names.
I recommend you delete your staging account ACME credentials and register a new account. That should resolve the errors for you.
Apologies for the service disruption. I'll ask someone on our SRE team to add a note to the staging environment status page.
I’m pursuing an alternative fix concurrently. I’ll provide updates here when possible.
The status page for the staging env has been updated to mark this event. Thanks again for reporting it @dennisjac. Our monitoring had detected this problem as well but it was misdiagnosed and a communication breakdown prevented a more timely fix.
Based on the alternative fix this is no longer required. Any orders created during the problematic period in staging will now 404 when accessed directly instead of 500ing. Any orders created by the same account for the same names will produce a new order instead of a 500 or the older broken order.
Please let me know if you run into any other difficulties. We’ll be monitoring the situation but I believe it has now been resolved.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.