Hey, any idea why I can't see the live view for my camera? I can however see the jpg images every 1 sec :S
Search Criteria
Package Details: unifi-video 3.10.13-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/unifi-video.git (read-only, click to copy) |
---|---|
Package Base: | unifi-video |
Description: | Centralized management system for Ubiquiti UniFi surveillance cameras. |
Upstream URL: | https://www.ubnt.com/ |
Licenses: | custom |
Conflicts: | unifi-video-beta |
Submitter: | fryfrog |
Maintainer: | torben |
Last Packager: | torben |
Votes: | 10 |
Popularity: | 0.000000 |
First Submitted: | 2016-04-18 17:44 (UTC) |
Last Updated: | 2021-12-28 10:51 (UTC) |
Dependencies (6)
- java-jsvc
- java-runtime (jre10AUR, jre12AUR, jdk10AUR, jdk10-openj9-binAUR, jdk7AUR, jre7AUR, amazon-corretto-16AUR, jdk8-graalvm-binAUR, jdk16-graalvm-binAUR, jdk16-adoptopenjdkAUR, liberica-jre-11-binAUR, jdk11-j9-binAUR, jre11-jbr-xdgAUR, jre16-openjdkAUR, jre14-openjdkAUR, jre15AUR, jre14AUR, jre13AUR, jre16AUR, jre18-openjdkAUR, amazon-corretto-19-binAUR, jdk19-graalvm-binAUR, liberica-jre-11-full-binAUR, jdk19-graalvm-ee-binAUR, jdk13-openjdk-binAUR, liberica-jre-8-full-binAUR, jdk11-graalvm-binAUR, jre-openj9AUR, jdk11-graalvm-ee-binAUR, jre12-openjdkAUR, jdk11-dragonwell-standard-binAUR, jdk11-jetbrains-binAUR, jdk20-graalvm-binAUR, jdk17-graalvm-binAUR, jdk8-graalvm-ee-binAUR, jdk20-openj9-binAUR, zulu-13-binAUR, jdk8-dragonwell-extended-binAUR, jdk8-dragonwell-standard-binAUR, jdk11-dragonwell-extended-binAUR, jdk17-dragonwell-standard-binAUR, jre11AUR, jdk8-j9-binAUR, jdk7-j9-binAUR, jdk7r1-j9-binAUR, jdk8-dragonwell-extendedAUR, jre13-openjdkAUR, jre15-openjdkAUR, jdk21-graalvm-binAUR, jre17-jetbrainsAUR, jdk8-openj9-binAUR, jre-ltsAUR, microsoft-openjdk-11-binAUR, microsoft-openjdk-17-binAUR, microsoft-openjdk-21-binAUR, liberica-nik-24-full-binAUR, jre21-jetbrains-gitAUR, jdk21-jetbrains-gitAUR, zulu-17-binAUR, zulu-11-binAUR, zulu-8-binAUR, mandrel-binAUR, mandrel24-binAUR, liberica-jdk-17-full-binAUR, liberica-jdk-11-lite-binAUR, liberica-jdk-11-full-binAUR, liberica-jdk-11-binAUR, jdk17-graalvm-ee-binAUR, jdk21-graalvm-ee-binAUR, jdk22-graalvm-ee-binAUR, jdk20-graalvm-ee-binAUR, jdk22-graalvm-binAUR, jre19-openjdkAUR, jdk17-jetbrains-binAUR, zulu-jdk-fx-binAUR, jre21-jetbrainsAUR, jdk17-zulu-prime-binAUR, jre17AUR, java-openjdk-binAUR, amazon-corretto-17AUR, amazon-corretto-21-binAUR, jdk21-temurinAUR, amazon-corretto-8AUR, amazon-corretto-11AUR, jdk11-temurinAUR, liberica-jdk-full-binAUR, liberica-jdk-21-full-binAUR, liberica-jdk-8-full-binAUR, jdk17-temurinAUR, jdk8-temurinAUR, zulu-21-binAUR, jdk-temurinAUR, jre8AUR, jdk8AUR, zulu-17-fx-binAUR, jdk8-perfAUR, zulu-jre-fx-binAUR, zulu-fx-binAUR, zulu8-fx-binAUR, zulu11-fx-binAUR, zulu17-fx-binAUR, zulu21-fx-binAUR, jdk-openj9-binAUR, jdk11-openj9-binAUR, jre-jetbrainsAUR, jre-openjdk-wakefieldAUR, jdk-openjdk-wakefieldAUR, jdk21-openj9-binAUR, zulu-23-binAUR, jreAUR, jdkAUR, jdk21-jetbrains-binAUR, jre-zulu-binAUR, jre-zulu-fx-binAUR, jdk21-dragonwell-standard-binAUR, jdk21-dragonwell-extended-binAUR, jdk-android-studioAUR, jdk17-openj9-binAUR, jre-zuluAUR, jre-zulu-fxAUR, jre21-zulu-binAUR, jre17-zulu-binAUR, jdk23-graalvm-ee-binAUR, zing-8-binAUR, zing-21-binAUR, java-openjdk-ea-binAUR, jdk-openjdk, jdk11-openjdk, jdk17-openjdk, jdk21-openjdk, jre-openjdk, jre11-openjdk, jre17-openjdk, jre21-openjdk, jre8-openjdk)
- lsb-release
- mongodbAUR (mongodb32-binAUR, percona-server-mongodb-binAUR, mongodb36-binAUR, mongodb34-binAUR, mongodb40-binAUR, mongodb44-binAUR, mongodb42-binAUR, mongodb60-binAUR, mongodb50-binAUR, mongodb50AUR, ferretdbAUR, mongodb70-binAUR, ferretdb-binAUR, mongodb44AUR, mongodbAUR, mongodb-binAUR)
- which (busybox-coreutilsAUR)
- zip (zip-natspecAUR) (make)
Required by (0)
Sources (5)
klden commented on 2017-07-15 21:42 (UTC)
paco3346 commented on 2017-05-04 20:33 (UTC) (edited on 2017-05-04 20:33 (UTC) by paco3346)
It's good to give back. I almost had to give up and just spin up a Ubuntu 16.04 server but reeeaaally wanted to stay with Arch. Love my Arch.
fryfrog commented on 2017-05-04 19:21 (UTC)
Thanks a bunch to *you* for finding the issues. I'm using a docker container, but at some point I'll re-test running it native. :)
paco3346 commented on 2017-05-04 19:05 (UTC)
Ah yes, I see your permissions update in there. I think I probably caused a few things to be owned by root while I was poking around. (I ran a few things as sudo). Thanks for updating!
fryfrog commented on 2017-05-04 05:00 (UTC) (edited on 2017-05-04 05:28 (UTC) by fryfrog)
Thanks for poking around, I'll fiddle these changes into the package and see how it turns out.
Edit: Package updated, .patch file added to fix server.xml. And java-runtime>=8 dependency.
I'm not going to do a chown as part of it, that already happens as part of post_install.
paco3346 commented on 2017-05-04 02:40 (UTC) (edited on 2017-05-04 04:26 (UTC) by paco3346)
Bingo! 4 hours later...
There's something broken with the gzip compression in tomcat.
You can disable it by modifying /usr/lib/unifi-video/conf/server.xml and looking for all references of compression="on"
I'll let you guess what value you should update it to :)
Also, this is no longer jre7 compatible. Lots of "Could not initialize class javax.imageio.ImageIO" Runs swimmingly well with 8
Hey, me again. Edit #3. You'll also need to sudo chown -R unufi-video:unifi-video /usr/lib/unifi-video/conf/evostream/ if you run into problems with getting a single frame of video but no stream or recording
fryfrog commented on 2017-03-26 03:45 (UTC)
I had enough trouble w/ unifi-video on Arch that I've switched to using a docker image based on Ubuntu. I found an existing one that was pretty good and then improved the heck out of it.
If any of you are having trouble w/ it from this AUR package, consider giving the docker version a try.
https://hub.docker.com/r/pducharme/unifi-video-controller/
fryfrog commented on 2017-02-21 20:24 (UTC)
An Ubuntu vm was my next step if I hadn't just randomly tried to load up video.ubnt.com for no dang reason and it saw my nvr. I didn't even know it'd do that.
ssgross commented on 2017-02-21 19:03 (UTC)
Will try doing fryfrog's suggestion when i get a chance. For now, I have it up in running in a headless vm running ubuntu. i also had success with it working using a docker container following the suggestions of
https://github.com/rednut/docker-unifi-video-controller
fryfrog commented on 2017-02-19 03:58 (UTC)
Can those that have been having problems try doing the setup using https://video.ubnt.com from a computer on the network where the nvr software is installed? I just tried that after spending a few frustrating hours trying to do it as I'd expected using http://ip:7080/. It worked. :/
Pinned Comments
torben commented on 2023-01-04 09:20 (UTC) (edited on 2023-01-04 09:20 (UTC) by torben)
Please be aware, that Ubiquity has discontinued support for Unifi-Video..
I will keep an eye on this package while I am still using it, but please understand that without support von Ubiquity there isn't much I can do in case of problems with the app itself.
Also, I strongly recommend no longer publishing Unifi-Video unprotected on the Web. Work under the assumption, that this application can be breached.
torben commented on 2021-12-18 16:55 (UTC) (edited on 2021-12-27 14:04 (UTC) by torben)
Version 3.10.13-2 mitigates the log4j JNDI vulnerability out of the box
Be aware, that unifi-video is affected by the recent log4j JNDI Lookup vulnerabilities. As Ubiquity is no longer maintaining this piece of software, we can't expect an update.
The best mitigation (removing the JNDI Lookup Ability in log4j) for unifi-video can be found here:
https://community.ui.com/questions/Mitigating-the-Java-Log4J-exploit-in-UniFi-Video-on-Debian-Ubuntu/c59621d2-3cbf-48aa-9780-76477e0b1d39#answer/06ed75d6-113c-4230-9d44-7394e4ba2542
Basically, it removes the corresponding lookup-class from log4j-core.jar via:
I strongly recommend everybody to update either to 3.10.13-2 or to fix the log4j JAR file manually.