Port forwarding and tunnels

Local, remote and SOCKS5 tunnels saved as rules on a connection, started with its SSH terminal and watched in the Tunnels panel.

Applies to
Edgely Console
Updated

A tunnel carries network traffic through an SSH connection: to reach a service that only the server can see, to let the server reach something on your computer, or to browse as if you were on the server's network. In Edgely Console a tunnel is usually a port forwarding rule saved on a connection, and it runs while that connection's SSH terminal is open.

Checked on 2026-10-26 against the code of Edgely Console 0.9.4, the release on Downloads.

Three kinds of tunnel

KindBadgeWhat it doesCommon use
LocalLOpens a port on your computer and carries what connects to it, through the SSH server, to an address and port of your choiceReach a database or a web console that only the server's network can see
RemoteROpens a port on the SSH server and carries what connects to it back to an address and port on your sideLet a program on the server call a service running on your computer
Dynamic (SOCKS5)DRuns a SOCKS5 proxy on your computer whose connections leave from the SSH serverPoint a browser or a tool at the server's network as a whole

Tunnels carry TCP.

Where rules are kept

Rules belong to a saved connection. Edit the connection: the Port Forwarding Rules section lists its rules, each with a drag grip, its L, R or D badge, its description, whether it starts on connect, and buttons to edit, duplicate or delete it. The section appears once the connection is saved, so create the connection first, then edit it to add rules.

A rule is saved the moment you click Add in the dialog: there is no need to save the connection afterwards, and cancelling the editor keeps it.

Running tunnels

Tunnels run inside an SSH terminal session: open the connection's SSH terminal.

  • Rules with Auto-start on connect start every time the terminal opens, and the terminal prints a [Tunnel] line for each one that started or failed.
  • Show Tunnels in the terminal toolbar opens the Tunnels panel at the bottom of the session, with the number of tunnels in its title.
  • Each tunnel in the panel has a status dot: Active, Not running, or red with the error in its tooltip when a running tunnel stops. A running tunnel has buttons to copy its address and to stop it and, for Local and Dynamic tunnels, shows the traffic it has carried and its open connections once there are some. A rule that is not running has a start button, and a tunnel that stopped on an error a Dismiss button.
  • The + in the panel's title opens the same dialog for a tunnel that runs in this session only, without saving a rule.

Every tunnel of a terminal runs on that terminal's SSH connection: closing the terminal, or losing the connection, stops them all. Auto-start rules come back the next time you open the terminal.

A local tunnel

  1. Edit the connection and click Add Rule under Port Forwarding Rules.
  2. In Add Port Forward, pick Local.
  3. Fill in:
    • Local Host: the address the port listens on. 127.0.0.1 (the default) keeps it to this computer; 0.0.0.0 lets other machines on your network use it.
    • Local Port: the port that opens on your computer. 0 lets the system pick a free one.
    • Remote Host: the destination, as the SSH server sees it (127.0.0.1 for a service on the server itself, or a name or address on its network).
    • Remote Port: the destination port.
  4. Fill in Description (optional) if you like, turn on Auto-start on connect for a tunnel you always want, and click Add.

Point any client at the local port as if the service ran on your computer. Quick Presets in the dialog fill in common cases.

A remote tunnel

  1. Click Add Rule and pick Remote.
  2. Fill in:
    • Remote Port: the port that opens on the SSH server.
    • Local Host: the address on your side the traffic goes to, usually 127.0.0.1.
    • Local Port: the port that service listens on.
  3. Click Add.

Edgely asks the SSH server to listen on its own loopback address, 127.0.0.1, whatever Remote Host says: programs running on the server reach your service at 127.0.0.1 and the remote port. Other machines on the server's network reach it only if the server's sshd_config sets GatewayPorts yes, which makes it listen on every address.

A dynamic tunnel (SOCKS5)

  1. Click Add Rule and pick Dynamic (SOCKS5), or use the SOCKS Proxy quick preset.
  2. Fill in Local Port (typically 1080) and Local Host (127.0.0.1).
  3. Click Add.

Set your browser or tool to use 127.0.0.1 and that port as a SOCKS5 proxy, with no username or password. Every connection it opens leaves from the SSH server, and host names are resolved on the server's side, so names that only exist on the remote network work. Addresses can be IPv4, IPv6 or host names.

Duplicating and reordering rules

  • Duplicate: the copy button on a rule opens Add Port Forward filled from that rule, with the port it listens on left empty, since two rules cannot listen on the same port: the Local Port for a Local or Dynamic rule (left empty, it is picked automatically), the Remote Port for a Remote rule (required). Click Add and the copy appears right under the original; Cancel adds nothing.
  • Reorder: drag a rule by the grip at its left edge. Auto-start rules start in that order, and the Tunnels panel lists the rules that are not running in that order too.

Both are saved at once, and the order is kept when Edgely restarts.

Tunnels through a jump host

A connection with a jump host runs its SSH session through the whole chain (see Jump hosts and bastions), and its tunnels run on that session: they come out at the connection's own server, the last one in the chain. Write Remote Host as that server sees the destination.

To reach something only the bastion can see, add the rule to the bastion's own connection, with Auto-start on connect on, and open the bastion's SSH terminal (or start the rule from its Tunnels panel). That is also how an RDP or VNC connection reaches a desktop behind a bastion: a Local rule on the bastion to the desktop's address and port, then the RDP or VNC connection pointed at 127.0.0.1 and the local port.

Common problems

  • The port is already taken. Another program listens on the local port: pick another port, or stop that program. The message reads Address already in use on macOS and Linux, and Only one usage of each socket address ... (os error 10048) on Windows.
  • A remote tunnel cannot be reached from another machine. Edgely asks the server for 127.0.0.1 (see above): call it from the server itself.
  • Tunnels keep stopping. The SSH connection behind them is dropping. Keep Alive in Settings > Connections is on by default; if it was turned off, turn it back on, or shorten the Keep Alive Interval.
  • The SSH server refuses the forward. Its administrator may have turned forwarding off (AllowTcpForwarding in the server's sshd_config).

Security notes

  • A dynamic tunnel sends everything its clients open through the SSH server. Stop it when you do not need it.
  • A local port is a service exposed on your computer. 0.0.0.0 opens it to every machine on your network.
  • A remote tunnel's port is reachable by every user and program on the SSH server, through its loopback address, and by the server's whole network when its sshd_config sets GatewayPorts yes.

Tips

  • Give rules descriptions (db-prod-readonly, local-dev-share): the rules list shows them.
  • When "the database is unreachable", the Tunnels panel at the bottom of the SSH terminal tells you at a glance whether the tunnel is running.

Something missing or wrong?

Documentation gaps are bugs. Tell us which page you were reading and what you expected to find.

Send feedback →

Product names, logos and brands mentioned on this page are the property of their respective owners. They are used for identification and comparison only, and their use does not imply any affiliation with or endorsement by them.