Hi — I have a persistent custom-domain issue on a Hobby project that I can't resolve from my side (and SSL support isn't available on Hobby), so posting here.
Domain: e-pindych.ru (+ www) · Project: katya-site · Team: iva-qs-projects
Symptom — the certificate exists but the edge never serves it:
- Dashboard shows "Valid Configuration" and SSL certificates are issued (visible in the dashboard and in Certificate Transparency logs — Let's Encrypt, valid until Sep 2026, including a fresh
*.e-pindych.ruwildcard). - But a TLS handshake to
e-pindych.ruandwww.e-pindych.rureturns no peer certificate for the SNI (SSL handshake has read 0 bytes). - Port 80 returns an empty reply.
- The same edge IP
216.198.79.1serves*.vercel.appcertificates correctly — so the edge is up, it just doesn't have this hostname bound. - Reproduced from multiple independent networks worldwide (not a local DNS/cache issue).
What I've tried (no effect):
- Waited many hours / overnight.
- Removed and re-added the domain several times.
- Redeployed production (fresh build).
- Migrated the domain to Vercel nameservers (
ns1/ns2.vercel-dns.com). Dashboard now shows "Nameservers: Vercel" and Vercel issued a fresh*.e-pindych.ruwildcard cert ~1h later — but 4+ hours later the edge still serves no certificate.
Everything verifiable looks correct:
- DNS: apex and
*ALIAS → Vercel;Aresolves to216.198.79.1. - CAA allows
letsencrypt.org(pluspki.goog,sectigo.com); noAAAA; no DNSSEC. - No incident on vercel-status.com.
This looks like an edge / domain-binding issue on Vercel's infrastructure: the certificate is issued but the serving layer never binds the hostname. Could someone from Vercel re-trigger / fix the edge binding for this domain? Happy to share project/domain IDs. Thanks!