Site name: wellbeingsummit2026 (site_id 4e3a3d68-7f92-4158-9eb9-bac36bfdd140)
Custom domain: wellbeingsummit.angelapelizer.com
Our wildcard cert covering *.angelapelizer.com / angelapelizer.com (shared with another site on our team, angela-pelizer-cebec) expired 2026-07-04. Auto-renewal was failing with a DNS problem because the domain was on external DNS (Hostinger) without the ACME TXT record.
Timeline:
- We migrated angelapelizer.com to Netlify DNS and switched nameservers at the registrar (HostGator) to dns1-4.p07.nsone.net.
-
- DNS propagated (confirmed via 8.8.8.8 and 1.1.1.1, both now show the Netlify nameservers).
-
- We clicked “Renew certificate” a few times in Domain management while troubleshooting, which triggered a Let’s Encrypt rate limit:
- Acme::Client::Error:
- That retry-after time has passed, DNS is now correctly delegated to Netlify, but the certificate still hasn’t auto-renewed and clicking “Renew certificate” now returns “There are too many certificate creation with this site recently. Please try again later.”
- The site is currently live for an active ad campaign under wellbeingsummit2026.netlify.app (valid cert) but the custom domain wellbeingsummit.angelapelizer.com is serving the wrong cert (*.netlify.app) and showing a privacy error to visitors.
- Could someone on the team manually clear the rate limit / re-trigger provisioning for this domain? Happy to provide any further verification. Thanks!