Unifi-Adoption failed Status
As far as you know that unifi devices must be adopted in the unifi controller to manage and configure them. Though it is claimed that unifi devices are plug and play there are sometimes which totally contradicts it. The status Adoption failed is one of the cases.
Before troubleshooting an adoption issue, it is important to first check to ensure all the following requirements are met:
- All necessary ports need to be open on the controller and on the local network. The important port is TCP 8080 which is used for device and controller communication.
- The UniFi Controller and UniFi device must be able to communicate with each other over the network. In simple words, they must be pinging each other.
- The UniFi device must not be managed by another UniFi Controller or needs to be reset to a factory default state.
- If the device has been reset and is being readopted to a new controller, make sure the previous controller is no longer accessible to the device to ensure it is not re-adopted automatically. For example, if previous controller was hosted in an UniFi Cloud Key that is still connected to the network, disconnect that Cloud Key to make sure it is truly out of reach.
Once these requirements are confirmed to be in place, test the adoption again. If the device is not adopted, proceed with troubleshooting the issue.
Troubleshooting on Adoption failed
When troubleshooting adoption issues there are a number of potential causes and issues that could be at play. It is very important to narrow issues down as much as possible to a smaller number of potential causes; this will avoid expending unnecessary time and effort.
Let’s start with simple troubleshooting steps first:
If the IP is NOT reachable
- Ping the IP of the AP from the controller installed the system (Make sure that the AP and the controller are in the same network). The Ip must be reachable if not, then find the answer for the following questions:
1. Is the device powered? Led on it is glowing?
2. Check if the IP is right. run and IP scanner and check if the MAC ID of the AP matches with some other IP or its the same. The more simple way to do is login into your router and check if the device is being detected as a connected wired client under its clients.
3. If the AP is not being detected as a connected client or not getting an Ip from the network (Not shown in IP scanner either) you may need to change the cable and the port on which AP is connected.
4. Reset the device to factory default.
- If the above steps did not work and the AP still showing adoption failed then this suggests a device-specific issue for example:
- The UAP may be in a faulty state.
- Device firmware needs to be updated. Which can be done via TFTP.
If the IP is DO reachable
- So, You have checked and the IP is reachable for the AP and its still showing adoption failed. This isn’t a piece of total good news but yes some of it.
- First, check if you are pinging the right IP and to check that you will need to keep pinging the IP and remove the AP from the network simultaneously and see if the ping stops and recovers when you reconnect it. (There are still various ways to confirm that but I cannot come easier than this).
- Okay. So we have confirmed if the IP is right or wrong. If right then proceed with further steps and if wring check section If the IP is NOT reachable.
- Now since you have the right IP and AP on the controller but with status, adoption failed which happens only in two cases:
1. The controller and the AP communication is being blocked.
2. The Ap was managed by some other controller previously. For this, you can check our managed by other article to have help with.
- Now that we have narrowed down way much. Considering the first case I would suggest you disable the antivirus and firewall on the system temporarily and check if the status gets changed.
- If you are still stuck then forget the AP from the controller (Note down the IP of the AP). To forget the AP from the controller go to Device tab>Click on the AP>Config>Scroll down to Manage device>Click forget device.
- Now since Device is disappeared from the controller now Reset the device to factory default. (Make sure you reset the device fine the LED on it should be solid white/orange depends on the generation of the AP).
- Now reset back and check if the AP appears on the controller for adoption and adopt it fine.
Rare cases in which L3 adoption may need
- If you are still stuck and the AP still not adopting you may need to perform the L3 adoption.
1. Reset the AP to factory default.
2. Establish an SSH session with Ap.
3. The default credentials to login into the AP are: ubnt/ubnt
4. Now type the following command and hit enter:
set-inform http://ip-of-controller:8080/informA most common mistake is putting the wrong IP in the command. You need to put the IP of the system on which the controller is hosted. For example, if its cloud key then you should use the IP of the cloud key and if its a software based on Windows PC then you must use the IP of the PC on which the controller is installed.
5. After issuing the set-inform, the UniFi device will show up for adoption in the Devices section of the controller. Once you click Adopt, the device will appear to go offline or have the status of “Adopting”.
6. Once the device says it is Adopting or goes offline, whatever happens first, issue the command
set-informdescribed in step 4 again. This will permanently save the inform address, and the device will start provisioning.
If the device still show the error which it should not. You can always email me or put your issue in the comment box I will try to help you out as much I can.
Also, If you comment I get motivated.!
I hope the article was helpful and you have got what you were looking for. If you liked the article and if it was helpful please support and donate.