Arch Linux User Repository

We are on Stable with this Package. Please flag out-of-date only if the Version provided with this package does not match the version under "Stable" in this link: https://help.ubnt.com/hc/en-us/articles/360008240754#1

@wantinstallation The proper way to deal with multiple Java versions is using archlinux-java. Run archlinux-java set java-8-openjdk and it should work after that.

I switched from the new web UI to the old since I did not see any unifi devices in the new web UI. After having lot's of 500 and 400 errors when clicking "Settings" in the menu bar on the left I manually changed the unifi.service to this: ExecStart=/usr/lib/jvm/java-8-openjdk/bin/java -jar /usr/lib/unifi/lib/ace.jar start ExecStop=/usr/lib/jvm/java-8-openjdk/bin/java -jar /usr/lib/unifi/lib/ace.jar stop

I found the hint here: https://help.ui.com/hc/en-us/articles/204949764-UniFi-Network-Application-Fails-to-Start-When-Opened

Hope it helps other

There is something deeply broken with this package. Cannot access the interface via the unit file or manuall running the commands with root. Accessing from remote machine without https cites requirements for TLS but then cannot access remotely with TLS. @torben, where are you making those system changes?

I am not sure, if this really is related, because in my case I couldn't open the web interface anymore at all. I first suspected that this was due to the latest update of Unifi, but actually it was pure coincidence:

Reason here was a deprecated TLS Version as single active source on the server. Current browsers do no longer support older TLS Versions, so I had to update my system.properties to something like this:

unifi.https.ciphers=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

unifi.https.sslEnabledProtocols=TLSv1.2

Especially the last line which switches to TLS 1.2 as protocol fixed things for me. I'm not sure if it would be sane to allow 1.1/1.0 as well. For now I don't see any problems with Unifi Devices to connect or to be managed when using 1.2.

@freswa I'm not sure, if this is a general problem or related to the fact, that my installation is several years old. If new installs still use old TLS, you might want to bundle a new system.proerties.

This package does not work properly for me (anymore). When I start the service through systemctl, the localhost:8443 is not accessible. I tried to instead run the command manually as root, and then the service is accessible. This got me wondering if the unifi user has all necessary rights, to e.g. set up a web service? I tried to look at folder rights, but afaik that all looks fine. I further do not find any error messages anywhere.

Max-P,a few notes on your backup and restore instructions.

You need mongodb-tools. You have /usr/lib a few times when you mean /var/lib.

For those that have issues starting Unifi after updating MongoDB: you may need to rebuild/repair the database for it to work again. Something with the WiredTiger database backend versions. I'm currently running on mongodb-bin-4.4.1-1 with no problems and Unifi controller is working perfectly.

sudo -u unifi -g unifi mongod --repair --dbpath /var/lib/unifi/data/db

Alternatively, you can do a backup and restore on a fresh DB:

1. Restore an older version of MongoDB that was previously working
2. Start mongod manually: sudo -u unifi -g unifi /usr/bin/mongod --dbpath /usr/lib/unifi/data/db --port 27117 --unixSocketPrefix /usr/lib/unifi/run --bind_ip 127.0.0.1
3. Dump the database: mongodump --port 27117 -o backup-unifi-controller
4. Stop mongod (Ctrl+C in the terminal running it)
5. Upgrade mongodb
6. Make a backup of /usr/lib/unifi/data/db and delete its contents (make sure the folder exists and has the correct permissions)
7. Start mongod again
8. Restore the backup: mongorestore --port 27117 backup-unifi-controller
9. Stop mongod and start unifi normally

service start

● unifi.service - Ubiquiti UniFi Server
     Loaded: loaded (/usr/lib/systemd/system/unifi.service; enabled; vendor preset: disabled)
     Active: active (running) since Thu 2020-11-19 17:40:21 PKT; 2s ago
   Main PID: 312152 (java)
      Tasks: 15 (limit: 18502)
     Memory: 129.3M
     CGroup: /system.slice/unifi.service
             └─312152 /usr/bin/java -jar /usr/lib/unifi/lib/ace.jar start

Nov 19 17:40:21 T460 systemd[1]: Started Ubiquiti UniFi Server.
Nov 19 17:40:21 T460 java[312152]: 2020-11-19 17:40:21,925 main ERROR Error processing element InMemoryAppender ([Appenders: null]): CLASS_NOT_FOUND
Nov 19 17:40:22 T460 java[312152]: 2020-11-19 17:40:22,258 main ERROR Unable to locate appender "InMemoryAppender" for logger config "root"
➜  ~ 

but stops after 5 seconds.

unifi.service - Ubiquiti UniFi Server
     Loaded: loaded (/usr/lib/systemd/system/unifi.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Thu 2020-11-19 17:35:27 PKT; 12ms ago
    Process: 308425 ExecStart=/usr/bin/java -jar /usr/lib/unifi/lib/ace.jar start (code=exited, status=255/EXCEPTION)
   Main PID: 308425 (code=exited, status=255/EXCEPTION)

Nov 19 17:35:17 T460 systemd[1]: Started Ubiquiti UniFi Server.
Nov 19 17:35:17 T460 java[308425]: 2020-11-19 17:35:17,855 main ERROR Error processing element InMemoryAppender ([Appenders: null]): CLASS_NOT_FOUND
Nov 19 17:35:18 T460 java[308425]: 2020-11-19 17:35:18,188 main ERROR Unable to locate appender "InMemoryAppender" for logger config "root"
Nov 19 17:35:27 T460 java[308425]: Port 8080 not available
Nov 19 17:35:27 T460 systemd[1]: unifi.service: Main process exited, code=exited, status=255/EXCEPTION
Nov 19 17:35:27 T460 systemd[1]: unifi.service: Failed with result 'exit-code'.
~

eagebhart, if you actually read the output you posted, you'd see that it has nothing to do with this package.

This is not building for me. I've done an pacman -Syu, and updated my keys. pacman-key --refresh errors with a General error, could not be retrieved on the same key.

Here is the snippet of the error. I have not tried working around it yet.

:: (1/3) Parsing SRCINFO: libcurl-openssl-1.0 :: (2/3) Parsing SRCINFO: mongodb-bin :: (3/3) Parsing SRCINFO: unifi-beta

:: PGP keys need importing: -> 27EDEAF22F3ABCEB50DB9A125CC908FDB71E12C2, required by: libcurl-openssl-1.0 ==> Import? [Y/n] :: Importing keys with gpg... gpg: keyserver receive failed: General error problem importing keys

Or this:

sudo pacman-key --refresh-keys ──#(Wed,Nov18)─┘ gpg: refreshing 121 keys from hkps://hkps.pool.sks-keyservers.net gpg: keyserver refresh failed: General error ==> ERROR: A specified local key could not be updated from a keyserver.