UNMS - Installation Guide


This article describes how to install a fresh copy of UNMS or update an existing installation on a (self-hosted) server. This is a guide for a Linux installation, see the following note for Windows and macOS operating systems:

  • See thesection below for the UNMS installation prerequisites.
  • Unfortunately proper operation, smooth backups and upgrades of critical Docker containers cannot be ensured on Windows and macOS systems.
  • At this time we recommend that you install a virtualization program such as VirtualBox to run the latest version of Ubuntu 18.04.3 (Bionic Beaver) 64-bit and then follow the Linux instructions provided below.

Table of Contents

  1. Prerequisites
  2. Installation Instructions
  3. Updating an Existing Installation
  4. Related Articles


Back to Top

ATTENTION: It is recommended to install UNMS on a server that is equipped with a public IP address and FQDN, which is directly connected to the main gateway of the network. In this setup, UNMS will automatically use a valid trusted certificate through Let's Encrypt, will report outages in the most precise manner, and all of its advanced functions will perform optimally.

It is certainly possible to place UNMS server in a different spot in a topology, but there may be some limitations involved.

Installation Instructions

Back to Top

Run the command below on the host to install and start UNMS (it will automatically install Docker if it is not installed already). If a UNMS installation already exists, it will be overwritten, but all data will be kept. It is possible to use the --update attribute if the new installation needs to have the same parameters as the old one. 

The command below will always install the newest, stable version that is listed in the Software Releases section on the Ubiquiti Community. To view, select the Stable status, followed by the UNMS tag in the General section.

curl -fsSL https://unms.com/v1/install > /tmp/unms_inst.sh && sudo bash /tmp/unms_inst.sh

During the installation process, the script will check if TCP port 80 and TCP port 443 are open/available. If the ports are in use, the script will pause and ask which ports should be used by UNMS. The same applies to the overcommit memory settings. If the vm.overcommit_memory is not set to '1', the installation script asks for permission to enable it. In case those interrupts are unwanted in the installation process it is possible to suppress them with --unattended attribute which lets the installation script do all the necessary arrangements by itself.

When the process is complete, UNMS will be accessible at the https://<ip or hostname> address. Please do not use localhost to connect to UNMS.

NOTE: The installation script needs to use sudo permissions to install Docker in case it is not available in the OS already. The permissions are also needed to create the UNMS user, under which the UNMS application runs as well as to set up a cron task that manages the UNMS updates.

Registering new devices to UNMS can be done by following the steps in:

If it is necessary to customize the installation process, follow the steps in:

If you wish to install a UNMS version that is not the current, stable version see:

Updating an Existing Installation

Back to Top

Once installed, UNMS will periodically check for new updates and prompts for installation. Verify whether UNMS is up to date and the version that is installed in the  settings.png  Settings > Maintenance section. It is also possible to manually check for updates in this section.

We recommend using the Web UI update method over manually updating through the CLI. It is highly suggested to create a full backup of UNMS before using the CLI method.

Related Articles

Back to Top

UNMS - The UNMS Key and the Device Registration Process

UNMS - Optional Installation Steps

UNMS - Ping, Latency and Outages Guide

UNMS - Beta Version Install Guide

Was this article helpful?
1189 out of 1646 found this helpful
Can't find what you're looking for?
Visit our worldwide community of Ubiquiti experts for more answers
Visit the Ubiquiti Community