HTTP tunnel guide
Expose localhost to the internet without port forwarding
Publish a local web app through a public HTTPS URL using Proxlane Launcher or the Go CLI, without changing router settings.
Example target
127.0.0.1:3000
Public endpoint
HTTPS URL
Free plan
1 active tunnel
Publish step by step
- 01
Start the web app locally
Confirm the app opens on this computer first. This guide uses port 3000, but any port from 1 to 65535 works.
- 02
Publish it from Launcher
Open Proxlane Launcher, choose Web app, enter the local port, and press Start. The background service keeps the tunnel running after the window closes.
- 03
Or use the CLI
Advanced users can create the same HTTP tunnel from a terminal.
proxlane http 3000 - 04
Open the public URL
When the tunnel is ready, click the HTTPS URL in Launcher or copy it to another device. Test from a network that is not your development machine when possible.
Why router configuration is not required
The Proxlane agent opens an outbound connection to the relay. Incoming HTTPS traffic reaches the relay and is carried back through that agent connection to your local HTTP service.
Your router does not need an inbound port-forwarding rule, and the local app can continue listening on a loopback address.
Use a random URL or reserve an endpoint
Free is suitable for short tests with a random hostname. Plus and Pro can reserve stable HTTP hostnames or use verified custom domains when a callback or shared preview must keep the same address.
Protect a shared development page
A public URL can be reached by anyone who knows it. Add Basic Auth, Bearer protection, or an IP allowlist when the page contains private development data. Protection is checked at the relay before traffic reaches localhost.
Troubleshooting
Connection refused
Start the local app and confirm the selected port. Try opening http://127.0.0.1:3000 on the same computer before testing the public URL.
Wrong page or framework port
Development servers may move to a different port when the default is busy. Use the port printed by the framework, then restart the Proxlane profile.
Tunnel is running but the app is unavailable
Open Diagnostics in Launcher. Relay authentication can succeed even while the local HTTP target is stopped, so check the Local HTTP result separately.
Frequently asked questions
Does the local app need HTTPS?
No. The local target can use HTTP. Proxlane terminates public HTTPS at the edge and forwards the request to the local HTTP service.
Does the tunnel stop when Launcher closes?
No. Launcher controls the Windows background service, so an enabled tunnel continues after the Launcher window closes.
Proxlane