JetKVM Setup
Experimental
JetKVM support is Experimental. JetKVM doesn't run kvmd, so the agent
fronts its native web UI in raw reverse-proxy console mode.
How to connect a JetKVM device to KVM Fleet.
Prerequisites
- JetKVM with SSH/shell access enabled
- An enrollment token from the dashboard
Install the agent
JetKVM runs a BusyBox userland with a writable /userdata partition. The
installer detects it automatically (it looks for /userdata/kvm_config.json);
you can also force it with --device jetkvm:
If your JetKVM web UI requires a login, pass those credentials so the agent can authenticate the proxied console:
The agent installs under /userdata/kvmfleet/ and registers a BusyBox init
script so it survives reboots.
Console access
KVM Fleet wraps JetKVM's own web console behind the platform's access governance and audit trail, then proxies it through the agent's outbound tunnel. Every session is gated by your JIT policy and recorded in the audit log.
Network considerations
The agent makes only outbound HTTPS connections to app.kvmfleet.io on
port 443. No inbound ports need to be opened.
Troubleshooting
| Symptom | Fix |
|---|---|
| Agent won't start | Check the init script: /userdata/kvmfleet/init.sh status |
| Device shows offline | curl -I https://app.kvmfleet.io from the device |
| Console shows "device console unreachable" | Confirm the JetKVM web UI is reachable on http://localhost and re-run with the right --kvmd-user/--kvmd-pass if it needs auth |