I pushed 3.10.4 to testing a few days ago and I've been running it locally, I'll promote it to release today.

Just wanted to say thanks for pushing the update ... Thanks!

Updated to 3.10.4 today without issue.  Nice work!

Looks like there's a new update. Can we get the docker updated, please?

 

 

@fryfrog I see you've been testing v3.10.5 since about 13 days ago?  Stable?  If so, wanna move it to the latest tag?

Sorry, forgot about it again! Pushed and tagged. :)

1 hour ago, fryfrog said:

Sorry, forgot about it again! Pushed and tagged.

 

Thanks for the quick response!

I believe the docker got an update over the last few days, now when I try to look at recordings, only the current day shows. Nothing else is there.

 

Anyone seen this behavior before?

 

Got this in the error log when I try to recover the database under config

1562943122.591 2019-07-12 09:52:02.591/CDT: ERROR [uv.recording.sync] Unable to process: /media/recordings in RecordingSynchronizationTask 1562943122.588 2019-07-12 09:52:02.588/CDT: ERROR [uv.recording.sync] Unable to process: /media/camera in RecordingSynchronizationTask 1562942781.886 2019-07-12 09:46:21.886/CDT: ERROR [uv.db.svc] Failed to acquire client connection null in MongoDb-Connecting

 

Strange if I try to to last week/month recordings show, but not specified times. Its almost like the indexing on recordings is not functional so I am assuming it has something to do with the MongoDB?.

 

For now downgrading controller and cameras fixes the cant see recordings issue. If anyone has any ideas with regards to this, much appreciated.

server.log

Edited July 12, 20196 yr by kaine1688

Looks like there are issues with the latest UniFi-Video updates from Ubiquity. This is what I am seeing for my alerts:

 

I tried to use the unifi-video container it installs, but on first run it does not start the unifi-video service, I can console in to start it or a container restart will start it. The real issue is when it starts it props for login not the setup wizard which makes it useless since you cant add a user.

Try the `:3.10.6` tag and see if that works. They've changed something in 3.10.7 or 3.10.8 and people are seeing what you see.

https://github.com/pducharme/UniFi-Video-Controller/issues/158

^ The issue for it, I haven't had any time to look, but others have. Maybe give it a look and contribute anything you find?

Edited October 2, 20196 yr by fryfrog

3.10.6 and 3.10.5 starts to work the wizard comes up for NVR name and UTC then next to user setup then clicking next goes to login screen, it doesn't finish the wizard.

I just cycled through the wizard like 3 times on `:3.10.6` and it worked every time, just fine. Make sure the folders it needs to write to have the correct ownership and permissions maybe?

I've checked permissions, tried different install places everything i can think of. The wizard still going from user setup to login (it skips the step to get camera password and button to go to cameras) and cant log in with user and password i set. I try and come back to it later.

I made a backup within Unifi-Video and nuked my docker installation (deleted the appdata folder as well).  Now after a fresh docker pull from CA and setting the is_default=true setting within system.properties, the docker log shows "(unifi-video) checking for system.properties and truststore files...
done." and the docker will not load the web ui for Unifi-Video.  If I remove the system.properties file the webui will appear but login is not possible, obviously. 

 

I am not sure what else I can try from my end to get this docker back up and running.

 

Steps Taken:

 

1. Delete docker and image

2. Remove dangling images from docker using user scripts

3. Remove docker template from previously installed dockers within CA

4. Create appdata folder with a system.properties file with is_default = true

5. Install docker making sure folder mappings are correct

 

I have also tried skipping step 4 and starting then stopping the new docker install and then creating the system.properties file.

 

The docker seems to only use about 8mb of ram and a very small amount of CPU while its in the hanging state with the system.properties file present with is_default=true. 

There is something weird between 3.10.6 and 3.10.8 that I still haven't quite figured out. On github, https://github.com/pducharme/UniFi-Video-Controller/issues/158 this issue is talking about it. The best I can find so far is that in one version, it fires up w/ the wired tiger config and in later versions it fires up w/ the old style database. Maybe based on the version of mongodb.

Read the whole issue first, but I think if you start with a working version running `:3.10.6` and then update to `:beta` it might work. Right now, the beta branch has mongodb 4.0 while the `:latest` has 3.6.

Thanks fryfrog!

 

