• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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