{"id":4932,"date":"2016-05-10T18:30:59","date_gmt":"2016-05-10T22:30:59","guid":{"rendered":"http:\/\/chriscolotti.us\/?p=4932"},"modified":"2016-05-11T07:19:27","modified_gmt":"2016-05-11T11:19:27","slug":"first-look-hands-ubiquiti-unifi-cloud-key","status":"publish","type":"post","link":"https:\/\/chriscolotti.us\/technology\/first-look-hands-ubiquiti-unifi-cloud-key\/","title":{"rendered":"First Look and Hands On With Ubiquiti Unifi Cloud Key"},"content":{"rendered":"
<\/a><\/p>\n I have been running a cloud based version of the Ubiquiti Unifi Controller for just about a year now. \u00a0I decided to run it this way because I happen to manage my home office gear as well as a small setup for my church and a local RV park. \u00a0The cloud based controller version was a perfect solution do have all the sites under one roof. \u00a0However, it does cost money to host it every month, and there is some management of the virtual server, but all in all it’s been flawless. \u00a0It also gives every device the same place to call home and has always stayed online. \u00a0Last week I also blogged about how the Unifi iOS app<\/a> can connect to that controller and I also have access to all those sites on a mobile device. \u00a0What some people don’t know yet is Ubiquiti also fired up a cloud aggregation portal that they host and you can register multiple controllers with. \u00a0That got me thinking, should I break the sites out into individual controllers using the new Unifi Cloud Key? \u00a0Well first I needed to see what this little device was all about.<\/p>\n <\/p>\n Right off the bat when you plug this it and power it up with PoE, it will try to use DHCP to get online. \u00a0Once you know the IP address and connect to it one thing jumps right out. \u00a0There is TWO management interfaces on the single IP address. \u00a0The first is to the Unifi Controller installation, the other is to manage the Unifi Cloud Key firmware itself.<\/p>\n <\/a><\/p>\n What you will find is that both interfaces are on HTTPS and they are separated in the following manner:<\/p>\n This means that most likely you cannot change the controller’s startup to use port 443 like many people do with a cloud based controller since 443 is already in use for the Key management. \u00a0That’s okay for the most part if you ask me. \u00a0My public cloud controller I did switch to 443 on the port to make it easier to remember. \u00a0The point here on the architecture is that it’s two web services on the same device using different ports. \u00a0It also appears that non SSL is forced to SSL for the login pages.<\/p>\n There is a microSD that comes with it that the manual says is used for backup, but so far I have not found any way to utilize it. \u00a0The forums indicate it’s for future use while the setup doc says “To back up the Unifi Controller database and configuration, use the included microSD Card<\/p>\n This is pretty straight forward and only a few things to look at. \u00a0Once you click “Configure” under Configure Your Cloud Key on the start page you will get the key login.<\/p>\n <\/a><\/p>\n Once logged in the first thing it’s smart enough to make you do is change the default password.<\/p>\n <\/a><\/p>\n Once you get connected you are presented with a dashboard and a few links. \u00a0You can see there is on;y 1.45 GB available showing…so again not sure where the MicroSD is accounted for and how you access it for backups.<\/p>\n <\/a><\/p>\n Under Configuration you can set the device name, time zone, \u00a0and IP address of the device itself. \u00a0It’s by default set to DHCP and also has a fallback IP address if no DHCP can be reached.<\/p>\nUnifi Cloud Key Architecture<\/h3>\n
\n
Configuring the Unifi Cloud Key<\/h3>\n