Kaashvilla.com : could not provision a Let’s Encrypt certificate for your custom domain

Support
, ,
1

Domain: kaashvilla.com

Netlify site: phenomenal-kataifi-f1001b.netlify.app

Current situation:

Initially, DNS verification was successful in Netlify, but Let’s Encrypt certificate provisioning failed with the message:

“We could not provision a Let’s Encrypt certificate for your custom domain.”

Following troubleshooting, I removed and re-added the custom domain to the site. After re-adding, DNS verification temporarily failed, but it is now succeeding again.

Current status:

  • DNS verification is successful.

  • Certificate provisioning still fails.

  • HTTPS access shows NET::ERR_CERT_COMMON_NAME_INVALID.

DNS records (GoDaddy) — confirmed correct:

A @ 75.2.60.5
A @ 99.83.190.102
CNAME www → phenomenal-kataifi-f1001b.netlify.app

Additional checks:

  • DNSChecker confirms global propagation of the correct records.

  • curl -I http://kaashvilla.com returns “Server: Netlify”.

  • No AAAA records.

  • No CAA records.

  • DNSSEC is disabled.

  • ACME challenge path is reachable through Netlify.

Request:

Could someone please review the certificate provisioning logs for kaashvilla.com and www.kaashvilla.com and check whether there is a stuck or invalid Let’s Encrypt validation/certificate state on the backend?

The domain is correctly routed to Netlify, DNS verification succeeds, but certificate issuance continues to fail.

2

Additional observation:

The behavior is inconsistent.

  1. Clicking “Verify DNS Configuration” succeeds.

  2. Netlify reports that DNS verification was successful and allows certificate provisioning.

  3. After clicking “Provision Let’s Encrypt Certificate”, the process fails.

  4. The HTTPS page then reverts to:

“DNS verification failed”
“kaashvilla.com doesn’t appear to be served by Netlify”

This happens despite:

  • DNS records being correct and globally propagated.

  • The domain returning “Server: Netlify” via curl.

  • Previous successful DNS verification.

It appears the failure occurs during or immediately after certificate provisioning rather than during initial DNS validation.