Hi Vercel team/community,
I am having an HTTPS/TLS issue with my domain:
The domain is connected to my Vercel project and Vercel CLI confirms:
"Success! Valid Configuration: www.mylease.co.in is configured (CNAME record) and verified for project mylease-website."
DNS is currently configured as:
CNAME www → be404f91b34b91e0.vercel-dns-017.com.
The authoritative DNS trace also confirms this CNAME.
The CNAME target resolves to:
64.29.17.1 216.198.79.1
The apex domain works correctly:
https://mylease.co.in → HTTPS works and the Let's Encrypt certificate is valid.
However:
does not complete the TLS handshake.
HTTP works correctly:
http://www.mylease.co.in → HTTP 200 Server: Vercel
But HTTPS fails before a certificate is returned.
For example:
openssl s_client -connect 64.29.17.1:443 -servername www.mylease.co.in -tls1_2
returns:
CONNECTED(00000003)
no peer certificate available
SSL handshake has read 0 bytes and written 222 bytes
unexpected eof while reading
I get the same result against:
216.198.79.1:443
and also when connecting to:
76.76.21.21:443
The browser also shows that www.mylease.co.in is not accessible over HTTPS, while mylease.co.in works correctly.
The DNS configuration has already been changed from:
A www → 76.76.21.21
to the Vercel-recommended CNAME, and Vercel now reports the domain as verified.
Could someone please advise whether this indicates an issue with the managed SSL certificate/SNI binding for www.mylease.co.in on the Vercel edge?
Thank you.
UPDATE – Additional TLS diagnostic
I have now isolated the issue further.
DNS is correct and authoritative DNS confirms:
www.mylease.co.in CNAME be404f91b34b91e0.vercel-dns-017.com.
The CNAME target resolves to:
64.29.17.1 216.198.79.1
Vercel CLI reports:
"Success! Valid Configuration: www.mylease.co.in is configured (CNAME record) and verified for project mylease-website."
HTTP works:
http://www.mylease.co.in → HTTP 200 Server: Vercel
I tested TLS directly against both Vercel edge IPs.
WITH SNI:
openssl s_client -connect 64.29.17.1:443 -servername www.mylease.co.in -tls1_2
Result:
no peer certificate available SSL handshake has read 0 bytes and written 222 bytes unexpected eof while reading
The same result occurs with:
216.198.79.1:443
WITHOUT SNI:
openssl s_client -connect 64.29.17.1:443
Result:
subject=CN=no-sni.vercel-infra.com issuer=C=US, O=Let's Encrypt, CN=YR1
The same result occurs with:
216.198.79.1:443
This demonstrates that TLS is functioning on the Vercel edge and the edge is able to present a certificate, but when SNI is specifically www.mylease.co.in, the connection is terminated before a certificate is presented.
The apex domain mylease.co.in works correctly over HTTPS with its Let's Encrypt certificate.
Could Vercel engineering please check the SSL certificate/SNI binding and certificate provisioning for www.mylease.co.in across the Vercel edge?
It appears that the www hostname is verified and routed correctly, but its certificate is not being served during the TLS handshake.