I think this may be an issue for the Unifi forums, but I guess its worth checking here....

 

I nuked my installation because I cannot connect my docker to the Unifi Cloud so I can remotely view my cameras.  I go through the process, it finds my NVR, and stays on the connected screen until it times out with an error reading "cannot connect to NVR" but if i go back to the UI for the docker under settings it shows my NVR is connected to the cloud anyways.  I try to connect to my cameras using the iOS app and although my NVR shows up I cannot connect to it.  Not sure if this is a common problem already solved by someone on this forum, or if I will have to dig deep on this one.

 

I have tried with a completely fresh NVR docker and I still get the same behavior.  I am using Chrome with the Device Discory Tool from Ubiquiti installed.

Edited October 9, 20196 yr by nblain1

I am Unable to set up this docker for the first time, When i load the page after installing this docker it asks me for username / password. anyone know how to proceed from here?

Ubnt and ubnt are the default username and password. 

32 minutes ago, sunnyd425 said:

Ubnt and ubnt are the default username and password. 

Already tried that no joy

 

when i start the container fresh i get 

 

2019-10-15 19:33:20.364220 [warn] PUID not defined (via -e PUID), defaulting to '99'
2019-10-15 19:33:20.733027 [warn] PGID not defined (via -e PGID), defaulting to '100'
2019-10-15 19:33:21.150279 [info] Setting permissions recursively on volume mappings...
Starting unifi-video... (unifi-video) Hardware type:Unknown
(unifi-video) checking for system.properties and truststore files...
(unifi-video) WARNING!!!! system.properties cannot be found..restoring from : /usr/lib/unifi-video/etc/system.propetties

done.

 it gets stuck there no web ui. if i then force a restart of the container.

 

2019-10-15 19:33:20.364220 [warn] PUID not defined (via -e PUID), defaulting to '99'
2019-10-15 19:33:20.733027 [warn] PGID not defined (via -e PGID), defaulting to '100'
2019-10-15 19:33:21.150279 [info] Setting permissions recursively on volume mappings...
Starting unifi-video... (unifi-video) Hardware type:Unknown
(unifi-video) checking for system.properties and truststore files...
(unifi-video) WARNING!!!! system.properties cannot be found..restoring from : /usr/lib/unifi-video/etc/system.propetties

done.
Waiting for mongodb to come online.........................................................................................................................................................................................................................................................................Stopping unifi-video... done.
2019-10-15 19:42:21.317846 [warn] PUID not defined (via -e PUID), defaulting to '99'
2019-10-15 19:42:21.339894 [warn] PGID not defined (via -e PGID), defaulting to '100'
2019-10-15 19:42:21.664134 [info] Permissions already set for volume mappings
Starting unifi-video... (unifi-video) Hardware type:Unknown
(unifi-video) checking for system.properties and truststore files...
done.
Waiting for mongodb to come online..... done.

And then i get the webUI however i get a login screen that i have no credentials for.

 

Edited October 15, 20196 yr by Target-Bravo
More Info

Any chance of having a Unifi Protect docker added to the Community application plugin now that the the amd64 .deb has been released?

https://apt.ubnt.com/pool/beta/u/unifi-protect/unifi-protect.jessie~stretch~xenial~bionic_amd64.v1.12.5.deb

That would be just awesome. Currently running it in a VM, but would love to use it as a Docker instance instead.

I got one working at fryfrog/unifi-protect, but it looks like releasing 1.12.5 was another mistake, not a sign of them finally doing a proper release. I'll probably re-fiddle my image to take a `.deb` again, but will leave it up as is for now.

Fresh Unifi Video docker does not accept default ubnt/ubnt credentials, writing is_default=true into system.properties have no effect - file is always overwritten with empty file on startup.

 

Rebooting container once will yield it inoperable as webui would stop responding.

I can confirm that writing "is_default=true" simply makes it so that Unifi-Video rebuilds the database but it will always return me to the login window.

 

The only thing I altered from the original template is the installation folder. I don't have a cache drive anymore so I just installed it in the array (user/appdata).

Edited October 27, 20196 yr by migueldias

Hey, I just tried setting up `:3.10.6` fresh and updating to `:beta`, it worked. I was also able to start w/ a fresh `:beta` and do the wizard and restart it a few times and it all worked. So I went ahead and pushed the MongoDB 4.0 update to `:latest`.