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

Since this package uses JDK 11, we can explicitly use JDK 11 like this:

[Unit]
Description=Ubiquiti UniFi Server
After=network.target

[Service]
User=unifi
WorkingDirectory=/usr/lib/unifi
ExecStart=/usr/lib/jvm/java-11-openjdk/bin/java -jar /usr/lib/unifi/lib/ace.jar start
ExecStop=/usr/lib/jvm/java-11-openjdk/bin/java -jar /usr/lib/unifi/lib/ace.jar stop

[Install]
WantedBy=multi-user.target

Might be worth mentioning that the changelog for this release (7.3.76) bumped the Java requirement to 11, so if you had previously set your JRE default down to 8 to make it work you'll need to bump it back up to 11 now.

Think this needs a version constraint for mongo now - upgrade failed miserably on me last night since mongo is now at v6 and Arch moved to OpenSSL3 which seems to add the requirement for openssl-1.1 to be in the FS as well.

I just wanted to chime in and confirm previous notes;

1. Edit the pkgbuild and changing depends in this way; (thank you CommanderCrisp)
   mongodb => mongodb36
   java-runtime-headless=8 => jre8
2. Make sure the correct Java runtime is selected; (thank you bobpaul)
   https://wiki.archlinux.org/title/Java#Switching_between_JVM

With all of that out of the way it all seems to work. I was editing the PKGBUILD and still having runtime issues and 404 problems, but switching the Java runtime seemed to solve those.

Like any piece of software not packaged in a distribution agnostic way it's a real head scratcher when there weren't any obvious errors in the logs too.

I also had to explicitly install mongodb36-bin.

Unifi still requires mongodb<6 on 7.2.94 Depends list should be adjusted accordingly.

I can confirm, on a brand new arch VM who's job is to be a unifi box I was getting 404 errors when trying to access https://localhost:8443

Doing this change before building was enough for this machine's unifi UI to actually start working (Does not have other java environments present)

sed -i "s/'mongodb'/'mongodb36-bin'/g" PKGBUILD

I should also note that my CentOS 7 mongodb was so old that 36 was actually too great a jump. I had to build the mongodb34-bin AUR package first, run unifi with that, verify I could log in OK... then stop it, re-install/replace it with mongodb36-bin and now I'm able to use my migrated controller just fine.

Granted, anyone not migrating should be fine with mongodb36-bin right out the gate.

Rather than set java-8-openjdk/jre as the default java with archlinux-java, I modified the unifi.service file with systemctl edit --full unifi to select java-8 as described on the wiki. (https://wiki.archlinux.org/title/java#Launching_an_application_with_the_non-default_java_version) I need java-18-openjdk for some of my other AUR packages or they fail to build successfully.

Does Unifi support newer version of java if using oracle java? Or is java8 a requirement regardless? If java8 is a requirement, then it would probably be good to just make jre8-openjdk-headless a requirement and patch the service file accordingly.

May be changes provided by @CommanderCrisp should be come to PKGBUILD?

for me just forcing to install "mongodb50-bin" alongside unifi made unifi start working. (and deleting the previous newer db version files) The mongodb aur packages are now on version 6 which unifi is apparently not compatible with.