← Back to Forum
0
Setup & Configuration

LocaltoNet with localhost app, do I need router port forwarding or not

Posted by rrobinson • July 11, 2026

I just installed it and my little web app loads fine on localhost, but I've never messed with networking beyond that. Before I start exposing it publicly, I'm trying to understand whether this tool creates the outside access on its own, or if I still need to log into my router and open ports manually.

Also not sure where firewall changes fit into this, if at all. Just want the basic setup path straight before I break something.

Comments (3)

rwebb Jul 11, 2026

LocaltoNet is meant to handle the public exposure itself, so you usually do not need router port forwarding first. The only thing I had to allow was the app making an outgoing connection in Windows Firewall, because if outbound traffic is blocked the tunnel will not come up.

elizabetholson Jul 11, 2026

Yep, and the one gotcha is your local app needs to listen on the actual local interface/port LocaltoNet is targeting, not just a weird dev bind that only your browser setup happens to reach. I've seen people blame the tunnel when the service was only bound to 127.0.0.1 or the wrong port, so I'd verify that part first before touching anything else.

rrobinson Jul 11, 2026

I checked the bind and yeah, that's the part I was fuzzy on, my app is only on localhost:3000 right now and LocaltoNet is pointing at that fine. So if it works in the browser on 127.0.0.1, am I good to go for the tunnel, or do I actually need it listening on 0.0.0.0 for this to work right?

×