We recommend using a UniFi OS Console for the simplest, most streamlined adoption process. Adoption issues typically result from third-party equipment usage or other environmental factors, such as firewalls or niche networking configurations.
To perform a standard device adoption, please ensure that:
- All devices have a valid IP address, subnet mask, and gateway assigned from the LAN/VLAN they are connected to. This is done automatically when using a UniFi Gateway.
- The UniFi device and the Network Application can communicate with each other via ping (ICMP traffic).
- TCP Port 8080 and UDP Port 10001 can receive inbound traffic and transmit 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 Network Application. You must also have at least one wired AP present and within range of the wireless AP you wish to adopt.
Here are some issues that may prevent device adoption:
Your UniFi OS Application and Device Are On Different Networks
All UniFi OS applications, other than UniFi Network, require adoptable devices to be connected to the same Layer 2 network as the hosting application.
Some third-party gateway users may notice that their UniFi devices do not appear. This is often because they are on a different VLAN than their host application. In these scenarios, Layer 3 (internet) adoption is required. For more details, see our Layer 3 Adoption Guide.
Note: We only recommend Layer 3 adoption to advanced users, or those adopting devices to a Cloud Console.
Faulty Device Cabling
If you do not see an upstream port or LED indicator light, there may be a problem with your device’s power or data connection. Try replacing your cable(s) to see if this resolves your adoption issue. Also, please note that Ethernet cables only support data transfer up to ~300 ft. (90 m).
Device Discovery is Being Blocked by a Third-Party Firewall or Antivirus Software
TCP Port 8080 and UDP Port 10001 must receive inbound broadcast traffic and transmit outbound traffic to facilitate device discovery and communication. As such, we recommend disabling any third-party firewalls prior to device adoption. Windows firewalls are common adoption prohibitors for self-hosted UniFi Network users. For this reason, we always recommend running the application on a UniFi OS Console.
Your UniFi OS and/or Application(s) Are Outdated
Please ensure that you are always running the latest versions of UniFi OS and your applications. To do so, we recommend enabling automatic updates. You may refer to community.ui.com/releases for information on our latest versions.
Your Device is Managed by Other
You can use one of these methods to adopt your device:
- Restore your UniFi OS Console or application from a backup during which the device was previously adopted.
- Use the Network Device SSH Authentication credentials associated with the configured on the original host to perform an advanced adoption. If you do not remember the credentials, you can find them in your UniFi Network System settings.
- Factory reset your UniFi device.
You may encounter this state if you have recently factory-reset your UniFi OS Console or UniFi Application without manually resetting your device, in which case it is still managed by the “old” application.
Note: If you are self-hosting your UniFi Network Application, you should only ever download the UniFi software on a single host-device. Some users mistakenly download this multiple times because they believe it is a requirement to manage their Network Application from other devices, but this is actually creating a completely new instance. To manage your network from another device, you can type in the IP address of your application host while connected to the same local network. Alternatively, you can enable Remote Access to manage your network anywhere.
Misconfigured Port Profiles or VLANs
Please ensure that you have not created any port profiles or VLAN configurations that are preventing communication between adoptable devices and your applications. Both should be on the same VLAN.
If none of the above are causing your adoption issue, read the section below.
Adoption Failures and Advanced Troubleshooting Issues
Your Device Cannot Obtain a New IP Address
If your device retains its default IP (192.168.1.20), it could be having issues obtaining a new one from your DHCP server. This is most common for self-hosted network or third-party router users. As such, we recommend using a UniFi Gateway to ensure the most optimal setup experience.
To resolve this, reboot your device so it can reattempt obtaining a new IP. If this doesn’t work, try connecting the device to a different port with a different Ethernet cable to rule out the possibility of a wiring or port-related issue.
If your device still cannot obtain a new IP, please ensure that your network and DHCP server are properly configured. A simple way to do this is by connecting a different device to the same port to see if it can obtain an IP. If it does, this may indicate a problem with your device. As a last resort, factory-reset the device by holding its Reset button for 10 seconds. If the problem persists, submit an RMA request for the device.
You Have a UniFi Gateway and a Modem/Router Combo
There could create a network overlap, resulting in poor connectivity for devices behind your UniFi Gateway.
To fix this, switch your modem or router to bridged mode, or ask your ISP to make this configuration for you.
An Unknown Network Factor is Partially Blocking Connectivity
If you suspect something within your network is partially blocking connectivity, you can attempt to manually point your device towards your Network Application by using the SSH method for Layer 3 adoption.
Expedite Your Support Request
Prior to reaching out to support, we recommend gathering/verifying the following information. Including these details in your request will expedite your support experience:
- How are you hosting your UniFi applications (i.e., UniFi OS Console vs. self-hosted)?
- What is your UniFi Network application version? You can refer to community.ui.com/releases for the latest available version.
- If you are using a UniFi OS Console, what UniFi OS firmware version are you using? You can refer to community.ui.com/releases for the latest available version.
- Is this your first time adopting this device?
- What color is the device’s LED indicator light? Is it blinking in a particular way? For status information, see Understanding Device LED Status Indicators.
- What is the device’s IP address? If the device doesn’t appear in your Network application, you can use the WiFiman mobile app (iOS / Android) or another IP scanner to find this information.
- Provide more information on your network’s topology. Is this device hardwired, or are you attempting a wireless adoption? Is the device connected to the same network/subnet, or is this a remote Layer 3 adoption?
- Provide a copy of your support file. More detailed instructions can be found here.
- Users with a UniFi OS Console should obtain their Support File from the UniFi OS settings (*.tgz extension).
- Users with a self-hosted Network application can obtain their support file from the Network application settings (*.supp extension).