YeOldeStonecat
Well-Known Member
- Reaction score
- 6,556
- Location
- Englewood Florida
If you run the controller locally...it should discover it through a scan.
If you have the controller on a IP that the device can contact...be it internal or external, what I do is use the discovery tool to find the local LAN IP of the new device I plugged in.
I then fire up Putty, and log into that IP (default user/pass is ubnt/ubnt), and then run the set-inform command.
By default, devices come with an inform set to http://unifi:8080/inform
So you want to set to the FQDN you made your cloud controller, such as:
set-inform http://unifi.catspad.org:8080/inform
Of, if you're doing a multi-site WAN or LAN with multiple internal networks, as long as each network device can contact the internal IP you give the controller, just set it via IP like:
set-inform http://192.168.1.250:8080/inform
Now with the set-inform command, I like to run it twice. First I log into the device with Putty, and run the command. I then look at my controller and within a few seconds the newly informed device will appear in the controller as available to be adopted. So click in the Adopt button in your controller, wait about 10 seconds..and then in your Putty console, hit the up arrow to repeat your set-inform line...hit enter to run it, and then you'll see it finish adopting and go into provisioning in your controller.
I'm not clear on what you're saying about your unifi.ubnt.com account. The cloud key should be registered at that portal, named, so it shows up in the list of all your client site Unifi controllers. When you log into unifi.ubnt.com you should see your cloud key listed there and then click to launch a browser to connect to it. Same thing as if you logged onto the Cloud Key locally at 192.168.1.250. The Unifi.ubnt.com portal just...proxies you to the local on prem controller via a secure tunnel. When I'm onsite at a client I often just log into the cloud key locally...faster response time.
If you have the controller on a IP that the device can contact...be it internal or external, what I do is use the discovery tool to find the local LAN IP of the new device I plugged in.
I then fire up Putty, and log into that IP (default user/pass is ubnt/ubnt), and then run the set-inform command.
By default, devices come with an inform set to http://unifi:8080/inform
So you want to set to the FQDN you made your cloud controller, such as:
set-inform http://unifi.catspad.org:8080/inform
Of, if you're doing a multi-site WAN or LAN with multiple internal networks, as long as each network device can contact the internal IP you give the controller, just set it via IP like:
set-inform http://192.168.1.250:8080/inform
Now with the set-inform command, I like to run it twice. First I log into the device with Putty, and run the command. I then look at my controller and within a few seconds the newly informed device will appear in the controller as available to be adopted. So click in the Adopt button in your controller, wait about 10 seconds..and then in your Putty console, hit the up arrow to repeat your set-inform line...hit enter to run it, and then you'll see it finish adopting and go into provisioning in your controller.
I'm not clear on what you're saying about your unifi.ubnt.com account. The cloud key should be registered at that portal, named, so it shows up in the list of all your client site Unifi controllers. When you log into unifi.ubnt.com you should see your cloud key listed there and then click to launch a browser to connect to it. Same thing as if you logged onto the Cloud Key locally at 192.168.1.250. The Unifi.ubnt.com portal just...proxies you to the local on prem controller via a secure tunnel. When I'm onsite at a client I often just log into the cloud key locally...faster response time.
