Hi,
I'm experiencing what appears to be a stalled automatic SSL certificate provisioning issue for:
The project is on the Hobby plan.
Both domains are attached to the correct Vercel project and Vercel reports:
- verified: true
- misconfigured: false
- configured_correctly
- conflicts: []
- verificationError: null
- production deployment: Ready
However, no SSL certificate is being provisioned.
The DNS cutover was completed on September 21, 2026, and the domains have remained correctly configured since then.
Current certificate state:
- Vercel certificate inventory is empty
- domain objects show certificate: null
- domain objects show error: null
- TLS connections close before presenting any certificate
- no pending certificate/order is exposed
- no issuance failure is exposed
- no ACME failure is exposed
- no rate-limit error is exposed
The authoritative DNS currently matches Vercel's project-specific requirements exactly:
A @ → 216.198.79.1 A @ → 64.29.17.1
CNAME www → 25b7ef168fb9ba09.vercel-dns-017.com.
I've also checked the common certificate blockers:
- both authoritative GoDaddy nameservers return the intended records
- HTTP reaches the correct Vercel deployment
- /.well-known/acme-challenge/ reaches Vercel
- the www ACME path is not intercepted by the normal www redirect
- no conflicting AAAA record
- no restrictive CAA record
- no broken DNSSEC/DS chain
- no conflicting _acme-challenge record
- no project-level redirects or rewrites interfering with ACME
- no relevant Vercel TLS platform incident
Current behavior:
http://anuragbhavsar.com → reaches the correct Vercel deployment
https://anuragbhavsar.com → TLS closes before a certificate is presented
http://www.anuragbhavsar.com → correctly redirects toward the HTTPS apex, but the HTTPS destination cannot complete TLS because no certificate is available
I also went through Vercel's authenticated AI Support.
The AI confirmed that the configuration validates correctly, the certificate inventory is empty, and internal support review is required.
I attempted to escalate under:
Domains → SSL Certificates
but private case creation was unavailable because this project/account is on Hobby, and Vercel directed me to the Community.
I found several Community reports describing very similar behavior, including cases where valid configuration and working HTTP/ACME were present but no certificate was served.
At this point I don't see a remaining DNS-side or project-side blocker.
Could a Vercel team member please inspect whether automatic certificate provisioning is stuck for these domains and, if appropriate, retrigger provisioning from Vercel's side?
I'd also appreciate confirmation if there is an internal certificate issuance/provisioning state that isn't exposed through the public CLI/API.
Thank you.
