• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Let's Encrypt failing with 500 "Error finalizing order" on all of our hosts since today

Bitpalast

Plesk addicted!
Plesk Guru
On all of our servers we are suddenly getting this error when Let's Encrypt certificates are installed or should be extended:

Code:
Invalid response from https://acme-v02.api.letsencrypt.org/acme/finalize/5801111111/1532222222.
Details:
Type: urn:ietf:params:acme:error:serverInternal
Status: 500
Detail: Error finalizing order

Following the attempt, an order file remains in /usr/local/psa/var/modules/letsencrypt/orders and needs to be manually deleted for further attempts. However, further attempts fail with the same error.

What's wrong so suddenly???

Verified on Plesk Onyx and Obsidian, latest Let's Encrypt extension installed. All machines and accounts affected including a 100% default installation test machine without customer accounts.
 
Last edited:
It's driving me crazy. Due to the high number of domains we operate I can see that the number of failures during these hours will cause tons of support requests soon. And all of them will need manual attention, because all the .json files in the /usr/local/psa/var/modules/letsencrypt/orders across all machines for the failed renewals and installations will need to be removed and then all these certificates will need to be recreated manually ... Hopefully Let's Encrypt will fix the issue soon. It doesn't really look like it considering their latest ticket status.
 
Back
Top