The Console is a local web interface for unit health, live detections, and a curated set of configuration. Not every kit ships with it installed.
Check whether the Console is already installed
From a browser running on the unit itself, open:
http://127.0.0.1:4280/If the Console loads, it is installed and you can stop here. If the browser reports that the connection was refused, continue with the installation below.
Note That address works only from a browser on the unit. It will not resolve from a separate laptop — see the access table further down.
Install
Log in locally or over SSH and run:
cd ~/WarDragon
git clone https://github.com/alphafox02/wardragon-console.git
cd wardragon-console
sudo packaging/install.shThe Console binds to loopback and is not exposed on the LAN. Nothing else on the unit needs to change.
Open the Console
| Access from | Address |
|---|---|
| The unit itself | http://127.0.0.1:4280/ |
| A laptop | SSH tunnel local port 4280 to 127.0.0.1:4280 on the unit, then open http://localhost:4280/ on the laptop |
| iOS tablet or phone | http://wardragon.local:4280/ |
| Android over USB tether | Use the fixed address shown in the Console’s Operator Notes panel |
An SSH tunnel from a laptop looks like this, substituting the unit’s address:
ssh -L 4280:127.0.0.1:4280 dragon@<wardragon-ip>What you will see
Tabs cover system health, GPS, per-source receiver status, live drones and signals, configuration with TAK certificate upload and a Restart button, and a read-only version check.
Under receiver status, the active sources are Wi-Fi, Bluetooth, and DJI. Legacy source slots that are not wired up on your kit stay down. That is normal, not a fault.
Critical Anyone with physical access to the USB tether path can write configuration and restart services. Treat physical access to the unit as full administrative access.
Related
- WarDragon User Guide, Section 7 — Console reference
- WarDragon User Guide, Section 9.5 — shutting down from the Console