After beginning adoption, the UAP remains in “adopting” state for long period, without success. In some cases, the UAP appears as "adoption failed" in the controller.
Possible causes / recommended actions
- Software Firewall / Anti-virus prevents communication between controller-UAP.
- Disable Firewall (e.g., Windows Firewall) when testing connectivity between controller & UAPs.
- Assuming UAPs appear online, adjust the Firewall / AV settings to allow incoming/outgoing connections for UniFi controller (including ports).
- UAP is unable to reach the UniFi controller.
- Wait up to 30 seconds and refresh the controller page
- If the UAP is still “adopting”, make sure AP has access to Internet (e.g., SSH into the AP and ping unifi, it should come back right away, even if it fails)
- Assuming AP can ping the gateway, use a PC on the same network as the UAP and go through the Wizard, using default username/password and write down its IP address
- Install latest version of UniFi and go through the wizard steps, using ubnt/ubnt as admin's username/password connect UniFi APs and laptop (with controller installed) to the same router
- Check the router and write down the IPs of the AP (can be found under DHCP client table of router)
- SSH into each problematic AP and issue 'syswrapper.sh restore-default'
- UAP continues with default IP of 192.168.1.20—issue with DHCP server.
- Make sure that the DHCP server is active (router in network performing function)
- If router is leasing DHCP address to UAP, try ping/SSH again (UAP may be faulty)
- From the controller, make sure AP does obtain the IP from DHCP, note the IP from Controller PC, SSH into the AP (using the IP, default username/password is ubnt/ubnt) tail -f /var/log/messages copy and send the text output to firstname.lastname@example.org