Closed morgothulhu closed 5 months ago
Hi @morgothulhu, according to the internal logs, it looks like your domain has a CAA record set up which contains accounturi
parameter whose value does not match the ACME account ID that we are using (it does include letsencrypt.org
which is fine though). This prevents the automatic certificate provisioning process from proceeding.
Could you remove accounturi
paramter and retry the same process again?
thanks @magurotuna. It worked! resolving!
Problem description
anybody getting some issues with custom domains
Get automatic certificates
functionality?Keep on getting
Failed to provision a TLS certificate: challenge is not valid.
nslookup -q=cname _acme-challenge.{domain} 1.0.0.1
andnslookup -q=txt _acme-challenge.{domain} 1.0.0.1
are both returning the expecteda6010e7e9bb940f8db763402._acme.deno.dev.
Steps to reproduce
Expected behavior
Getting automatic certs
Environment
No response
Possible solution
No response
Additional context
No response