Unable to issue certificate

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:
Install Certificate from Plesk
It produced this output:
Invalid response from https://acme-v02.api.letsencrypt.org/acme/finalize/2537897271/409375950191 Details: Type: urn:ietf:params:acme:error:orderNotReady Status: 403 Detail: Order's status ("pending") is not acceptable for finalization
My web server is (include version):
Apache 2.4.52
The operating system my web server runs on is (include version):
Plesk running on Ubuntu 22.04.5
My hosting provider, if applicable, is:
Own Server
I can login to a root shell on my machine (yes or no, or I don't know):
yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): Plesk Obsidian 18.0.70 Update #3
Web Pro Edition

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Sorry Domain is lakedeatondental.com

That is a bug in your Plesk ACME Client. It must wait for the order status to be "Ready". It is not doing that. It is trying to "Finalize" an order that is only in the "Pending" state.

Often with Let's Encrypt an order moves to "Ready" immediately after authorizations complete but this is not guaranteed and is not required in the ACME spec. You might get lucky just retrying if this is the case.

Another possible reason is that Plesk is not handling a prior failure properly.

In either case, you are best off asking Plesk support how best to proceed.

3 Likes

Thank you

2 Likes