← Back to Forum
0
Proxy

LocaltoNet link always dumps people on the wrong page

Posted by ryanwilson • July 8, 2026

I’ve got a local app running fine, but the only page anyone actually needs is under a subpath, not the root. So when I hand someone the LocaltoNet URL, they hit /, stare at a useless page, and I get to explain URLs like it’s 1998.

Is this something people usually solve in the app itself with a redirect, or is there a sane way to make the tunnel/proxy send traffic straight to /admin or whatever by default? Mostly trying to avoid building a goofy workaround if there’s an obvious setting for it.

Comments (2)

bortiz Jul 8, 2026

Yeah, I'd probably just make / bounce to /dashboard or /admin in the app if that is the real entry point, least janky fix for sure. If LocaltoNet has a clean path rewrite then that is kinda free value, but app-level redirect feels like the safest play so people do not spawn into a blank screen.

gregorystewart Jul 8, 2026

I’d lean app-side too, mostly because it keeps behavior consistent whether you reach it through LocaltoNet, localhost, or a different proxy later. One thing I’d check first is whether / is ever meant to be an API root or health check, because that is the one case where an automatic redirect can get a little messy.

×