GoTerm
All guides

Everyday work

Hosts, groups and jump hosts

A host is a server you saved: its address, its user and how it signs in. A server on a private network is reached through a jump host, as with ssh -J.

Updated

On this page
  1. How a jump host works
  2. Connect from the search
  3. Sort hosts into groups
  4. Go through a jump host
  5. Three ways to sign in
  6. When a connection fails
  7. More on hosts
  8. Good to know

How a jump host works

GoTerm signs in to the jump host first, asks it for a connection to the private server, and signs in there too. The private server’s name is looked up inside its own network.

PRIVATE NETWORKSSHSSHGoTermthe gatewaybastiona public addressdb-0110.0.0.12web-0110.0.0.21k8s-ctl10.0.0.30
GoTerm connects to the bastion over SSH, then through it to three servers on the private network behind it.
  • One hop: a jump host can’t go through another.
  • Each signs in with its own saved password or key, and GoTerm shows neither.
  • Hosts behind a jump host work in the terminal and in Files, on any SSH port.

Connect from the search

  1. On Hosts, type where to connect in the search, as you would for ssh: deploy@web-09.example:2222.
  2. Or paste a whole command, such as ssh -p 2222 deploy@web-09.example.
  3. A saved host that points there shows up. If none does, choose the New host card: the form opens filled in.

Tip: An IPv6 address goes in brackets: root@[2001:db8::1]:22.

Sort hosts into groups

  1. On Hosts, open the arrow beside New host and choose New group.
  2. Name it, and pick its space: yours, or a team’s.
  3. Edit a host and pick the group under Group.

Go through a jump host

  1. Save the jump host first, as a host with a saved password or key.
  2. Open the private server’s host with Edit, or choose New host.
  3. Give its address and port as the jump host reaches it, such as 10.0.0.12. Any port works.
  4. Under Connect through, pick the jump host, then choose Save.

Tip: On the jump host’s menu, Use as jump host starts a new host that goes through it.

Three ways to sign in

Each host has one, under Auth method.

  • Password

    Saved in GoTerm
    Yes
    Typed each time
    No
    Team members use it
    Yes
  • Private key

    Saved in GoTerm
    Yes
    Typed each time
    No
    Team members use it
    Yes
  • Ask every time

    Saved in GoTerm
    No
    Typed each time
    Yes
    Team members use it
    No
Auth methodSaved in GoTermTyped each timeTeam members use it
PasswordYesNoYes
Private keyYesNoYes
Ask every timeNoYesNo
A hostweb-01Passwordsaved in the VaultPrivate keysaved in the VaultAsk every timetyped, never kept
A host signs in with a password or a private key saved in the Vault, or asks for its password each time and keeps none.

When a connection fails

GoTerm says why in plain words: no such host name, the port refused, no answer in time, or something other than SSH on that port. It doesn’t dial private or internal addresses itself: go through a jump host on that network.

Straight to a private addressSSHGoTermthe gatewaydb-0110.0.0.12: refusedThrough a jump hostSSHSSHGoTermthe gatewaybastion198.51.100.7db-0110.0.0.12
GoTerm won’t dial a private address such as 10.0.0.12 itself. Through a jump host on that network, it reaches it.
  • A refused password or key is told apart from a server that didn’t answer.
  • Every refused or failed connection goes in the audit log, with why.
  • In the desktop app’s Direct mode, your own computer dials, so addresses on your network work.

More on hosts

  • Docker containersOpen a shell inside any running container on a host you already reach. No extra ports.
  • Windows desktops over RDPOpen a Windows server’s desktop in a tab, right next to your SSH sessions.
RDPGoTermthe gatewayapia container on web-01workera container on web-01win-01a Windows desktop
From GoTerm, a shell inside each container on web-01, and a Windows server’s desktop in a tab.

Good to know

  • A jump host and the hosts behind it are in one space: all yours, or all one team’s.
  • A host behind a jump host can use any SSH port.
  • A jump host that others go through can’t be deleted until you take it off them.
  • Direct mode in the desktop app dials from your computer, so it can’t go through a jump host.
  • Give a host its own Terminal theme, a red one for production say, so you always know where you are.

Didn’t find your answer?

Write to us, and an engineer who builds GoTerm will reply.

Ask an engineer
  • Getting started

    Try the demo, add your first host and open a terminal.
  • Desktop app

    Install it on Windows, dial from your own computer, or use it free.
  • Sessions and sharing

    Keep sessions running, come back to them, and share them live.
  • Files

    Move files beside your terminal, or between hosts.
  • Web tabs and tunnels

    Open private pages and forward ports through a host.
  • Snippets

    Save commands once, and run them on one host or ten.
  • Monitors

    Check sites and ports, and get told when they go down.
  • Teams and roles

    People, teams, roles, host groups and each team’s activity.
  • Access and contractors

    Give a host for a few hours, and see what changed after.
  • Audit log and recordings

    Who did what, from where, and what their screen showed.
  • Running a workspace

    Your address and region, colours, settings and moves.
  • The Vault and your keys

    Save, share and replace passwords and private keys.
  • Security and sign-in

    Two-factor, confirmed devices, and how secrets are kept.
  • Allowed addresses

    Open your workspace only from your office’s network.
  • Private access

    Open your workspace only to your team’s own devices.