ubiquiti device discovery tool does not find cloud key

UBIQUITI DEVICE DISCOVERY TOOL DOES NOT FIND CLOUD KEY HOW TO
UBIQUITI DEVICE DISCOVERY TOOL DOES NOT FIND CLOUD KEY MAC OS
UBIQUITI DEVICE DISCOVERY TOOL DOES NOT FIND CLOUD KEY INSTALL
UBIQUITI DEVICE DISCOVERY TOOL DOES NOT FIND CLOUD KEY ARCHIVE
UBIQUITI DEVICE DISCOVERY TOOL DOES NOT FIND CLOUD KEY SOFTWARE

UBIQUITI DEVICE DISCOVERY TOOL DOES NOT FIND CLOUD KEY HOW TO

Let’s dig in and discover how to do that. While you can use a Windows Server for the Unifi controller, Ubiquiti also offers an option to run the controller on Linux. You should not receive an error and see that the service is running. Now that you have configured the service, validate that it is running using the command sc query unifi.

UBIQUITI DEVICE DISCOVERY TOOL DOES NOT FIND CLOUD KEY SOFTWARE

The Unifi Controller software will launch and after a minute or so it will show that it is started.Ĭhanges to the default Unifi Controller directoryĬonfigures Java to run the controller as a service and to start on boot Accept all of the defaults and finish the install. Once you’ve installed Coretto, now run the Unifi Controller software you should already have downloaded.

UBIQUITI DEVICE DISCOVERY TOOL DOES NOT FIND CLOUD KEY INSTALL

Since Oracle changed their licensing requirements for Java in a non-home use many organizations will opt to use OpenJDK instead of Oracle’s Java SE.Īssuming you’ve already downloaded Corretto, run the MSI to install OpenJDK and follow the prompts ensuring you leave everything as default to finish the installation of OpenJDK.

If you need to remove Java for some reason, check out this article.Īmazon Corretto is a pre-packaged OpenJDK installer. In this article, you’re going to install Amazon Corretto rather than the typical Java download from Oracle. To run the Ubiquiti discovery tool, you must first install the controller software, you’ll first need to install Java if you don’t have it already. Amazon Corretto 8 – Java 8 is also acceptable assuming you meet the licensing requirements or other OpenJDK package.Unifi Controller Software for Windows – This article will use version 5.13.29.Windows Server 2019 – All of these steps will also work on most other Windows versions.Prerequisitesīefore you start, be sure you have the following prerequisites: To fix this, you will learn how to set it up to run as a service thus removing the logged-in requirement. By default, a user has to be logged in for the controller to run. The installer will install a basic web server that you can log in and start managing devices.īy default, the webserver that the controller software installs will run as an application. To use get it the controller set up is as easy as installing the software and launching it. Using Windows Server or even a Windows desktop is a common host for a Unifi Controller. Installing the Unifi Controller on Windows Server

UBIQUITI DEVICE DISCOVERY TOOL DOES NOT FIND CLOUD KEY MAC OS

Since the controller supports Windows, Mac OS X, and some distros of Linux, we’re going to cover two different options for installing the controller installing on Windows and Linux. This controller connects to and manages all of the devices on your network. To manage Ubiquiti networking devices, you must set up the Ubiquiti discovery tool and controller.

Updating Unifi Controller on Windows Server.Configuring the Ubiquiti Discovery Tool and Controller.Installing the Ubiquiti Discovery Tool and Controller.Installing the Unifi Controller on Windows Server.

UBIQUITI DEVICE DISCOVERY TOOL DOES NOT FIND CLOUD KEY ARCHIVE

This will create a P12 bunded certificate archive with a temporary password we use later. Under Windows 10, I use the Windows Subsystem for Linux (WSL) and Ubuntu. To create a P12 bunded certificate archive, I use OpenSSL. We need to create a P12 bunded certificate archive and transfer this to the Cloud Key. My SSL certificate files are in a different format for what we need. I used the same wildcard SSL certificate I hold for my public domain name. The SSL certificate needs to have the same domain name associated as in the custom hostname field. We can now access the Cloud Key with a custom hostname, but we also need to add a custom SSL certificate to the controller. This new hostname gives me a friendly URL, but the SSL warning is still there. I created a sub-domain ‘unifi’ at my DNS provider (I use Azure DNS for all my domains) and pointed an A-record to the UniFi Cloud Key IP address. In the Cloud Key Controller, we can use a custom hostname (under Controller settings -> Advanced Configuration). Also, the web browser will not remember your login credentials for the next login.

The connection is using https (that’s good), but there is no domain name, so the default SSL certificate triggers a security warning in your web browser because it can’t be verified. If you do not know your Cloud Key IP-address, use the Ubiquiti Device Discovery Tool. In my situation, the IP-address is 192.168.1.64 When connecting to the UniFi Cloud Key Controller, you need to know the IP-address and port number (default 8443).

Ubiquiti device discovery tool does not find cloud key