← Back to Forum
0
Troubleshooting

My domain on LocaltoNet now gives ERR_SSL_PROTOCOL_ERROR but the reserved hostname still loads

Posted by oliviathomas • July 10, 2026

I didn't touch the local service, it's just plain HTTP on localhost and still reachable through the LocaltoNet hostname. My custom domain was working before and now browsers only throw ERR_SSL_PROTOCOL_ERROR on that one, which makes this feel like SSL/proxy config instead of the app itself.

For anyone who's run into this, is the usual culprit DNS not pointing where it should, Cloudflare orange-cloud type proxying, or something in the custom domain/certificate setup on the LocaltoNet side? Trying not to waste an hour power-cycling random things.

Comments (2)

charlesnguyen Jul 10, 2026

Set the DNS record for your custom domain to DNS only, not proxied, if you're on Cloudflare that's the orange cloud off. I hit the same exact SSL_PROTOCOL_ERROR when Cloudflare was trying to speak HTTPS to the tunnel side while the app behind it was only plain HTTP, the LocaltoNet hostname still worked fine the whole time.

laylastewart Jul 10, 2026

Check the cert status for the custom domain inside LocaltoNet, that's the other common breakage when the reserved hostname still works. I've had this exact split where DNS was fine but the custom-domain cert got unset/expired after a backend hiccup, and the browser just threw SSL_PROTOCOL_ERROR with zero useful hint.

×