We recommend using our UniFi OS Consoles for the simplest, most streamlined adoption process. Most adoption issues are a result of third-party equipment or external factors such as firewalls and niche networking configurations.
The following are the only requirements for a standard device adoption:
- All devices need to have a valid IP address, subnet mask, and gateway assigned from their appropriate LAN/VLAN. This is done automatically when using a UniFi Gateway.
- There should be IP communication between the UniFi device and the Network Application.
- Port 8080 should be unrestricted for inbound and outbound traffic.
To adopt APs wirelessly, you must enable Wireless Meshing in your UniFi Network Application.
To adopt UniFi IoT devices and wireless cameras, you must enable New Device Auto-Link in your UniFi Network Application.
Your UniFi application and device are not on the same network
Excluding UniFi Network, UniFi Applications require devices to be connected on the same Layer 2 Network as the application host.
We only recommend Layer 3 (internet) adoption to advanced users, or those adopting devices to our Cloud Console. You can reference our Layer 3 Adoption guide.
There is a problem with the physical cabling connecting your device
Try to replace your cable to ensure your device is receiving proper power and information is flowing. Note that ethernet cables only support data transfer up to ~300 ft. (90 m).
A third-party firewall or antivirus software is blocking the device from being discovered
Device discovery requires allowing incoming and outbound broadcast traffic on port 8080. We recommend completely disabling any third-party firewalls to test adoption. Windows firewall is a common culprit leading to adoption problems for self-hosted Network Applications. For this reason, we always recommend using a UniFi OS Console for maximum compatibility.
You are using an outdated version of your application or UniFi OS
Ensure that you are running the latest versions of UniFi OS and your UniFi Applications are up-to-date. We always recommend enabling automatic updates to avoid this.
Your device appears as “Managed by Other”
This indicates that your device was already set up and adopted to a different application host. You can resolve this by factory resetting the device. This is done by pressing and holding the Reset button for 10 seconds. Alternatively, you may “Forget” the device from the other application host which will also result in a factory reset.
Ports or VLANs are misconfigured on your switch
Ensure that you have not created any port profiles or VLAN configurations that would prevent your devices from communicating with your application host. They should both be on the same VLAN.
If you've performed all of the steps above and still don’t see your device, see the Advanced adoption troubleshooting section below.
Advanced Issues and “Adoption Failed”
Your device did was unable to receive an IP address
A device retaining its default IP address (192.168.1.20) indicates that there was an issue receiving a new IP from your DHCP server. This is most common for self-hosted networks, or those using a third-party router. For this reason we recommend UniFi gateways for optimal setup experience.
The first step is to reboot your device to allow it an opportunity of receiving a new IP address. If this doesn’t work, try connecting it to a different port and using a different ethernet cable to rule out external factors.
If you are still unable to receive a proper IP address, you should check to make sure your network and DHCP server is properly configured. One simple test is to connect a different device to the same port and see if it obtains an IP address. If it does, this may indicate a problem with your device. As a last resort, try to reset it to factory default by pressing and holding the Reset button for 10 seconds. If the problem continues, RMA the device.
You have a modem/router combo in addition to a UniFi Gateway
There could be a potential network overlap between the two devices, resulting in a lack of internet connectivity for devices behind your UniFi gateway.
To fix this issue, switch your modem or router to bridged mode, or ask your ISP to make this configuration for you.
There is an external factor in your network partially blocking connectivity
It is possible you have an unknown element in your network causing partial connectivity issues resulting in the ability to see the UniFi device, but being unable to adopt it. In this case, you can SSH into the device using the following command:
set-inform http://[UniFi OS Console or Network Host Device IP Address]:8080/inform
Example: set-inform http:/192.168.1.1:8080/inform