Site: rssstaging / Custom domain: reaganstrategicsolutions.com
I’m unable to renew/provision a Let’s Encrypt certificate for this domain. Clicking “Renew certificate” consistently returns:
“certificate parameter is required when updating an existing certificate”
The certificate section also separately shows: “Certificate renewal incomplete: missing domains www.reaganstrategicsolutions.com” — even though www.reaganstrategicsolutions.com is already listed in the certificate’s own Domains field.
This is the exact same error I got at the very start of troubleshooting, before making any DNS changes at all, which strongly suggests this is a stuck certificate object on the backend rather than a DNS configuration issue.
Everything I’ve checked and fixed so far, working through your troubleshooting guide step by step:
- DNS verification shows successful. Apex A record correctly set to 75.2.60.5 (external DNS via GoDaddy)
- Confirmed no duplicate A records on the apex
- Confirmed www.reaganstrategicsolutions.com CNAME is set correctly to rssstaging.netlify.app (matching your recommended target, not pointed at the apex domain) — confirmed 100% globally propagated via DNSChecker.org
- Found and fully deleted an inactive Netlify DNS zone that had accidentally been created for this domain (was never delegated via nameservers, so had zero effect on live traffic or email)
- Removed a duplicate www domain alias that appeared after a remove/re-add cycle
- Found and fixed a separate issue: project visibility was set to Private, redirecting visitors to app.netlify.com. Changed to Public — this fixed general site accessibility but the certificate issue is unrelated and persists
- Tried “Provision certificate,” “Renew certificate” (multiple times, including just now after full DNS propagation), and a full remove/re-add of the custom domain — all produce either the same error or the same incomplete-renewal warning
I’ve now exhausted every self-service option in the dashboard and every cause listed in your troubleshooting docs. Could someone please check the certificate object on the backend for this site directly? It appears to be in a broken/inconsistent state.
Thanks for your help — happy to provide any additional info needed.