Browser SSH Terminal Web UI
Access a remote shell directly from your browser. The NFLTR dashboard includes a full-featured xterm.js terminal — no local SSH client installation, no key distribution. Click "Connect" on any agent proxying an SSH server.
The target machine must have an SSH server (e.g. sshd) running and listening on the configured port (typically 22). The NFLTR agent proxies SSH traffic — it does not provide SSH itself. You also need valid SSH credentials (username + password or key) on the target machine.
How It Works
The browser connects to the NFLTR server over a WebSocket. The server bridges the WebSocket to the SSH tunnel established by the agent. The agent proxies SSH to the target machine. Full interactive terminal with colors, resize, and scrollback.
Terminal Preview
Last login: Mon Jan 13 14:22:31 2025 from 10.0.0.1
user@prod-api-01:~$ docker ps --format "table {{.Names}}\t{{.Status}}"
NAMES STATUS
api-server Up 14 days
postgres Up 14 days
redis Up 14 days
user@prod-api-01:~$ ▌
Features
🖥️ Full Terminal
xterm.js with 256-color support, mouse events, scrollback buffer, and clipboard integration.
📐 Auto Resize
Terminal resizes dynamically with the browser window. PTY dimensions sync automatically.
🔐 Session Auth
Uses your existing NFLTR session. No SSH keys to distribute or manage.
🌐 Zero Install
Works from any device with a modern browser. No SSH client, no PuTTY, no terminal app.
⚡ Low Latency
WebSocket connection to server, then gRPC tunnel to agent. Optimized for interactive typing.
📱 Mobile Ready
SSH from your phone or tablet. Touch-friendly terminal with on-screen keyboard support.
How to Enable
On the agent
# Start the agent with SSH port exposed
nfltr tcp 22 --name my-ssh-server
# Or forward to a specific SSH server on the network
nfltr tcp 22 --forward 192.168.1.100:22
From the dashboard
- Sign in to your NFLTR dashboard
- Find the agent in your Agents list
- Click the SSH button next to the agent name
- A terminal window opens in your browser
Prefer a local terminal? Use nfltr ssh-proxy --name <agent-id> from any machine with the CLI installed. See TCP & SSH Tunneling for details.
Use Cases
- Emergency access — Access servers running SSH from any device when you're away from your workstation.
- Shared access — Give team members browser-based access to SSH-enabled machines without distributing SSH keys to each member.
- Locked-down environments — Access servers from networks that block SSH (port 22) but allow HTTPS.
- Mobile ops — Run quick diagnostics from your phone during on-call incidents.
- Customer support — Provide temporary shell access to support engineers via session tokens.
Remote shell from any browser
No local SSH client needed — full terminal right in the dashboard. Requires an SSH server on the target machine.
Open Dashboard TCP & SSH →