SSH Port Forwarding (-L & -R)¶
Click + Tunnels on the right side of the terminal header to forward ports over your active SSH connection.
Local (-L) vs. Remote (-R)¶
Local (-L): Listen here, forward to the server¶
Binds 127.0.0.1:<Local port> on your Windows PC and forwards traffic through SSH to a target reachable from the server.
Common example — connect a local GUI tool to a remote database:
- Type: Local (
-L) - Local port:
5432 - Target host:
127.0.0.1 - Target port:
5432
Once toggled on, connect DBeaver, pgAdmin, or psql to 127.0.0.1:5432 while keeping PostgreSQL unexposed to the public internet.
Remote (-R): Listen on the server, forward here¶
Binds 127.0.0.1:<Server port> on the remote server and forwards incoming connections back to a service running on your PC.
Common example — expose a local dev server through your VPS:
- Type: Remote (
-R) - Server port:
8080 - Target host:
127.0.0.1 - Target port:
3000
Connections to 127.0.0.1:8080 on the server (for example from Caddy or Nginx) are tunneled straight to localhost:3000 on your PC.
Saving, editing & auto-start¶
- Save on host: Saves the tunnel configuration permanently on the host entry (uncheck for a temporary session-only tunnel).
- Edit anytime: Click the pencil icon on any tunnel row to adjust ports, names, or options; active tunnels restart automatically with the updated settings.
- Start automatically on connect: When enabled (
Auto), Hostess starts the tunnel in the background whenever you connect or reconnect to that host.
Multiple tabs to the same host
If an auto-started port is already bound by another open tab, Hostess won't interrupt your login with a modal popup — instead, the Tunnels button highlights the conflict quietly and shows the reason inside the popover.