• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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