rttys servers
Connection summary
Active sessions
Throughput (per second)
TX bytes/s
RX bytes/s
Devices
| Role | Tags | Local | Remote | State | Process | PID | FDs | TX (B/s) | RX (B/s) | TX total | RX total | Idle |
|---|
Active / recent sessions
| SID | Device | Status | Frontend ↔ | Device ↔ | TermData out | WS TX | WS RX | Dev TX | Dev RX | Total | Last seen | Notes |
|---|
Data flow path
🌐 Frontend (Browser)
WebSocket
xterm.js
xterm.js
idle
⚙ rttys server
Go · Gin · gorilla/ws
idle
📡 rtty-go client
Custom binary protocol
idle
🐚 Local PTY / Shell
/dev/pts/*
idle
Per-connection data (frontend ↔ rttys)
| Remote | State | PID | Process | TX total | RX total | TX/s | RX/s |
|---|
Per-connection data (rttys ↔ rtty-go)
| Remote | State | PID | Process | TX total | RX total | TX/s | RX/s |
|---|
Processes (rttys / rtty-go / caddy / gopanel)
| PID | Name | User | State | CPU% | RSS | Threads | FDs | Read B | Write B | Cmdline | Runtime |
|---|
Service control
These actions are forwarded to rttys's /service-control API, which calls systemctl on the host. Use with care.