ubiquiti device discovery tool does not find cloud key

#Ubiquiti device discovery tool does not find cloud key install#
#Ubiquiti device discovery tool does not find cloud key windows 10#
#Ubiquiti device discovery tool does not find cloud key password#
#Ubiquiti device discovery tool does not find cloud key windows#

The biggest issue I was having is that the USG needed to be manually restarted after ANY change. Once the CK restarts it should see the USG and everything should be working. You really just need to be able to restore the firmware on the CK with the backup you just made from the local controller (make sure this controller is turned off). Set up CK (it doesn't connect to USG at this time). USG showed up in controller and now can see the world wide web!īackup controller to HDD. USG went back into Provisioning and then Adoption Failed message appeared. Changed IP address/DHCP range on USG to 192.168.0.1. Controller found USG and adopted it without issue. USG WAN was plugged into existing router (Netgear with 192.168.1.X subnet).

#Ubiquiti device discovery tool does not find cloud key install#

Here's the solution for anyone else with this issue.įirst I had to install the controller software on my local machine (5.2.7 for Mac).

Set a static IP address on my laptop of 192.168.1.10 and see if I can then find both the USG and the CloudKey.Įdit: I finally got this working. What are your suggestions? I'm going to turn off DHCP on the netgear today and have it act as a dumb switch. I'm aware the USG can only be controlled by once instance of the software at a time. I was able to adopt the USG using a local install of the UniFi controller but then I couldn't hand it off to the CloudKey. I'm currently using the Netgear as the DHCP server (192.168.1.1) which might be the reason it's failing. The problem arises when I try to adopt the USG. I am able to configure the CloudKey without issue. On my netgear router I am able to see the CloudKey and the USG. Anyway, I have a brand new USG and a brand new Cloudkey that I want to configure together. If you have any questions, just drop a comment below.No idea why I was having issues with this last night maybe because it was late.

If you are still unable the adopt the Access Point, then follow this article where we are going to solve the adoption failed error. Type info and press enter to see the status of the access point: UAP-AC-Lite-BZ.5.43.36# infoĪs you can see in the results above, the inform URL is set correctly, but the device is still waiting for adoption. If the access point still doesn’t show up in the controller, then check if the settings are applied correctly. You should now see the access point in the controller, ready for adoption. Complete the adoption in the controller.Type the following command and press enter:

So if the IP Address of your controller is 192.168.1.1, then the inform URL is : The inform URL is the IP Address of your controller followed by the port number: 8080/inform.

#Ubiquiti device discovery tool does not find cloud key password#

Type ssh (replace 192.168.1.142 with the IP Address of your access point)Įnter the default password ubnt (or lookup the SSH details in your controller)

#Ubiquiti device discovery tool does not find cloud key windows#

Press Windows key + X (or right-click your start menu) To do this we are going to use PowerShell.ġ. We first need to connect the access point over SSH. You can use the Ubiquiti Discovery Tool for this or Advanced Ip Scanner. We also need to know the IP Address of the access point. This doesn’t always work, better is to use the IP Address of the controller, for example: Unifi is the internal DNS name of your Unifi Controller. Note The default inform url is unifi:8080/inform. If you have changed it, then you can look it up in the controller under System > Application Configuration > Device SSH Authentication. The default SSH username and password are ubnt.

#Ubiquiti device discovery tool does not find cloud key windows 10#

You don’t need an SSH client for this, we can simply use PowerShell for this, which is installed by default on all Windows 10 and 11 computers. To set the inform URL we need to connect over SSH to the Unifi access point. This doesn’t always work, so we need to tell the access point the correct address of the Unifi Controller. By default, the access point will search the network for the controller, using the default DNS name unifi. The Set-Inform URL tells the Unifi Access Point where the controller is located. In this article, I will explain how you can use the Set-Inform command on an Unifi Access Point. But sometimes the device won’t show up in the controller. When the status led of your new access point is steady white (or steady amber for older access points) then it’s waiting for adoption.

But what if your new access point isn’t showing up in your controller? I am on the SSID that they are broadcasting, however I cannot find my cloud key in the discovery tool. Unifi Access points are great devices, most of the time when you connect a new Access Point they will find the controller within a minute. Hi, I have a cloud key that is managing 3 UAPACPROs.