Choose the server's protocol
SSH is the normal starting point for a secure terminal. Some installations also expose alternate protocols. Selecting one changes the requirements on the server and network; it does not convert an SSH-only server into another kind of service.
Use an alternate protocol only when your release offers it and the administrator approves it. Keep a working SSH profile while testing another method.
Mosh and changing networks
Mosh can help a terminal tolerate changing network addresses and interruptions. It requires compatible remote support and a route that carries the necessary traffic. A successful SSH handshake does not prove the subsequent Mosh traffic can cross a firewall or relay.
- Confirm that the remote machine has the required Mosh support.
- Confirm that the network and route allow its traffic.
- Select Mosh where available and connect with the approved authentication.
- Check the actual session status before assuming roaming protection is active.
A WebSocket-only self-hosted kit is not automatically a datagram relay. Check your particular kit and client for compatibility.
Telnet is not encrypted
Telnet sends traffic and credentials without SSH's encryption. Treat it as an isolated-network compatibility tool, not an alternative for internet administration. OmniTerm can restrict it to isolated environments.
Do not send a reusable password over an untrusted Telnet connection. For graphical sessions, use the separate remote desktop guide; terminal protocol settings do not automatically configure RDP or VNC.