• 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.

Question How to solve plesk and cloudflare ssl auto issue conflict

vikK

New Pleskian
Server operating system version
ubuntu
Plesk version and microupdate number
Version 18.0.44 Update #3
For one of my site cloudflare is also using Letencrypt CA to issue universal certificate which requires _acme-challenge validation. Plesk also uses the same method for ssl issuing verification.

So normally I would create a _acme-challenge NS record in cloudflare pointing to maindomain.com and let plesk managed the _acme-challenge. Cloudflare universal certificate was issued by their own CA or other CA than letsencrypt than doesn't require _acme-challenge TXT record.

I couldn't find anyway to change ssl verification method for plesk to non-DNS.

So how do I solve this issue? Anyone faced similar issue and managed to fix it?
 
I solve that simply by creating the txts in cloudflare necessary since the certificate validates the txts listed, now the other option is the certificate of origin and enable hsts
 
Back
Top