• 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 Let's Encrypt: Domain validation failed, but CAA records are correct

Wyrix

New Pleskian
I'm using the Let's Encrypt extension in Plesk Obsidian. With this extension, I'm trying to request a wildcard certificate, but it returns;
Domain validation failed for <domain>: Invalid response from <url>.
Type: urn:ietf:params:acme:error:caa
Status: 403
Detail: CAA record for <domain> prevents issuance

My DNS records are;
<domain>. CAA (issuewild) letsencrypt.org
<domain>. CAA (issue) ;
<domain>. CAA (iodef) mailto:<email>

Does somebody have an idea what's going wrong here? The logs aren't helping me.
 
It turns out that if you have a single domain certificate on a domain and want to change it to a wildcard certificate, you sometimes must have the issue CAA record set to 'letsencrypt.org'.

In my case, I'm changing all domains from single domain certificates to wildcard certificates and in 2 out of 30 domains, the issue CAA record was needed.
 
It turns out that if you have a single domain certificate on a domain and want to change it to a wildcard certificate, you sometimes must have the issue CAA record set to 'letsencrypt.org'.

In my case, I'm changing all domains from single domain certificates to wildcard certificates and in 2 out of 30 domains, the issue CAA record was needed.
You should mark it as solved then? Just to keep things clean in the beginning. We all browse eagerly Obsidian forum these days :)
 
Back
Top