UniFi – How to Manually Change the Cloud Key’s Controller Version via SSH


Readers will learn how to change the controller version on the UniFi Cloud Key. This article will discuss how to download and install a controller version. We are showing the process for the latest stable at the time of writing this, but the same steps are used for any release.

Only stable releases are found on our downloads site, alpha and beta releases are in their respective release blog.


  • It is always best to make a backup prior to changing the controller release.
  • If you are changing release channels you may lose some statistics. Typically this would only happen when downgrading between major release branches (i.e. 4.6, 4.7, 4.8, 4.9). So, if you upgraded to 4.9, then decided you wanted to change back to 4.8 you would lose some stats.  


1. First you need to get the download link for the firmware. This can be found by going to our main downloads page, HERE and clicking on the Linux download, and then clicking the Download button.

You could also grab the link from the release post in the appropriate blog section of the community. Only stable releases will be on our main downloads page, whereas alpha and beta releases are in their respective release blog.

2. Once you have the link to the .deb file you need to connect to your Cloud Key via SSH. If you aren’t sure of the IP and are on the same L2 subnet then you could use the UniFi discovery tool to find it.

3. After you are connected to the Cloud Key it is recommended that you change to the /tmp directory, by issuing: cd /tmp

The console would show something like: root@UniFi-CloudKey:/tmp#

4. From here you want to use wget to grab the file. So to grab the .deb referenced above you would issue: wget http://dl.ubnt.com/unifi/4.8.12/unifi_sysvinit_all.deb

5. After you’ve downloaded the file you want to issue: dpkg -i unifi_sysvinit_all.deb

6. Once it has successfully installed, and you are back at /tmp#, you want to issue: rm unifi_sysvinit_all.deb

That will remove the deb from the /tmp folder.

7. You can ‘exit’ from the SSH session now that the controller upgrade is complete.

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *