Vercel custom domain TLS reset: www hostname fails while apex works (Pakistan)
Hello Vercel Community,
I'm experiencing a persistent TLS connection reset affecting www.p999guide.pk on my Vercel project p999.
The unusual behavior is that the apex domain works correctly, but the www hostname fails during TLS negotiation. The www hostname works normally when I connect through a VPN, but fails without VPN on both my normal ISP connection and a mobile hotspot.
Domain configuration
- Project:
p999 - Apex domain:
p999guide.pk - WWW domain:
www.p999guide.pk - Hosting: Vercel
- Location: Pakistan
- Vercel deployment URL: Working
- SSL certificate: Valid until January 23, 2027
Vercel support has checked the domain configuration from its diagnostic location and confirmed that both hostnames are verified and attached to the project. Their diagnostic location successfully accessed the www hostname and received HTTP 200.
1. Apex domain works without VPN
Command:
openssl s_client -connect 64.29.17.1:443 -servername p999guide.pk -briefResult:
Connecting to 64.29.17.1CONNECTION ESTABLISHEDProtocol version: TLSv1.3Ciphersuite: TLS_AES_128_GCM_SHA256Peer certificate: CN=*.p999guide.pkHash used: SHA256Signature type: rsa_pss_rsae_sha256Verification: OKNegotiated TLS1.3 group: X25519MLKEM7682. WWW hostname fails using the same IP
Command:
openssl s_client -connect 64.29.17.1:443 -servername www.p999guide.pk -briefResult:
Connecting to 64.29.17.1write:errno=54SSL_shutdown:shutdown while in initBoth tests use the same IP address, port, device, network and TLS client. The hostname supplied through SNI is the important difference.
3. Additional observations
Without VPN:
https://p999guide.pk/works and returns HTTP 308 redirecting towww.https://www.p999guide.pk/fails during TLS handshake.- TCP port 443 connects successfully.
- The connection resets immediately after the TLS ClientHello.
- Multiple Vercel IP addresses produce the same failure.
- The problem occurs on both my normal ISP connection and a mobile hotspot.
With VPN:
https://www.p999guide.pk/works normally.
The Vercel-generated deployment URL also works.
4. What I have already investigated
- DNS resolution
- Vercel custom-domain verification
- SSL certificate validity
- TCP connectivity on port 443
- TLS handshake using curl
- TLS handshake using OpenSSL
- Multiple Vercel edge IPs
- Different network connections
- VPN versus non-VPN access
- Vercel connectivity diagnostic report
Vercel support confirmed that the domain configuration looks correct from its diagnostic location.
5. Request for technical assistance
Could someone from the Vercel community or engineering team help investigate:
- Why does the same Vercel IP successfully complete TLS when SNI is
p999guide.pkbut reset the connection when SNI iswww.p999guide.pk? - Could there be a hostname-specific TLS/SNI routing or edge provisioning issue?
- Could this behavior be related to network filtering or routing affecting the
wwwhostname from Pakistan? - Is there any additional diagnostic that can identify where the TCP reset originates?
I am not assuming that Vercel is necessarily responsible for the reset. I would appreciate help identifying the source.
I can provide the complete redacted vercel-debug.txt report and additional curl/OpenSSL outputs if required.
Thank you.