Jump hosts and bastions

Reach a server through one or more bastions: how to set the chain up, what follows it, how each hop signs in and checks its host key, and what the messages mean when a hop fails.

Applies to
Edgely Console
Updated

A jump host (or bastion) is a server you reach first in order to reach the servers behind it. In Edgely Console a connection can name another saved connection as its jump host, and that one can have its own, so a chain of any length is one click away. This page says how to set one up, what goes through it, how each hop signs in and checks its host key, and what the messages mean when a hop fails.

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

Set up a jump host

  1. Save the bastion as an ordinary connection with an SSH protocol, its credential and, if you need one, its own jump host.
  2. Edit the connection you want to reach behind it.
  3. In Jump Host / Gateway (left column, under Group), pick the bastion. The picker lists every saved connection that has an SSH protocol, except the one you are editing; type in Search connections... to narrow it, or pick None (direct connection) to remove the jump host.
  4. Save the connection.

Once a jump host is picked, Connection Path under the field draws the whole chain: You (Local), each hop with its name and host:port, then the target in green. Use it to check the order of a chain of several hops before you connect.

To chain more hops, give the jump host its own jump host: Edgely follows the chain from the target back to the first server that has none, and connects to that one first. A chain that loops back on itself is refused when you connect, with Circular jump host chain detected.

How the chain is built

Edgely opens an SSH connection to the first hop, asks it for a forwarded channel to the next hop's SSH port, and runs a new SSH connection to that hop inside the channel, and so on up to the target. Every hop is its own SSH session, encrypted end to end between your computer and that hop: a bastion relays bytes it cannot read, and the credentials of the servers behind it never pass through it in clear.

The hop sessions stay open while the connection is in use and close with it. Each feature that connects builds its own chain, so an SSH terminal and an SFTP tab on the same connection are two chains through the same bastion.

What goes through the jump host

Every feature that runs over SSH follows the connection's jump host:

FeatureThrough the jump host
SSH terminal, its SFTP side panel and its port forwarding rulesYes
SFTP and SCPYes
Multi-server transfer and the diff tool, on SFTPYes
Docker environments reached over SSH, and Docker Exec in themYes
Resource monitor, resource dashboard over SSH, security audit, packages analyzerYes
The MCP server's command tools (ssh_exec, ssh_exec_write, system_metrics) and file tools (file_list, file_read, file_mkdir, file_upload, file_download, file_delete)Yes
RDP, VNC, ARD, Telnet, FTP and FTPS, WebDAV, WinRM, KubernetesThey connect to their host directly

The editor offers Jump Host / Gateway on every connection, whatever its protocols, and only the SSH-based features above use it.

To reach an RDP, VNC or database port that only the bastion can see, add a Local port forwarding rule to the bastion's own connection (for example local port 13389 to the server's address and port 3389) with Auto-start on connect on, open the bastion's SSH terminal so the rule runs (or start it from the terminal's Tunnels panel), then point the RDP connection at 127.0.0.1 and the local port. See Port forwarding and tunnels.

Signing in at each hop

Each hop signs in with its own saved connection. Edgely takes its SSH protocol when it has one enabled, else SFTP, else SCP, and uses that protocol's own credential, or the connection's default credential when that protocol has none.

  • Password: the username comes from the credential, or from the connection when the credential has none.
  • SSH key: the connection's username is used, and the key's certificate is offered first when the key has one.
  • No credential: the hop signs in through your SSH agent, which needs a username on the connection.

Host keys along the chain

Every hop's host key is checked against your known_hosts, with the same rule as a direct connection: Settings > Connections > Strict Host Key Checking, on by default. A server Edgely has never seen is shown with its key and the question Trust new host key?; the dialog names the host and port of the server the key belongs to, so a bastion's key is asked about as the bastion. Trust saves the key and Edgely connects again. A chain of new servers is asked about one hop at a time, up to four questions in one connection attempt; connect again to answer the rest. With Strict Host Key Checking off, no hop is checked.

The MCP server's tools never show the question: they accept a server they have never seen and refuse one whose key has changed.

ProxyCommand and jump hosts

A connection reached through a jump host cannot also have a ProxyCommand: the editor refuses to save both ("A connection reached through a jump host cannot also have a ProxyCommand. Remove one of them."). The first hop of a chain can have one of its own, and Edgely then reaches that first hop through its command, and the rest of the chain through it.

Keep-alive and reconnecting

The SSH terminal and the SFTP tab use Connection Timeout and the keep-alive interval from Settings > Connections: the timeout covers reaching the first hop, the keep-alive applies to every hop, and a hop that misses three keep-alives in a row is dropped. Docker over SSH, SCP, transfers, the diff tool, the security audit and the packages analyzer connect with a 30-second timeout and a 60-second keep-alive. When a terminal reconnects, by Auto Reconnect or with Reconnect, the whole chain is built again.

Sync, export and import

  • Sync carries the link to the jump host between your devices, never a credential. On a device where the jump host is missing, the connection arrives without it. Picking None on one device leaves the jump host in place on the others; remove it there too.
  • Organization sharing leaves the jump host out: a connection shared with your organization arrives without it.
  • Exports (.econ, .efull, .eset) keep the link. Exporting a selection does not add the jump hosts it names, so select them as well. On import, the link is restored to the jump host from the same file, or to your own copy of it; when neither exists the connection is imported without one, and the result says so: "A connection was imported without its jump host: the jump host it referenced is not in this file or this vault."
  • Imports from MobaXterm, Remote Desktop Manager and CSV bring no jump host: set it after the import.
  • Duplicating a connection keeps its jump host.

Before you delete a connection that others use as their jump host, pick another jump host (or None) on those connections: they keep pointing at it and cannot connect until you do (Jump host '...' not found in connections). If it is already deleted, open each of them, pick None (direct connection) or another jump host in the picker, and save.

When a hop fails

The terminal shows Connection failed: followed by the reason. In these messages the hops are counted from the first server you connect to, which is hop 0; with one bastion, the bastion is hop 0 and the target hop 1.

MessageWhat it means
Gateway hop 0 (<name>) failed: Connection failed: ...Your computer could not reach the bastion: the address, the port, a firewall or the network. Connection timeout and Could not resolve host come the same way
Gateway hop 0 (<name>) failed: Authentication failed: ...The bastion refused its credential
Failed to open channel to hop 1 (<host>:<port>): ...The bastion is up but would not open a channel to the next server: that server is down or unreachable from the bastion, or the bastion's SSH server does not allow forwarding (AllowTcpForwarding)
SSH auth at hop 1 (<name>) failed: ...The server behind the bastion refused its credential, its host key was not accepted, or the handshake failed (for example, the port does not answer as an SSH server)
Connection <name> does not have SSH, SFTP or SCP enabledA connection in the chain has no SSH-based protocol
Credential not found: <id>A hop's credential is gone from the vault: pick another one on that connection
SSH agent authentication requires username in connectionA hop with no credential has no username to offer the agent
Circular jump host chain detectedThe chain loops back to a connection it already went through
Jump host '<id>' not found in connectionsThe connection names a jump host that was deleted

Each hop connects to the next one on its SSH protocol's port, or 22 when the connection has no SSH protocol. A server reached through a jump host is therefore given an SSH protocol with the right port, even when you open it only with SFTP or SCP.

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.