UniFi — How to Install and Update via APT on Debian or Ubuntu
This article provides the steps to update the UniFi Network Controller on a Debian or Ubuntu system via APT (Advanced Package Tool). If you run into issues following the process described in this article, please take a look at the scripts provided in this Community post that includes UniFi Network Controller software installation on Ubuntu 18.04 and 16.04 and Debian 8/9.
Table of Contents
Introduction
In order to update the UniFi Network Controller via APT, it is necessary to create source files or edit lines in an existing sources.list file with Linux text editors: vi or nano. That is the most common method for package updates and installs for these operating systems. The repo structure should be permanent, but if there are any changes they will be pointed out in the UniFi Network Controller software version release posts, found in the Community.
Follow the instructions below to stay with the current stable release, regardless of changes in versions. When there is a new stable release, there will be a post on the Community announcing it.
UniFi Network Controller APT Steps
1. Install required packages before you begin with the following command:
2. Use the following command to add a new source list:
3. Add the GPG Keys. To add the GPG Keys use one of the two methods described below (Method A is recommended). When using the commands below, it is assumed you have sudo and wget installed, more information about sudo can be found here, and wget here.
(Method A) Install the following trusted key into /etc/apt/trusted.gpg.d
(Method B) Using apt-key.
4. Install and upgrade the UniFi Network Controller.
This should restrict Ubuntu from automatically installing Java 11. If you wish to undo this later, replace «hold» with «unhold».
5. This step may not be required, depending on the Linux distro you have. If your distro does not come with MongoDB, and it’s not available in their repo, then please see the MongoDB installation guide. You can find the latest installation guide for Ubuntu here, and Debian here. We recommend at least MongoDB 2.6.10. Some users have changed the backend to use MongoDB 3 successfully too.
6. The UniFi Network Controller should now be accessible at the computer’s configured local or public IP address, by typing that IP address in a browser’s navigation bar (Chrome is recommended). If it is not launching, use the following command: sudo service unifi start .
Other helpful commands are:
To stop the UniFi service: sudo service unifi stop
To restart the UniFi service: sudo service unifi restart
To see the status of UniFi service: sudo service unifi status
We strongly recommend staying with the stable release, but for those users who wish to do otherwise, click here to expand and see possible suite names, as well as code names in the table within.
«Testing» refers to the next generation release, it’s not released to the general public yet. «Stable» refers to the current stable release, that is the one supported by Ubiquiti and described in this article. «Old Stable» is the previous stable release, once it has been displaced by the new, current stable release.
Suite Name
Code Name
Archived Code Names
oldstable
unifi-5.10
The code names below have been archived and are no longer supported, these should only be used in very specific, rare scenarios.
Log files will be essential for any troubleshooting you might perform. Find them here:
User Notes & Tips
These notes have been added thanks to user collaboration.
This Community post shares some scripts for UniFi Controller software installation on Ubuntu 18.04 and 16.04 and Debian 8/9.
If you are installing in a VM or a headless server, you may encounter entropy issues. This could be anything from slow service start/restart to complete service failure. The fix is to install haveged . This is an external link for a tutorial on the subject.
Since UniFi Controller version 5.6.x the UniFi service does not run as root. This means that you cannot bind to privileged ports ( apt-get update will result in an error.
To fix this run the command the following way: apt-get update —allow-releaseinfo-change
If you receive an error stating the command is not understood in combination with the other options, users have reported that issuing the following two commands has fixed it: issue apt clean and hit enter, followed by apt-get update and enter.
The UniFi Controller, when installed on Debian and Ubuntu, will not have a GUI since it’s being run as a Service. Please use the service command for starting, stopping and restarting the UniFi Controller.
If you see the following error on your DNS server, a user reports solving this by forcing the system to use 8.8.8.8 as DNS server, not his ISP.
At the moment Ubiquiti does not support arm64, hence it is not available via the repo. A download and manual installation will be necessary for this.
In the Add the GPG Keys, method B:Source: External Link. For users behind restrictive firewalls the following command will allow them to import the GPG key:
Deon1sk4 › Блог › Установка и настройка Unifi controller + DHCP+ VLAN+ MongoDB на основе Ubuntu Server 14.04 LTS
Тематика не для этого сайта. Пост для себя, дабы не забыть. Поставили задачу для реализации бесшовной wifi сети. К хотелкам добавили, что бы была гостевая изолированная сеть и основная корпоративная. Выбрали точки доступа ubiquiti unifi. Что имеется к условиям задачи. Нужно поднять сервак на базе ubuntu 14.04, на основной сетевой интерфейс навесить vlan, поднять DHCP сервер, поднять базу mongoDB ну и поднять сам веб сервер для администрирования точек доступа. Стартуем)))
• Допустим, нам нужно подключить сеть VLAN200. Для этого создадим логический интерфейс «eth0.200», привязанный к физическому интерфейсу «eth0», который будет обрабатывать пакеты с тегом 200. vconfig add eth0 200 • Если выскочит ошибка «…Maybe you need to load the 8021q module…», надо будет подгрузить модуль 8021q в ядро Linux следующей командой: sudo modprobe 8021q • Повесим ip-адрес на новый интерфейс «eth0.200». sudo ifconfig eth0.200 10.10.X.X netmask 255.255.0.0 up посмотреть список интерфейсов: Ifconfig -a • Что бы настройки vlan не пропадали после перезагрузки сервера его нужно добавить в файл interfaces (конфиг) sudo nano /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback #wan auto eth0 iface eth0 inet static address 192.168.X.X netmask 255.255.0.0 gateway 192.168.X.X broadcast 192.168.255.255 dns-nameservers 192.168.X.X
#vlan 200 auto eth0.200 iface eth0.200 inet static address 10.10.X.X netmask 255.255.255.0 broadcast 10.10.X.255 vlan_raw_device eth0 Сохраняемся и выходим. • После нужно перезагрузить интерфейс командой sudo service network interfaces restart
3. Устанавливаем dhcp server • Вводим в командной строке терминала команду: sudo apt-get install isc-dhcp-server • Настройка конфигурационного файла DHCP сервера sudo nano /etc/dhcp/dhcpd.conf subnet 10.10.X.X netmask 255.255.255.0 < range 10.10.X.10 10.10.X.200; #option domain-name «MYDOMAIN»; option domain-name-servers 8.8.8.8; option routers 10.10.X.X; option broadcast-address 10.10.X.255; default-lease-time 604800; max-lease-time 604800; > Сохраняемся и выходим • Перезагружаем службу DHCP sudo service isc-dhcp-server restart • Смотрим что бы статус был job/running. Если по какой-то причине не не стартует смотрим лог /var/log/syslog 4. Далее настраиваем Настройка IPTABLES и NAT • Для начала нам нужно создать файл /etc/firewall.sh Нужно сделать его исполняемым sudo nano /etc/firewall.sh • Даем права на исполнение sudo chmod +x /etc/firewall.sh • Далее в скрипт вносим следующие параметры #!/bin/sh
sysctl -w net.ipv4.ip_forward=»1″
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
This step may not be required, depending on the Linux distro you have. If your distro does not come with MongoDB, and it’s not available in their repo, then please see the MongoDB installation guide. You can find the latest installation guide for Ubuntu here, and Debian here. We recommend at least MongoDB 2.6.10. Some users have changed the backend to use MongoDB 3 successfully too.
We strongly recommend staying with the stable release, but for those users who wish to do otherwise, click here to expand and see possible suite names, as well as code names in the table within.
