Connections & authentication
Save the connection details
Select + Session. These are documentation examples, not public test servers.
| Field | Example | Meaning |
|---|---|---|
| Name | Production - web | Sidebar label |
| Host | 192.0.2.10 | Hostname or IP, without ssh:// |
| Port | 10022 | The server's actual SSH port |
| Username | demo | Remote account; an empty value is requested before connecting |
| Authentication | Password | Choose password or private key |
Save, then open the profile from Groups or Recents. The first click on an inactive restored tab starts it. After failure or cancellation, use Reconnect explicitly.
Read connection progress
The terminal area shows elapsed timestamps for preparation, resolution, TCP, SSH handshake, host verification, authentication, PTY and shell startup. TCP entries include the actual target address and port.
A successful connection switches to remote output. Failures retain the stage and reason. Reconnect starts a new log and never replays previous input. These records are separate from terminal output logging.
Verify the host
Verify a first-seen fingerprint through your administrator or another trusted channel. A changed host key blocks authentication. After independently confirming a legitimate change, remove the matching old entry in Host trust manager and verify again.
Remember a password
Remember password is off by default. If enabled, the password is stored in Windows Credential Manager only after a successful connection. On subsequent connections it is tried automatically after host verification.
A rejected saved password is attempted only once per connection, then the authentication dialog opens. Forget saved password removes the record. Saving a password does not bypass host verification or override a private-key preference.
Two kinds of copying
Duplicate Session on a tab uses the same saved profile and can reuse its saved password. Copy in the session manager creates a new profile ID and does not copy the credential record.
Private keys and pending authentication
Select the private-key file. Encrypted keys require a passphrase, which is not saved. ssh-agent, keyboard-interactive / MFA are currently unsupported.
Handle later clears the secret draft and keeps the request in the pending queue. Work in another terminal, then return through the pending login/authentication entry. The original timeout still applies.
See troubleshooting and configuration storage.
Single jump host
Save the gateway as a normal SSH session, including its username. In the target session, set Jump host to that gateway and enter the address reachable from the gateway as the target host. For example, a gateway on port 10022 can connect to a LAN server on port 22.
The gateway and target have separate host-key checks and password/private-key authentication. Saved passwords belong to their respective profiles; the gateway password is saved after gateway authentication succeeds, even if the target later fails. The gateway must allow TCP forwarding. Terminal channels and SFTP share the target connection; closing one terminal does not interrupt another channel or an active transfer.
Only one jump host is supported. A referenced gateway cannot use another gateway or be deleted until its references (including restored tabs) are removed. Missing references fail explicitly without a direct-connection fallback. Existing configurations still default to direct connections. Excel export includes the gateway name and address; Excel import remains unavailable.
For IP copy/paste actions, a jump connection uses the configured target IP, never the gateway IP as the remote IP. If the target is a hostname resolved by the gateway, the IP actions are disabled.