Wildcard certificate (*.coreopsos.io) stuck expired — Renew certificate produces no state change

Site: willowy-froyo-971408.netlify.app
Team: Coreops

We have completed an extensive investigation before opening this case.

Current production configuration:

  • Primary domain: coreopsos.io
  • Alias: www.coreopsos.io (redirects to primary)
  • No wildcard domain is attached.
  • No branch domains exist.
  • No deploy previews exist.
  • No Git repository is connected (the site is deployed via Netlify Drop).

Current certificate state:

Certificate: Let’s Encrypt

Domains:

  • *.coreopsos.io
  • coreopsos.io

Created: Apr 7
Updated: Apr 25
Expired: Jul 6

Current HTTPS error:

Acme::Client::Error::RateLimited: too many failed authorizations (5) for “*.coreopsos.io

The retry window shown in the dashboard expired on July 11.

After that retry window had already passed, we performed exactly one manual “Renew certificate” operation.

Observed result:

  • No new provisioning started.
  • The “Updated” timestamp remained Apr 25.
  • The certificate remained expired.
  • The exact same error message remained after reloading the page.
  • No new status or provisioning activity appeared.

At this point it appears that certificate provisioning is stuck referencing an old wildcard certificate, even though the current production configuration only contains:

  • coreopsos.io
  • www.coreopsos.io

Could you please verify whether there is a stale certificate request or internal provisioning state associated with this site?

If appropriate, could you reset certificate provisioning and issue a certificate only for:

  • coreopsos.io
  • www.coreopsos.io

No DNS changes have been made during this investigation.

If you need any additional diagnostic information, screenshots, or read-only verification from our side, we’re happy to provide it. We intentionally avoided making further configuration changes to preserve the current state for investigation.

Thank you.