SSL certificate stuck after 24h+ despite DNS, DNSSEC, and CAA all confirmed clean — ricovision.co.kr

Support
1

Hi Netlify team,

Following up on this issue — I’ve run through the standard troubleshooting checks and everything comes back clean on my end:

  • DNS propagation: Confirmed globally via whatsmydns.net (including Korea, US, EU, Asia) — NS records correctly point to Netlify DNS.

  • DNSSEC: Verified via Verisign DNSSEC analyzer — full chain of trust from root → .kr → co.kr validates correctly, no errors.

  • Let’s Debug (http-01 challenge): Ran the check for ricovision.co.kr — result: “All OK, no problems found.”

  • CAA records: Checked via multiple DNS lookup tools — no CAA records exist for the domain, so nothing should be blocking certificate issuance from any CA.

  • Domain registration: Confirmed active and in good standing at the registrar (Gabia), no conflicting old records.

I also tried clicking “Verify DNS configuration” again, which reset the status to “Waiting for DNS propagation,” but it has been stuck there since, even though propagation was already confirmed complete before I clicked it.

Given that DNS, DNSSEC, and the HTTP-01 challenge path are all confirmed working, this looks like it may be an issue on Netlify’s certificate provisioning pipeline rather than my DNS setup. Could someone please manually check/trigger the SSL certificate provisioning for this domain?

Site name: spiffy-gumption-a38eec
Custom domain: ricovision.co.kr (primary), www.ricovision.co.kr

Thanks for your help.

2

Update: The status now shows a clear cycle —

  1. “Verify DNS configuration” → succeeds (“DNS verification was successful ✓, ready to provision a TLS certificate”)
  2. Clicking “Provision certificate” → fails again with “We could not provision a Let’s Encrypt certificate for your custom domain.”

So DNS verification passes every time, but the actual certificate provisioning step fails every time right after. Combined with the fact that DNS propagation, DNSSEC, CAA, and the HTTP-01 challenge have all been independently confirmed clean (see my earlier comment), this really looks like a server-side issue in the provisioning pipeline for this specific domain/account. Could someone please check the backend logs and manually trigger issuance?