← Back to Forum
2

LocaltoNet + Nginx Proxy Manager for multiple local apps on one tunnel

I had been doing the dumb version, separate exposure for every little service, and finally cleaned it up. Now LocaltoNet just hits the proxy on one port, then Nginx Proxy Manager fans requests out by subdomain to a dashboard, a test API, and a static site on the same box.

Works fine so far and it's a lot less annoying to manage. Curious if other people using LocaltoNet are doing the same thing, or if you've got a cleaner setup for juggling a few local apps behind one public entry point.

Comments (2)

ethanrivera Jul 12, 2026

Yeah, that was exactly the mental shift for me, once I stopped thinking "one tunnel per app" and just aimed LocaltoNet at the proxy, the whole thing got way simpler. I still need to sort out how I want to handle certs long term though, are you terminating TLS at NPM too or doing something different?

sofiaclark Jul 12, 2026

Terminate TLS at NPM, that’s the least fiddly setup if LocaltoNet is just your public pipe, and then keep the backends plain HTTP on your LAN unless one app is especially sensitive. The one thing I’d add is lock NPM down so it only accepts traffic from localhost or your Docker network, because once you centralize everything there that box becomes the one spicy little choke point.

×