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.
Open the profile's Protocol tab to choose a mode and its settings. Use an alternate protocol only when your release offers it and the administrator approves it. Keep a working SSH profile while testing another method.
Local native Mosh and Telnet profiles use Direct network from the device. Configured Gateway sessions depend on the Gateway's protocol support, reachable network and admitted route, and require trust in its handling of protocol traffic and credentials. The supported installed Protected workspace exposes an agent terminal, VNC, RDP and persistent X11; it does not expose Mosh, Telnet, SFTP or port-forwarding controls. See availability for browser and package requirements.
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 under Protocol, review Mosh settings and the optional Mosh port range, then 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.
Mosh is a terminal session. Use a separate SSH or SFTP session for file transfers, and SSH for forwarding.
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. LeapTerm can restrict it to isolated environments.
Where Telnet is available, select it under Protocol, check the destination port, and explicitly select Allow unencrypted Telnet before connecting. That acknowledgement does not encrypt the session. Do not send a reusable password over an untrusted Telnet connection.
Other session modes
SFTP and FTP/FTPS are file-session choices rather than terminal shells. FTP is plaintext; FTPS depends on the server's TLS configuration. Supported native desktop builds can also offer serial and local-terminal modes; these are unavailable in the browser workspace.
For graphical sessions, use the separate remote desktop guide; terminal protocol settings do not automatically configure RDP or VNC.