DEVELOPER WORKFLOW
Share a localhost service through a temporary TCP tunnel
First confirm the service works on the host. Use Orylin's desktop TCP workflow to invite the other computer, then access the forwarded service through an unused local port on that computer.
Host: verify the service before creating an invitation
Suppose a development web server actually listens on 127.0.0.1:8080. Open http://127.0.0.1:8080 on the host and confirm the expected response before setting up forwarding. If local access fails, fix the service first.
The target address refers to the service on the host computer. It is not the invitation URL, the joining computer's loopback address or a request to expose every local port. Keep the service's own authentication enabled.
Host: create a connection for the exact TCP target
Open Orylin's TCP tunnel workflow and follow its desktop-app prompts. Enter the service's real target address and port, create an invitation and approve the connection as required.
Share the generated invitation with the intended person. Running the desktop app alone does not establish the tunnel, and changing target settings applies to the next connection.
Joining computer: choose a free port and test the service
Choose an unused local port, for example 2222, and join the invitation using the required desktop workflow. For this HTTP example, open http://127.0.0.1:2222 on the joining computer after the connection is established.
The host's port 8080 and the joining computer's port 2222 can differ. Use the original service protocol and credentials. An Orylin connection indicator is only an intermediate check: verify the actual application response through the mapped port.
Know when a TCP tunnel is the right tool
The current workflow forwards one TCP port per connection. It does not forward UDP, turn the devices into an all-port VPN or provide multi-port management within one session. The page does not automatically choose a free local port.
Disconnect when finished and confirm the forwarded service is no longer reachable through that session. This creates access between participating computers; it does not promise a persistent public HTTPS URL or a hosted preview site.
Questions and answers
Does this create a public URL for my localhost app?
This workflow maps a service to a local port on the joining computer. It does not promise a persistent public HTTPS address or hosted preview site.
Can the local port differ from the host port?
Yes. A host service on 127.0.0.1:8080 can be accessed through an unused local port such as 2222 on the joining computer, using the service's original protocol.
Does the tunnel remove the service's login?
No. The original service's authentication and protocol still apply. A tunnel carries the connection; it does not grant an application account or replace its access checks.
Connect