![ubiquiti device discovery tool pending ubiquiti device discovery tool pending](https://resources.static.liongard.com/images/ubiquiti-unifi-inspector.png)
Or you may also use FQDN for the application inform URL: Troubleshooting: Device (with static IP) fails to connect to the 元 UniFi Network application For example, if you are setting then ping from the device to determine if XYZ is resolvable/reachable. Make sure that the device can resolve the UniFi Network domain name. You’ll need to configure your DNS server to resolve ‘unifi’ to your UniFi Network host’s IP address. Launch UniFi Network, go to the Devices section, find the device that is to be adopted with the status “Pending Adoption” and click Adopt under Actions. In the Adopt window that will appear, select the UniFi Network host and the site that will be adopting the device (for multi-site hosts) and click Adopt. Go to and log in with your Ubiquiti SSO credentials.Ģ. Go to the Devices section and locate the model with the Pending Adoption status. The device to be adopted will appear as ready to be adopted. Go to and login with your Ubiquiti SSO credentials.ģ. To access the application remotely Remote Access will have to be enabled. If you encounter discovery issues please use the UniFi – Troubleshooting Device Adoption article to help you troubleshoot the issue.Īfter installing the Discovery tool plugin (freely available in Chrome Web Store) on a computer running Chrome browser, any locally-available, unmanaged UniFi Devices (i.e., same L2 network as your computer) will appear as “Pending Adoption” in the UniFi Cloud Access Portal as well as your UniFi Network application itself (in the Devices section in both cases). UniFi APs have a default inform URL Thus, the purpose of using DHCP option 43 or DNS is to allow the AP to know the IP of the UniFi Network application host. LAN port connected locally to access management features on the router (USG or third party). Also, remember that in order to adopt, the following conditions must be true in order to have internet access and also have access to the router from within the network (locally):Ģ. Please make sure you’re familiar with how a regular L2 adoption on UniFi works (where the devices and UniFi Network application are on the same network) before attempting 元 (remote) adoption.
![ubiquiti device discovery tool pending ubiquiti device discovery tool pending](https://coppers.io/wp-content/uploads/2020/02/unifi-cloud-controller-provisioning-status-2048x1117.png)
![ubiquiti device discovery tool pending ubiquiti device discovery tool pending](https://content.spiceworksstatic.com/service.community/p/post_images/0000425426/60aad3a3/attached_image/wifi3.png)
Either configure the DHCP server or DNS server.Create a virtual application instance on Amazon EC2.When you’re at the site, open a browser and navigate to Cloud: either the UniFi Remote Access Portal or the UniFi Network application (when launched using Cloud).Take a laptop to the device’s site to perform adoption via Chrome browser (easiest method).For example, for a large-scale project with many devices there are a few possible methods for the adoption of devices: In many deployments where it’s not possible to have the UniFi Network host running on-premise, you can run the UniFi Network application in the Cloud or your NOC. on Amazon EC2) or NOC.įor regular device adoption, see UniFi – Device adoption. You might use Layer 3 adoption for applications located in the cloud (e.g. Layer 3 adoption is the process of adopting a UniFi device to a remote UniFi Network application.