pjhtech ToolsFor an AP or switch stuck adopting after its controller address changes, correct the inform target with set-inform http://<controller-IP>:8080/inform. The device must reach that controller on TCP 8080. Use the separate ownership fix if it reports Managed by Other.
Correct an inform target on a supported AP or switch
On the supported AP/switch, sign in using its authorized SSH account. Replace 192.0.2.20 with the intended Network application’s address:
set-inform http://192.0.2.20:8080/inform- Check that the device appears in the intended Network site, then select Adopt.
- If requested by the adoption workflow, repeat set-inform after that step.
- Confirm the device connects after provisioning.
DHCP or DNS keeps sending the old controller address
If devices use DHCP discovery on a UniFi gateway, open Settings → Networks → management VLAN → Option 43. Set Application Host Address to the intended Network host if it still points to the old one. For DNS discovery, correct the DNS server’s stale unifi record instead. Repeat set-inform after correcting the discovery target.
For a site migration, restore the existing application’s backup on the destination before redirecting devices, as described in the ownership section below.
The device still cannot reach the inform target
If the device still cannot reach that target, allow its management subnet to TCP 8080 on the application host and intervening firewall. To check delivery, use ip address show and tcpdump -D to identify the AP’s management interface, then capture:
tcpdump -ni <management-interface> -c 30 'host 192.0.2.20 and tcp port 8080'Wait for an inform retry and stop with Ctrl+C. SYN followed by SYN-ACK shows TCP transport; repeated SYN without a reply means the host listener, firewall or return path needs checking. No packets means first confirm the interface and actual inform destination.
Where the device lacks capture tools, capture on the application host or a mirrored management port instead. On the application host, allow device-management sources to TCP 8080; local discovery additionally uses UDP 10001.
A successful TCP exchange followed by rejection calls for the ownership or compatibility branch below.
A new self-hosted application is a separate controller, not a viewer for the existing controller. Open the existing controller’s web address to manage devices already adopted there; installing another instance is not an adoption repair.
No management lease or fallback address 192.168.1.20
Open Settings → Networks → IP Leases beside the management network and find the device’s MAC address. With a third-party DHCP server, check its lease list instead. No lease, or the fallback address 192.168.1.20, sends you to the VLAN/DHCP path; an unexpected subnet sends you to the wrong-native-VLAN or rogue-DHCP branch. Read that network’s gateway and DNS settings and compare any device static settings under UniFi Devices → device → Settings → IP Settings.
In Ports → VLAN Viewer, trace the device port to the gateway. Select each port and compare Native VLAN / Network and Tagged VLAN Management. For untagged management, retain the correct native network. If Settings → IP Settings → Network Override is enabled on the AP, add that management VLAN to the tagged list on every required hop; it must not be native on the directly connected port. Network Override selects management separately from SSID client VLANs. VLAN troubleshooting.
A device can keep forwarding client traffic while its management connection is broken. Re-adopting or factory-resetting it will not repair a missing tag or route.
Managed by another application, or rejected after communication
For Managed by Other after replacing or resetting the console, restore a backup that already managed the device: on the replacement, open Settings → Control Plane → Backups → Restore and select that backup. Restoring changes the selected application/settings, so use the intended destination, not an unrelated running site.
For an intentional move from a self-hosted Network Server, download its Network backup from the same Backups area, restore it on the new host, and only then redirect the inform target as described in the migration procedure.
If no usable backup or supported ownership reassignment exists, the final option is a factory reset followed by adoption. With local access to the powered AP/switch, use its documented Reset button until the reset LED indication appears (typically 5–10 seconds; use the model instructions). This removes its configuration and interrupts its clients. Do not use Forget on a live managed device as a harmless refresh: it also resets the device.
If the application explicitly reports unsupported firmware/application compatibility, open the device in UniFi Devices and record its model and firmware, then compare the installed Network version with that model’s release requirements in Ubiquiti Downloads. Update only along a supported path. A generic Adoption Failed status alone does not identify a firmware defect.
Check the post-provisioning state
Confirm the device remains connected in the intended site and retains the expected management and client VLANs after provisioning. If it repeatedly disconnects, correlate uptime and link events before another adoption attempt.