Hello Vercel team,
I have a custom-domain SSL/TLS provisioning issue.
Domain: twentytwoparts.com
www: www.twentytwoparts.com Project: twentytwoparts
DNS currently matches the configuration requested by vercel domains verify:
A @ → 216.198.79.1 A @ → 64.29.17.1
CNAME www → cc8cc8501dbce094.vercel-dns-017.com
Authoritative nameservers:
ns1.cloudoon.com ns2.cloudoon.net ns3.cloudoon.org
Public DNS resolves correctly.
Most importantly, HTTP reaches the correct Vercel deployment successfully:
curl -I http://twentytwoparts.com
returns:
HTTP/1.1 200 OK Server: Vercel
and includes normal X-Vercel-* headers.
However:
curl -I https://twentytwoparts.com
fails with:
schannel: failed to receive handshake, SSL/TLS connection failed
The same happens for www.
vercel certs ls returns:
No certificates found under twenty-two-parts
I also tested using Cloudflare WARP in full Warp mode and HTTPS still fails, so this does not appear to be only an MTN Nigeria routing issue.
The Vercel network debug script also shows TLS handshake failures against the newer Vercel edge ranges.
Since HTTP successfully reaches the correct Vercel deployment but TLS fails before HTTPS is established, could someone please check the domain's SSL certificate provisioning / SNI binding / edge TLS state and force a server-side domain revalidation or certificate reprovision?
I can provide the complete vercel-debug.txt output if required.
