Site name: dashing-froyo-4be4be
Custom domain: zachariahcollett.com
DNS: External (GoDaddy)
I’m getting “We could not provision a Let’s Encrypt certificate for your custom domain” and it hasn’t resolved in over 48 hours. Visiting the domain gives ERR_CERT_COMMON_NAME_INVALID, which I understand means the default netlify.app certificate is being served instead of one for my domain.
The site loads correctly at dashing-froyo-4be4be.netlify.app, so the deploy itself is fine.
What I’ve already checked, following the SSL troubleshooting support guide:
- Apex A record is a single record pointing to 75.2.60.5, confirmed by querying GoDaddy’s nameservers (ns47/ns48.domaincontrol.com) directly, not just via a resolver
- www is a CNAME to dashing-froyo-4be4be.netlify.app and resolves correctly
- No AAAA records on the apex
- No CAA records on the domain
- DNSSEC is not enabled (no DS or DNSKEY records)
- No duplicate A records on the apex
- GoDaddy domain forwarding was enabled initially and has been removed — that was the original cause of the first failed attempts
- Only one site in my account is using this domain; Domain management lists the netlify.app address, zachariahcollett.com as primary, and www.zachariahcollett.com as the redirect
- Records have been correct and fully propagated for more than two days, verified from multiple public resolvers
My guess is that the early failures while forwarding was still active left the SSL state stuck, and the automatic retry window has now elapsed. Could someone reset the certificate state on the site so provisioning can be attempted again?
Happy to provide anything else that would help. Thank you.