Connections
SSH, RDP, VNC and every other protocol MangoSSH speaks directly, with no external client to install.
- SSH — Full terminal sessions, MangoSSH's deepest-featured protocol. Per-connection hardening covers X11 and agent forwarding, algorithm policy and session recording.
- RDP — A built-in canvas-based client running inside the MangoSSH window — no external mstsc or xfreerdp process. Supports RD Gateway, SSH-tunnelled RDP, shared folders, smartcard and printer redirection and clipboard sharing.
- VNC — Screen sharing to any VNC server, in the same sidebar and group system as everything else.
- File transfer — SFTP and FTP, either standalone or as a two-pane browser bound to an already-open SSH session. A TFTP server and client are included for network gear.
- Telnet and serial — For switches, routers and anything on a console cable.
- Kubectl and local terminal — Kubernetes exec sessions and a plain local shell, in the same tabbed workspace.
A session in each
Reaching hosts you cannot route to
A target behind a jump host connects through a bastion, and one behind a cloud broker connects through ProxyCommand — with presets for AWS SSM, GCP IAP, Cloudflare Access, Teleport, Tailscale and Azure Bastion.
Step-by-step guides
How to set each of these up, one task per page.
- SSH hosts, tab by tab →Every tab of the Add / Edit SSH Host form and what each setting does.
- Remote Desktop (RDP) →The embedded RDP client: display, clipboard, drives, gateways and recording.
- VNC and Apple Remote Desktop →The embedded VNC client and Apple Remote Desktop hosts.
- SFTP and file transfer →The file browser, the inline editor, Quick SFTP, FTP, TFTP and folder compare.
- Port forwarding and jump hosts →Local, remote and dynamic forwards, ProxyJump chains and auto-detected dev servers.
- Remote access by ID →Reach a machine with no port forwarding: the host agent, Connect by ID, P2P and the unattended service.
Full detail
Step-by-step instructions, how to check each one worked, and what to do when it did not.