2021-07-01 20:45:29,965:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "POST /acme/finalize/128873684/10782481674 HTTP/1.1" 500 112
2021-07-01 20:45:29,965:DEBUG:acme.client:Received response:
HTTP 500
Server: nginx
Date: Thu, 01 Jul 2021 20:45:29 GMT
Content-Type: application/problem+json
Content-Length: 112
Connection: keep-alive
Boulder-Requester: 128873684
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Replay-Nonce: 0002LUURklht7h2Aco1eMsHWxoNkXSha6E42Q79hhO_RCk8
{
"type": "urn:ietf:params:acme:error:serverInternal",
"detail": "Error finalizing order",
"status": 500
}
Please see the big red bar reading "Service status: Service Disruption" at the top of every page on this forum. Click on it for more info. Thanks.
Hi, we're all working on it.
Hi. I also have same problem when doing renew test
I'm not seeing red bar you mentioned. I also check the status page, everything is operational.
3 hours later and still working?
The issue was apparently resolved ~ 2-3 hours ago, so the status page is back to operational.
However, just a minute ago I got a 500 Internal Server Error on finalize on the staging server, haven't tested production at the moment. Looks like they're working on something, or something blew up again.
As my acme client just failed its scheduled renewal on staging, I did a manual retry and it looks like it's consistently failing on finalize. Server always responds with the generic error:
{
"type": "urn:ietf:params:acme:error:serverInternal",
"detail": "Error finalizing order",
"status": 500
}
The status page mentions problems with cached OCSP responses. Is this the cause of 500 on finalize, or is this unrelated?
[In the unlikely case you need any details, I have debug logs available]
We have fixes in progress for staging. Sorry for the inconvenience.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.