← Back to Forum
1
Troubleshooting

Started getting SSL handshake failed on LocaltoNet custom domain, default URL still fine

Posted by ggomez • July 11, 2026

This looks isolated to the hostname layer, because the generated LocaltoNet address still serves the same local app and port without issue. DNS was already in place before this started, and I haven't changed anything on the local service side, so I'm trying to narrow the fault domain before I start flipping settings.

For anyone who's seen this with LocaltoNet, would you check certificate binding first, some DNS proxy/CDN setting, or a hostname/SNI mismatch? Also wondering if there's a quick way to confirm whether LocaltoNet is still presenting the cert expected for the custom domain.

Comments (1)

ggomez Jul 11, 2026

openssl s_client -connect yourdomain:443 -servername yourdomain is the one thing I'd run first, because it'll tell you right away what cert is actually being presented for the custom host. Yeah, that's exactly the part I'm trying to verify here since the LocaltoNet URL still works, if that comes back with the wrong cert or no SAN for my hostname then I'd know it's on the binding/SNI side and not the local app.

×