Project: tbodmrcanalysis
Custom domain: tboeagence.dtdsodeci.ci (primary domain)
DNS: external (cloud4africa / MTN Cloud), CNAME tboeagence → tbodmrcanalysis.netlify.app, TTL 300
Domain added: 20 July 2026
Current state: “We could not provision a Let’s Encrypt certificate for your custom domain.”
The state previously oscillated between “Waiting on DNS propagation” and
“DNS verification was successful” on page refresh.
Evidence the domain is issuable:
- Let’s Debug (HTTP-01): All OK
- http://tboeagence.dtdsodeci.ci/.well-known/acme-challenge/ returns a clean
404 from the Netlify edge — no catch-all redirect is shadowing the ACME path - No CAA records at tboeagence.dtdsodeci.ci, dtdsodeci.ci or ci
- Zone is not DNSSEC-signed (no DS record at the .ci registry)
- The four authoritative nameservers answer CAA queries with NOERROR
(no SERVFAIL/REFUSED on unknown RR types) - No AAAA record in the zone; the IPv6 addresses seen externally are inherited
from the CNAME target, as expected
Most important data point: three other subdomains of the same zone —
collecte.dtdsodeci.ci, ressenticlients.dtdsodeci.ci and rattachement.dtdsodeci.ci —
are on the same Netlify account, same DNS provider and same registrar,
and all three were certified normally within 4 to 24 hours.
Only this project fails.
Request: could you please check the certificate provisioning logs for this project,
and the Let’s Encrypt authorization failure count for this identifier?
I suspect the retry cadence has saturated the failed-authorization limit for
this hostname. I have stopped clicking Verify DNS configuration to let it refill.