Kits ship with remote access disabled. Until the steps below are done locally, the unit will refuse SSH and remote desktop no matter how well it is connected to the network.
Important This must be done with a display and keyboard attached and the unit connected to the internet. Network reachability alone does not make the unit remotely manageable.
1. Connect a display and keyboard
Mobile Remove the HDMI dummy plug from the right-angle adapter on the compute module and keep it — it goes back in at the end. Connect HDMI to a monitor or use the built-in maintenance screen. Remove the cap from the USB-C port on the case, insert the supplied USB-C to dual USB-A cable, and connect a keyboard and mouse.
Drop-In Use the external HDMI port on the front panel. USB placement depends on the compute module — Elite units expose USB behind the removable dust cover; Pro units use the external USB port below the HDMI connector. The Drop-In Installation Guide has the panel map.
Note Some processor variants need an HDMI adapter to reach an external display. The adapter appropriate to your kit is supplied.
2. Log in and change the password
Log in with the default credentials supplied with the kit, then change the password immediately. Do this before the unit joins any network you do not control.
3. Install SSH
sudo apt update && sudo apt install openssh-server
sudo systemctl enable ssh
sudo systemctl start ssh4. Install remote desktop
Install the remote desktop application named in the User Guide, Section 4.3, from the software center. Then:
- Set a permanent password under Settings, then Security. Unattended access requires it.
- Enable LAN discovery so the unit can be reached by IP address.
- Test the connection from another machine while the display is still attached.
5. Put the HDMI dummy plug back
Mobile Confirm remote access works before disconnecting anything. Then disconnect the HDMI cable, reinstall the dummy plug in the adapter, disconnect the USB-C cable, and replace the protective cap.
Critical Without the dummy plug, remote desktop shows a blank screen or fails to connect. This is the most common remote desktop fault on a Mobile kit. See Mobile kits: which button is which.
Connecting afterward
| Connection | How |
|---|---|
| SSH | ssh dragon@<wardragon-ip> |
| Remote desktop | Enter the unit’s ID or IP address, then the permanent password |
| On the unit’s hotspot | Join the unit’s SSID; the unit is always at 192.168.12.1 |
| On a LAN | Read the assigned address from the router’s DHCP lease table, hostname wardragon |
| Direct cable, no router | See Connecting to a WarDragon over a direct Ethernet cable |
If it still refuses
| Symptom | Likely cause | Action |
|---|---|---|
| SSH refused | OpenSSH not installed | Complete step 3 from the local console |
| SSH times out | Wrong address or no network path | Verify the IP and that both ends share a network |
| Blank remote desktop | HDMI dummy plug missing | Reinstall the plug (Mobile) |
| Permission denied | Wrong credentials | Confirm the username and the changed password |
Related
- WarDragon User Guide, Section 4 — first boot and local setup
- WarDragon User Guide, Section 10.3 — remote access troubleshooting