Jump hosts (bastions)

Many networks only allow SSH to internal servers through one hardened "jump host" or bastion. FusionTerm connects through it for you — the same as OpenSSH's ProxyJump.

1. Save the jump host itself as a normal SSH server (see Add a Linux server).
2. Open the internal server's settings, expand Advanced, and choose the jump host under Jump host (ProxyJump — connect through another saved session first).
3. Save and connect.

FusionTerm signs in to the jump host first, then to the internal server through it. Each hop uses its own saved username, password or key, and each hop's host key is checked — you may be asked to trust both the first time.

A list item with a jump host shows a →jump badge.

#Chains

A jump host can itself use a jump host, so you can chain several hops. FusionTerm refuses chains that loop back on themselves.

#Good to know

• If you delete a server that others use as their jump host, those servers switch to "connect directly" — check them afterwards.
• RDP (Windows) sessions can't use a jump host.
• In shared connections, a shared server can only jump through another shared server.