SSL provisioning disabled — stuck pending authorizations on a wildcard I don’t use, please clear

Netlify site: ordixa[.]netlify[.]app
Custom domain: ordixaa[.]com (with www[.]ordixaa[.]com)
DNS: external — Namecheap default nameservers, NOT Netlify DNS
Plan: free

Current error:
“SSL Provisioning is temporarily disabled because CertAuthorization is reaching to pending limit.”

Before this, I was repeatedly getting:
“Acme::Client::Error::RateLimited: too many failed authorizations (5) for *[.]ordixaa[.]com”

The problem: all the failed/pending authorizations are for the WILDCARD *[.]ordixaa[.]com. I do not need or want a wildcard. My site lists only ordixaa[.]com and www[.]ordixaa[.]com as custom domains — there is no wildcard entry. Since I’m on external DNS, a wildcard can never validate, so these authorizations keep failing and piling up as pending.

My DNS is correct and resolves to Netlify:

  • ordixaa[.]com → A → 75[.]2[.]60[.]5
  • www[.]ordixaa[.]com → CNAME → ordixa[.]netlify[.]app

I believe there is a stale/inactive Netlify DNS zone and/or a stale certificate still bundling *[.]ordixaa[.]com from earlier attempts, which is why the wildcard keeps being requested.

Could you please:

  1. Clear the stuck pending certificate authorizations for this site,
  2. Delete any stale/inactive Netlify DNS zone for ordixaa[.]com, and
  3. Delete the stale certificate that still bundles *[.]ordixaa[.]com,

so a fresh certificate covering ONLY ordixaa[.]com and www[.]ordixaa[.]com can be provisioned?

Thank you.

Following up after a few days — still stuck, and I’ve now confirmed it’s purely the certificate, not my DNS. Would really appreciate a hand clearing the backend state.

What I’ve verified since posting:

  • My site loads perfectly at ordixa[.]netlify[.]app, so the deploy itself is healthy.
  • DNS resolves correctly to Netlify:
    • ordixaa[.]com → A → 75[.]2[.]60[.]5
    • www[.]ordixaa[.]com → CNAME → ordixa[.]netlify[.]app
  • I deleted the Netlify DNS zone for ordixaa[.]com (I’m on external DNS at Namecheap).
  • My site lists ONLY ordixaa[.]com and www[.]ordixaa[.]com as custom domains — there is no wildcard entry.

So everything on my side is correct. The only thing failing is SSL provisioning, currently showing:
“SSL Provisioning is temporarily disabled because CertAuthorization is reaching to pending limit.”
and previously the repeated “too many failed authorizations for *[.]ordixaa[.]com” rate-limit error.

The failures are all for the WILDCARD *[.]ordixaa[.]com, which I don’t use and which can’t validate on external DNS. I believe stale pending authorizations and/or a stale certificate bundling the wildcard are wedged in the backend.

Could you please clear the stuck pending authorizations and any stale certificate bundling *[.]ordixaa[.]com, so a fresh certificate for only ordixaa[.]com and www[.]ordixaa[.]com can provision? Thank you.