Before you connect
You need a server address, an SSH username, and the authentication method supplied by its administrator. The SSH service must be running and reachable from your chosen route. A local native connection can work without an OmniTerm account; managed services may require sign-in.
Connect to a server
- Open Quick Connect or Add a server.
- Enter the hostname or IP address and username. Use the administrator's SSH port; the usual port is 22.
- Under Authentication & Security, choose a password or an SSH identity. A private key may need its own passphrase.
- Start the connection. Compare any new server fingerprint with one obtained independently from the server owner.
- When the terminal opens, confirm the machine and account before doing any work.
A profile might be named Development server, with address dev.example.com and a username supplied by your administrator. These are examples, not credentials or a public server operated by OmniTerm.
Decide what to save
A saved profile remembers how to find a server. It does not necessarily save the password. For reusable secrets, set up or unlock the vault and check the save options. Native credential storage also depends on an available operating-system keyring.
When a connection fails
Select the disconnected or error badge to open Connection Details. Check the address, port, authentication and route separately. Account login does not prove your SSH credentials are correct. Do not dismiss a changed fingerprint just to connect; follow host verification or troubleshooting.
Avoid typing while disconnected: some session workflows can queue input for reconnect.