Troubleshooting, limitations, and roadmap

The limits, stated plainly

Known properties of the hardware and the current software, not bugs:

• 4K tops out at 30 fps. The encoder's hardware ceiling; see the FAQ for why more capture bandwidth would not change it.
• The local HDMI output is 1080p 60 only, and only exists on the kit carrier; the standalone adapter build has no local output.
• HDCP-protected content does not capture. The bridge speaks HDCP 1.4 only, so sources that insist on newer HDCP will not send video. For a KVM controlling computers this rarely matters; for set-top boxes it will.
• Storage is the microSD card, full stop. Treat the card as the machine.
• No Wi-Fi configuration today. The radio hardware is present; the image does not drive it. Wired Ethernet is the supported path.
• No on-device updates today. Updating means reflashing the card until the update system lands.
• Attaching a disk image to the virtual drive is not yet in the console. The USB mass-storage device itself works; the interface for loading images into it is on the roadmap below.

Troubleshooting

The kit does not power on

Check which USB-C port the power is in. The target port (the Aura's OTG port) does not power the kit. Then check the supply: a plain 5 V 3 A adapter, not a fast-charge or PD charger, not a power bank, not a computer's USB port. PoE kits need an 802.3af/at switch or injector, not a passive PoE one.

No picture in the console

In order:

1. Is the source actually sending video? A sleeping machine sends nothing; wake it from the console's keyboard.
2. Check the HDMI cable into the board's input, at both ends.
3. If you just replugged HDMI while the kit was powered, wait a couple of seconds; the capture bridge detects the replug and recovers itself.
4. If you were changing EDIDs or cables and the picture stays gone, power cycle the kit. A power cycle re-runs the bridge's full setup and clears any state a hot replug left behind.

Low-resolution sources are fine: BIOS screens, POST, and boot menus at 640x480 capture and display correctly, and re-latch within a couple of seconds of a mode change.

The picture froze mid-session

If the source was unplugged, replugged, or changed resolution, the kit re-latches on its own; a full recovery can take around ten seconds, during which the console holds the last frame. If the target machine rebooted, the stream resumes as its video returns, and the keyboard keeps working throughout, so you can press the BIOS setup key while the screen is still catching up.

I cannot find the device on the network

The kit takes a DHCP address on Ethernet; find it in the router's client list. If it moved addresses, that is the DHCP lease expiring, and a reservation in your router pins it. Hostname discovery that survives address changes is planned.

I forgot my password

There is deliberately no recovery back door. Today the reset is manual: power off, take out the card, and on a Linux machine delete var/lib/warpkvm/users.json from the card's root filesystem, then boot; the device returns to the setup page with settings otherwise intact. Failing that, reflash the card, which resets everything. A supervised reset flow is planned.

The card will not boot

Reflash it in a card reader; the procedure and the deeper recovery modes are on the image page. The board itself cannot be bricked from software.

What's planned

The console already shows some settings dimmed with a note about the daemon release they arrive in. That is deliberate: the interface is built ahead of the daemon, and features light up as the daemon catches up, in roughly this order:

• Device basics: health readouts, reboot from the console, changing your password without a reset.
• Network and lifecycle: network configuration from the console, guided Tailscale setup, on-device updates with an A/B fallback so a bad update rolls back instead of needing a reflash, diagnostics, factory reset.
• Virtual media: uploading and storing disk images on the device and attaching them to the virtual drive from the console.
• Power and users: ATX power control with the WarpKVM ATX boards, Wake-on-LAN, multiple accounts, two-factor sign-in, API tokens.
• Integrations: MQTT and webhooks.

No dates on any of these, on purpose. Pre-orders are for the kit as described on the product page; everything in this list is direction, not a promise attached to your order.