• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Can't renew Let's Encrypt Certificate, no _acme-challenge string in Plesk Web GUI

jradzuweit

Basic Pleskian
Server operating system version
Ubuntu 18.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.70 Update #2
Hi,
I try to renew a Let's Encrypt certificate, but I don't get a _acme-challenge string to place it in the TXT Record of a external DNS Server. How can I optain the _acme-challege string via the Plesk web interface or do I have to switch to some command line tool?

Regards
Jürgen
 
Are you requesting a wild card certificate? If not, it uses HTTP challenge instead of DNS challenge.
no I do not request a wild card certificate, have checked both options are off. But the details page of the certificate says

1750757995089.png
Is there a possibility to check whether a DNS or HTTP challenge was used?
 
Like I said, it does a HTTP challenge if you are not getting a wildcard and it does a DNS challenge if you do get a wildcard.
 
Back
Top