| Git Clone URL: | https://aur.archlinux.org/unifi.git (read-only, click to copy) |
|---|---|
| Package Base: | unifi |
| Description: | Centralized management system for Ubiquiti UniFi AP |
| Upstream URL: | https://unifi-network.ui.com |
| Licenses: | custom |
| Conflicts: | tomcat-native |
| Submitter: | seblu |
| Maintainer: | freswa |
| Last Packager: | freswa |
| Votes: | 72 |
| Popularity: | 1.42 |
| First Submitted: | 2017-08-22 01:31 (UTC) |
| Last Updated: | 2025-06-16 11:46 (UTC) |
Once again, a mongodb upgrade breaks unifi. Please patch the PKGBUILD:
-depends=('mongodb' 'java-runtime-headless>=17' 'fontconfig')
+depends=('mongodb<7' 'java-runtime-headless>=17' 'fontconfig')
Previously: https://aur.archlinux.org/packages/unifi?O=30#comment-883689 https://aur.archlinux.org/packages/unifi?O=40#comment-875455 https://aur.archlinux.org/packages/unifi?O=40#comment-875286
quietvoid, check the deps.
Thanks. I've updated to jre17-openjdk-headless and it seems to work.
quietvoid, check the deps.
The service won't start for me with 7.5.174-2
systemd[1]: Started Ubiquiti UniFi Server.
java[1738284]: Error: LinkageError occurred while loading main class com.ubnt.ace.Launcher
java[1738284]: java.lang.UnsupportedClassVersionError: com/ubnt/ace/Launcher has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0
systemd[1]: unifi.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: unifi.service: Failed with result 'exit-code'.
Downgrading to 7.4.162-1 works again.
7.5.174 was just pulled from the stable release channel.
Upgrading to this latest package breaks the controller app, java version doesn't matter, tried with both Java 17 and Java 20 ... error is consistent with web context failed to initialize
Sep 05 09:14:17 tor java[7054]: Exception in thread "launcher" java.lang.NullPointerException: Web context failed to initialize
Sep 05 09:14:17 tor java[7054]: at java.base/java.util.Objects.requireNonNull(Objects.java:259)
Sep 05 09:14:17 tor java[7054]: at com.ubnt.net.OoOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO>
Sep 05 09:14:17 tor java[7054]: at com.ubnt.net.OoOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO>
Sep 05 09:14:17 tor java[7054]: at com.ubnt.service.Object.øÓ0000(Unknown Source)
Sep 05 09:14:17 tor java[7054]: at com.ubnt.ace.Launcher.Object(Unknown Source)
Sep 05 09:14:17 tor java[7054]: at com.ubnt.ace.Launcher.main(Unknown Source)
Edit: This was the initial package for 7.5.174-1, I see it has been updated. Also, I was able to successfully roll back to 7.4.162-1. Had to be careful with the journal permissions for mongodb.
With version 7.4.162-1 I can get access to the web controller at https://localhost:8443 but only if I use java 11 as described by @kuon in their 2023-03-13 00:54 (UTC) comment.
I am getting the 404 error as well.
I am getting a HTTP Status 404 – Not Found when visiting the web page after starting the server
@Auerhuhn Thx, fixed
Pinned Comments
freswa commented on 2019-10-30 11:50 (UTC)
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