PROBLEM Certificate location not specified in response

[weigi]

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. crt.sh | 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: zack-netzwerk.de

I ran this command:

It produced this output: Certificate location not specified in response

My web server is (include version): Plesk Onyx Version 17.8.11

I can login to a root shell on my machine (yes or no, or I don't know): now

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

Hello
I want to renew the certificate but I get the error " certificate location not specified in response"

PLEASE HELP the old certificate will expire soon
Thanks

[jrsyo]

seems related to the issue we raised earlier:

Suddenly getting "too many certificates" error across all domains

T…

[shanemielke]

Same issue here.

[artinstasik19]

Yes its here (

[JamesLE]

A change had accidentally enabled async order finalization in production. Some clients aren't yet compatible with that change in behavior on our side. I'm sorry about the trouble! We've now reverted the change, so things should be back to normal. We'll keep you updated on what we learn at our post-incident review.

[Osiris]

To all Plesk users reading this thread: please note that according to a thread on the Plesk Community (Resolved - URGENT Certificate location not specified in response Lets Encrypt | Plesk Forum) support for this new feature has been added to the Plesk Let's Encrypt extension since April this year (version 2.3.9).

Please update your Plesk and/or the Let's Encrypt extension to version 2.3.9 or newer to be future-proof with regard to asynchronous order finalization.