Package Details: unifi 6.4.54-1

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: 58
Popularity: 0.110474
First Submitted: 2017-08-22 01:31
Last Updated: 2021-09-20 14:55

Dependencies (3)

Required by (0)

Sources (6)

Pinned Comments

freswa commented on 2019-10-30 11:50

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

Latest Comments

1 2 3 4 5 6 ... Next › Last »

ZimbiX commented on 2021-10-09 11:41

@torben Thanks so much for the fix! https://localhost:8443 was inexplicably refusing connections, but adding

unifi.https.sslEnabledProtocols=TLSv1.2

to /usr/lib/unifi/data/system.properties got it working.

I reckon this should be done in the PKGBUILD, or at least suggested by it.

Additionally, as noted on later pages of comments, first installing mongodb-bin avoids many hours of compilation time for the mongodb package.

Strykar commented on 2021-09-08 22:29

Build fails with:

src/mongo/db/matcher/expression_type.h:74:30: note: remove 'std::move' call
src/mongo/db/matcher/expression_type.h: In instantiation of 'std::unique_ptr<mongo::MatchExpression> mongo::TypeMatchExpressionBase<T>::shallowClone() const [with T = mongo::InternalSchemaTypeExpression]':
src/mongo/db/matcher/expression_type.h:69:38:   required from here
src/mongo/db/matcher/expression_type.h:74:30: warning: redundant move in return statement [-Wredundant-move]
src/mongo/db/matcher/expression_type.h:74:30: note: remove 'std::move' call
src/mongo/db/matcher/expression_type.h: In instantiation of 'std::unique_ptr<mongo::MatchExpression> mongo::TypeMatchExpressionBase<T>::shallowClone() const [with T = mongo::TypeMatchExpression]':
src/mongo/db/matcher/expression_type.h:69:38:   required from here
src/mongo/db/matcher/expression_type.h:74:30: warning: redundant move in return statement [-Wredundant-move]
src/mongo/db/matcher/expression_type.h:74:30: note: remove 'std::move' call
scons: *** [build/opt/mongo/db/commands/touch.o] Error 1
scons: building terminated because of errors.
build/opt/mongo/db/exec/stagedebug_cmd.o failed: Error 1
build/opt/mongo/db/commands/touch.o failed: Error 1
==> ERROR: A failure occurred in build().
    Aborting...

torben commented on 2021-08-24 14:17

@code_xpert: I had the same problem a while ago IIRC. The problem was related to the database configuration being invalid. I can't remember it precicley, but in essence I had two config files for the wired tiger/mongod engine present, an old and a new one, where the package got confused during upgrade. Look in the config directory if there is everything ok there or if anything is supscious. I can't find any remnants of this anymore, but it was somewhere in /var/lib/unifi/data (maybe subdir "db"). I think, back than I did reactivate the old configuration somehow and the system went running again. Right now, my mongod db directory does not contain much configuration anymore, seems, that the current systemd scripts work primarily by command line arguments.

code_xpert commented on 2021-08-22 18:40

@torben I tried your fix because I had the same problem, and it worked! Thank you!

@medicineman25 he made the changes at "/usr/lib/unifi/data/system.properties".

I have a problem too. When I go to localhost:8443, it says "Unifi Controller is starting up..." for a brief second, then it says "Database Migration in progress..." forever. Has anyone experienced this problem too? How could I possibly fix this?

Thanks.

kode54 commented on 2021-08-01 10:10

Installed mongodb-bin 5.0.1-2. mongod crashes within seconds of restarting unifi.service with an out of memory error. Machine has 8GB of RAM and 8GB of swap.

Ketchup901 commented on 2021-07-17 21:17

@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.

wandinstallation commented on 2021-07-04 20:51

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

medicineman25 commented on 2021-07-04 18:50

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?

torben commented on 2021-05-19 18:22

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.

Eothred commented on 2021-05-19 09:49

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.