Profiles and services

Keep a localhost tunnel running after the terminal closes

Save a Proxlane background profile, check its Windows or Linux service, set a sharing deadline, and stop the tunnel when you are finished.

Written and reviewed by: ProxlaneOperated by CloudruUpdated: 2026-10-03

Owner

OS background service

Local configuration

Named profile

Temporary sharing

1 minute to 7 days

Before you start

Install and authenticate the CLI

Install the Windows or Linux CLI, run proxlane login as the same OS user, and approve the device in your browser. Start the local service you want to publish.

Read the installation guide

Prepare the service account

Use the OS user that owns your Proxlane configuration. First-time Windows service installation requires an elevated terminal for that user. Linux uses a systemd user service.

Step by step

01
Install the background service
Install the service as the same user that completed CLI login. Run Windows setup from an elevated terminal if service permissions require it.
```
proxlane service install
```
02
Save and start a named profile
The background option saves an enabled profile and starts the service. Use a descriptive name, then close the terminal only after checking the profile is ready.
```
proxlane http --background --name web 3000
proxlane service status --profile web
```
03
Check runtime and public access
Review status and service logs, then open the public URL. A ready relay connection and a responding local app are separate checks.
```
proxlane profile list
proxlane service logs -n 40
proxlane service doctor --profile web
```
04
Stop publishing explicitly
Disable the profile to keep its settings for later use. Remove it only when you no longer need the saved configuration. Closing a terminal or Launcher window does not disable a background profile.
```
proxlane profile disable web
proxlane service status --profile web
```

Set a deadline for temporary sharing

Publication expiry stops a tunnel at its deadline; it is different from an idle connection timeout. Use a duration from one minute to seven days. Expiry does not delete an endpoint reservation. Check the absolute deadline in status after creating or extending it.

proxlane http --background --name demo --expires-in 30m 3000
proxlane profile expiry demo --extend 30m
proxlane service status --profile demo

A persistent profile is not a fixed public address

An enabled profile survives your terminal or AI session, but random hostnames and ports may change on reconnect or restart. Reserve an HTTP hostname, custom domain, or TCP/UDP port on Plus or Pro if clients need the same address.

Keep the local application running too

The Proxlane service owns the tunnel, not your web app or game server. The local process must remain running and the computer must be online. Use your application's own process manager when it also needs to run unattended. The command below re-enables a saved web profile; to delete an unused demo profile and its settings, use proxlane profile remove demo separately.

proxlane profile enable web

Troubleshooting

Windows Access is denied

Install or start the service from an elevated terminal for the OS account that owns the Proxlane configuration. Do not switch to another account's configuration.

Tunnel exists but app is stopped

Run service doctor for the profile and restart the local application. Successful relay authentication does not prove the local HTTP/TCP service is responding.

A demo stays public

Check the correct profile's publication deadline and enabled state. Stop it with profile disable; an idle timeout alone does not end publication.

Frequently asked questions

Will closing Launcher stop the tunnel?

No. Enabled Launcher profiles are owned by the Windows background service. Disable the profile to stop publishing.

Is every background tunnel paid?

No. Background profiles follow your normal plan limits. Free can keep one HTTP or TCP tunnel active within its monthly transfer quota; UDP and endpoint reservations require Plus or Pro.

Proxlane