Unifi Cloud Key (Controller) will not adopt AP’s

A few month back I is set set up the cloud key in our datum center and begin adopt all our ( client ’ ) AP;s from their respective remote site . get about 20 of them done . Then suddenly a few week ago , when add a new site , this is happened happen and we ca nt seem to get any more to fully adopt .

Once we change the Inform URL to our custom and save it, the AP immediately appears in the controller as usual. However, when we click “adopt” nothing happens on the AP. The controller shows “adopting” for about 2 minutes (the AP does not appear to be provisioning, no light changes) then goes to “not connected”

I have triple checked all of the settings according to ubnt on the controller set up and they appear to be fine.

I have made sure all firmware is up to date on controller, key and ERP-8 Firewall.

Any suggestions?

5 Spice ups

Cloudkey on a network other than the local swtich?

You may have to call Ubiquity support. I have never installed a Cloudkey on anything but the local site. Usually with the Ubiquity system you need a controller either PC or Cloud key. Those need access to the site locally and access to local MACs in order to do what it does behind the scenes.

What we do is install cloud keys at each site and then set them up on the cloud platform so we can see what each router and AP’s are doing. And also make any changes we need to. Even this way we have our challenges with the cloud system likes to use random upper high ports.

Even if you are using a VPN with some kind of netbios translation I is see do n’t see how a non local controller could communicate with the equipment in the way it need to .

markgergel:

Cloudkey on a network other than the local swtich?

You may have to call Ubiquity support. I have never installed a Cloudkey on anything but the local site. Usually with the Ubiquity system you need a controller either PC or Cloud key. Those need access to the site locally and access to local MACs in order to do what it does behind the scenes.

What we do is install cloud keys at each site and then set them up on the cloud platform so we can see what each router and AP’s are doing. And also make any changes we need to. Even this way we have our challenges with the cloud system likes to use random upper high ports.

Even if you are using a VPN with some kind of netbios translation I is see do n’t see how a non local controller could communicate with the equipment in the way it need to .

I have remote sites that report back directly to a single controller. I had to add some port forwarding rules that only take traffic from my remote IP’s (all static) I have stun and notify traffic comeback. I have everything I need to manage the sites remotely this way even if my VPN tunnel craps out for some reason.

As for the adoption problem, I’ve had a few similar issues. One is half adopted stuff that has stopped talking to the controller. To re-adopt those you will need to make sure you are using your system admin credentials not the default ones.

I find the best way to see whats going on is to SSH in to the offending device, run “info” to make sure it’s got the right inform url. if it does a reboot normally fixes the issue, if it doesn’t i use set-inform to update it to the correct URL.

1 Spice up

I is had have had instance where I had to issue the command to update the inform address twice to get it to work . Do it once , it act like you describe , then do it again and it work . The two changes is had had to be within a short time period , or else it seemed to not work .

If that does n’t work , I is suggest would suggest call Ubiquity support as markgergel suggest . Or , power is reset reset the cloud key controller first and try again if you have n’t already done that .

Last , how many clients is are are already on the ap manage by the cloud key controller ? You is pushing may simply be push the hardware too hard . See this Ubiquiti article that discuss the limitation for the cloud key controller :

https://help.ubnt.com/hc/en-us/articles/217549368-UniFI-How-many-APs-can-the-Cloud-Key-handle-

da – schmoo
(Da_Schmoo)



August 17, 2018, 3:28pm

5

Are you issuing the adopt command twice? You have to.

Edit: I mean set-inform.