My production cert for civilbot.ai expired on Jun 22 and automatic renewal has been failing. The site is currently serving an expired cert and showing NET::ERR_CERT_COMMON_NAME_INVALID to all visitors. Could you investigate and re-trigger provisioning on your side?
Site details
- Site:
civilbot.netlify.app - Team / site slug:
[fill in] - Primary custom domain:
civilbot.ai - DNS: managed by Netlify DNS (zone hosted with you)
- Currently issued (expired) cert domains:
*.civilbot.net, civilbot.ai, civilbot.net - Created: Jan 24 · Updated: Mar 24 · Expired: Jun 22
Errors observed (in order)
-
First error on the HTTPS panel:
SniCertificate::CertificateValidationError: Unable to verify challenge for *.civilbot.ai:DNS problem: NXDOMAIN looking up TXT for _acme-challenge.civilbot.ai - check that a DNS record exists for this domainThis is unexpected —
civilbot.aiis on Netlify DNS, so Netlify should be writing the_acme-challengeTXT record automatically. It appears that wasn’t happening. -
After a hard refresh and removing the
civilbot.netdomain alias, the error changed to:SSL Provisioning is temporarily disabled because too many recent CertOrder creation with the site.So provisioning is now throttled.
Things I’ve tried
- Hard-refreshed the HTTPS panel
- Removed
civilbot.netfrom domain aliases to shrink the cert request - Confirmed Netlify DNS is managing the
civilbot.aizone
What I’m asking for
- Lift the rate-limit / throttle on cert provisioning for this site so renewal can be retried.
- Investigate why the
_acme-challenge.civilbot.aiTXT record wasn’t being written automatically given the zone is on Netlify DNS — so the next renewal cycle doesn’t fail the same way. - Confirm whether the
*.civilbot.aiwildcard is being added to the cert request automatically (it wasn’t on the original Jan 24 cert) and whether I should opt out of that if I’m not using wildcard subdomains.
Thanks — happy to share screenshots or grant team access if useful.
Yinglao