A device stuck at "Adopting…" indefinitely, or one that shows offline despite clearly being powered on, is a common enough issue to have a standard checklist rather than guessing each time.

Troubleshooting Steps

1. Confirm basic connectivity. Check the device has power (and PoE, if it needs it from the switch) and an active link light on its network port.
2. Check it can reach the console. If the device is on a different VLAN/subnet, confirm routing and any required firewall rules allow it to reach the console — this is the most common cause of a stuck adoption.
3. Reboot the device. Power-cycling it (or PoE power-cycling from the switch's port settings) resolves a surprising number of stuck-adoption cases.
4. Check for a firmware mismatch. A device running very old firmware can occasionally fail to adopt into a newer console version — updating the device's firmware standalone (if it has its own local access) before retrying can help.
5. Force adoption via SSH as a more direct option: SSH into the device (default credentials on a factory device, or ubnt/ubnt on older firmware) and run the set-inform command with your console's inform URL to point it at the controller directly.
6. Factory reset as a last resort. If nothing else works, a factory reset (usually a long-press of the physical reset button) clears any corrupted state and lets you start adoption fresh.

Common Questions

Is it safe to force adopt via SSH?

Yes, this is a standard and well-documented recovery method — it simply tells the device where to check in for management, the same information normal adoption provides through the dashboard.

The device shows offline but everything else on the network works fine. Why?

This usually points to the device itself (power, firmware, or a bad port/cable) rather than the broader network, since other devices are unaffected — start with the physical connection and a reboot before looking at network-wide causes.