This article describes additional features of UNMS installation process. It includes changing ports for accessing through GUI, setting ports for communication with devices, working behind a proxy and more.
Table of Contents
- Installing Prerequisites
- Managing the SSL certificate for access via HTTPS
- Changing the HTTP and HTTPS ports
- Changing the device inform port
- Running UNMS behind a reverse proxy
- Changing the UNMS container's IP address
- UNMS Data
- Devices Latency and Outage Statistics
Run the following commands on your Ubuntu or Debian system to ensure that all required tools are installed:
sudo apt-get update sudo apt-get install curl sudo bash netcat
Managing the SSL certificate for access via HTTPS
If you want UNMS to use default LetsEncrypt certificate please do not use any of these attributes.
By default, UNMS uses Let's Encrypt to automatically create and manage an SSL certificate for its domain name. The certificate is saved under
If you need to use your own certificate you can use these installation script arguments to do it:
--ssl-cert-dir <DIRECTORY> : This is a path to a directory where your certificate is located
--ssl-cert <FILENAME> : This is a filename of your certificate
--ssl-cert-key <FILENAME> : This is a filename of the certificate key
some older certificates have a separate certification authority key. You can use this optional attribute to set it:
--ssl-cert-ca <FILENAME> : This is a filename of a certification authority's key
Make sure that the UNMS has read permission on the certificate directory and all files. Remember that you can have each file in a custom folder as long as those folders are subfolders of
curl -fsSL https://unms.com/install > /tmp/unms_inst.sh && sudo bash /tmp/unms_inst.sh --http-port 8080 --https-port 8443 --ssl-cert-dir /etc/certificates --ssl-cert fullchain.pem --ssl-cert-key privkey.pem
Changing the HTTP and HTTPS ports
Please be aware that UNMS must be accessible from the internet via HTTP port 80 if you want to use automatic SSL certificate management via Let's Encrypt.
Use installation script arguments
to configure the UNMS server to listen on non-standard ports. Defaults are 80 (HTTP) and 443 (HTTPS).
curl -fsSL https://unms.com/install > /tmp/unms_inst.sh && sudo bash /tmp/unms_inst.sh --http-port 8080 --https-port 8443
Changing the device inform port
Please be aware that UNMS must be accessible from the internet via HTTP port 80 if you want to use automatic SSL certificate management via Let's Encrypt. Using a separate inform port is useful when you need to expose the port outside your private network, but don't want to expose the UNMS GUI. Use installation script argument
to configure the UNMS WebSocket server to use a separate port for communication with your devices.
curl -fsSL https://unms.com/install > /tmp/unms_inst.sh && sudo bash /tmp/unms_inst.sh --ws-port 8444
Running UNMS behind a reverse proxy
Use installation script arguments
if you plan to run UNMS behind a reverse proxy server. The setting
is only necessary if the proxy listens for HTTPS on a different port than UNMS. The setting
is only necessary when you use
(as mentioned in the section above) to separate the inform port form the HTTPS port.
curl -fsSL https://unms.com/install > /tmp/unms_inst.sh && sudo bash /tmp/unms_inst.sh --public-https-port 443 --http-port 8080 --https-port 8443
Please be aware that this puts the responsibility of managing an SSL certificate on the reverse proxy and disables the automatic certificate management via Let's Encrypt. The reverse proxy must still use HTTPS for communication with UNMS, optionally with a custom SSL certificate. HTTP-only communication between UNMS and the reverse proxy is not supported. The UNMS - Reverse Proxy Examples article shows working reverse proxy configurations for Nginx and Apache.
Changing the UNMS container's IP address
If you are using private address range 172.x.x.x. in your network you may prefer to change the default address of UNMS docker containers in order to avoid any possible collision.
Use installation script argument
to change the UNMS container's subnet if you experience IP address conflicts.
curl -fsSL https://unms.com/install > /tmp/unms_inst.sh && sudo bash /tmp/unms_inst.sh --subnet 184.108.40.206/24
You may also wish to change the IP address of the docker0 bridge created by Docker. See the docker user guide for more information. Please note that this may affect containers other than UNMS running on your system.
For a detailed tutorial on DigitalOcean see: UNMS - How to Deploy on DigitalOcean.
We recommend using the latest version of Ubuntu 16.04.1 LTS (Xenial Xerus) or Amazon AMI. Here are examples of suitable cloud services:
- AWS, EC2 instance, t2.small (2 GB RAM), Ubuntu 16.04.1 LTS (Xenial Xerus)
- DigitalOcean, basic droplet (2 GB RAM), Ubuntu 16.04.1 LTS (Xenial Xerus)
By default, the installation script ensures that the application settings and data (logs, site images, encryption key, etc.) are stored outside of the docker container (
). This will enable you to back up that data, and more importantly, this will enable you to perform any future UNMS upgrades without any data loss.
Devices Latency and Outage Statistics
By default, all connected devices to UNMS will ping the UNMS host to check for latency and if any devices are being reported as offline which will result in outage statistics being generated. Ping must be allowed to the UNMS Host for this to work properly.