Package Details: unifi-video 3.8.5-2

Git Clone URL: (read-only)
Package Base: unifi-video
Description: Centralized management system for Ubiquiti UniFi Surveillance Cameras
Upstream URL:
Licenses: custom
Conflicts: unifi-video-beta
Submitter: fryfrog
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 5
Popularity: 0.895691
First Submitted: 2016-04-18 17:44
Last Updated: 2017-10-31 03:09

Latest Comments

fryfrog commented on 2017-09-20 22:05

Heads up, 3.8.0 adds a new port. If you're doing anything tricky, you'll need 7442 as well as the old 7443. A symptom I saw from this was that the cameras would connect after the update, do their firmware update and then never re-appear.

klden commented on 2017-07-23 04:30

@fryfrog @paco3346

chowning the config folder does fix the problem for the live view! Thanks for finding this out!

fryfrog commented on 2017-07-18 15:43

@paco3346: Sorry for not updating, I also help w/ the docker version and did that way back when 3.7.1 came out. Should have done this one too. :/

I checked inside my docker and that dir is all unifi-video:unifi-video.

I'll add a chown to the packages install/update and it'll "fix" it every install/upgrade at least. Or maybe it should be a pre-run in the systemd unit file? :/

paco3346 commented on 2017-07-18 13:43

Also, 3.7.1 has been out for a while

I've had no issues simply swapping out the version number and updating the sha256 hash.

paco3346 commented on 2017-07-18 13:41

No, just the first time. Once the config files are owned by the unifi-video user evostream never reverts them back to root.

What user owns the config files in /usr/lib/unifi-video/conf on Ubuntu?

fryfrog commented on 2017-07-18 03:30

@paco3346: Interesting, I wonder why this works on Ubuntu?

I *can* confirm you have to run their script as root, it complains otherwise. I can add the chown as a patch to the script they run perhaps.

It'd have this problem every time it started up, right?

paco3346 commented on 2017-07-18 03:08

@fryfrog I just installed this on another machine and had the same issue @klden described. The problem is that the evostreams binary is running as root so the first time it launches it creates a bunch of config files in /usr/lib/unifi-video/conf owned by root
Since the jar file runs as unifi-video it can't ever update these files which causes the backend streaming service (Evostream) to never be able to pick up on new camera streams (which is what breaks recording and live streaming).

Workaround: after you start unifi-video the first time run a chown -R unifi-video:unifi-video in /usr/lib/unifi-video/conf

I've not yet tested to see if you can run the systemd unit itself as unifi-video

klden commented on 2017-07-16 14:20

@fryfrog: yep it is from inside haha. I saw the logs from 1 of my camera and it couldn't connect to the unifi-server via port 6666. I'll spin up a ubuntu docker then! :D Thanks for your response!

Update: Your container image is working! Thanks!!

fryfrog commented on 2017-07-15 22:37

@klden: Are you having this issue *inside* your own network when going to the web ui directly? Or outside via port forward or their web portal? If outside, it is probably port forwards. If inside... that was one of the handful of issues I couldn't get sorted which made me spin up an Ubuntu docker instead. :/

klden commented on 2017-07-15 21:42

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

All comments