• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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