JetKVM Setup
How to connect a JetKVM device to KVM Fleet.
Prerequisites
- JetKVM hardware with network access
- SSH access (default:
root@<device-ip>, no password) - An enrollment token from the dashboard
Install the agent
The install script detects JetKVM automatically and uses /userdata/kvmfleet/ for both the binary and state. This path survives firmware updates.
Install paths
| File | Path |
|---|---|
| Binary | /userdata/kvmfleet/agent |
| State | /userdata/kvmfleet/state.json |
| Init script | /etc/init.d/S99kvmfleet |
Firmware updates
JetKVM firmware updates do not wipe /userdata/. The agent and its credentials persist across updates. After a firmware update, the agent restarts automatically via the init script.
Console access
The JetKVM web interface is proxied through the agent tunnel. Video stream, keyboard/mouse input, and device controls all work through the KVM Fleet dashboard.
Network
The agent connects outbound to app.kvmfleet.io:443 via WSS. No inbound ports required.
Troubleshooting
| Symptom | Fix |
|---|---|
| Agent won't start | Check logs: cat /tmp/kvmfleet-agent.log |
| Device offline in dashboard | Test connectivity: wget -q -O /dev/null https://app.kvmfleet.io && echo ok |
| Binary missing after update | Unlikely — /userdata/ persists. Re-run the install script if needed |
| Init script not running | Verify: ls -la /etc/init.d/S99kvmfleet and ensure it's executable |