Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[support] pducharme's Dockers support thread

Featured Replies

Has anyone had success adding camera to the Unifi Video NVR? For whatever reason it's not detecting any of my cameras.

  • Replies 685
  • Views 161.8k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Glad to help, I was happy to find one that already exists and worked out of the box!

  • Hi,   To get inside the running docker, you can do the following :   Open an SSH connection to your Unraid Server (or on the server running the docker). Type:  docker exec

  • Hi Graham,   Just updated the UniFi to 5.5.24.  I also created a Beta branch, currently having 5.6.19.  (To get Beta branch, edit in advance mode the Docker page and change the repo by putti

Posted Images

Because they use some multicast thing, you can't fire up the container w/ all those port forwards in the normal mode and have it work. You should be able to use the adopt token and such. Or you can fire it up in --network="host" mode to add them, then drop back to normal.

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

^ This issue talks about another way where the container gets its own mac and IP, you could try it and see how it goes.

6 minutes ago, fryfrog said:

Because they use some multicast thing, you can't fire up the container w/ all those port forwards in the normal mode and have it work. You should be able to use the adopt token and such. Or you can fire it up in --network="host" mode to add them, then drop back to normal.

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

^ This issue talks about another way where the container gets its own mac and IP, you could try it and see how it goes.

If I'm understanding correctly this would only work for Unifi branded cameras - what about 3rd party like Hikvision?

Unifi Video is only for Unifi Video cameras, correct. Other cameras do not work with it. For that, you'll need something else. The only one I know of is Synology's Surveillance Station, but there are others for sure. I just don't know their names! :)

Since the latest beta it wont start, just says upgrading when hitting the URL for hours

Check the logs, see what is going on.

Any updates on how to fix mongodb? Wired tiger isnt supported by the unifi nvr

I tried to go back to the latest repository and that wont start at all.  I deleted my docker image and started over and still the same result.  I get the following error:

2018-10-04 22:14:54.888756 [warn] PUID not defined (via -e PUID), defaulting to '99'
2018-10-04 22:14:54.969258 [warn] PGID not defined (via -e PGID), defaulting to '100'
2018-10-04 22:14:55.023655 [info] Setting permissions recursively on volume mappings...
chown: cannot read directory '/var/lib/unifi-video/videos/2ee90163-4814-39bf-aaea-9d89b94246c6/2018/08/26': Structure needs cleaning

 

There isnt anything in the directory as I deleted everything to start completely fresh.  I have no idea where I am supposed to go from here.  It looks like there is some configuration somewhere left from the previous docker but I have no idea where since I deleted the appdata folder and the whole docker image for everything.

  • 2 weeks later...

I´m having issue starting the docker. It´s getting stuck on "starting controller services". I have tried deleting the data folder and starting over without any success. The data path for the docker is on a SSD outside of the array. The log show mongdb start over and over again.

Quote

2018-10-13T20:12:37.114+0200 I CONTROL  [main] ***** SERVER RESTARTED *****
2018-10-13T20:12:37.116+0200 I CONTROL  [initandlisten] MongoDB starting : pid=340 port=7441 dbpath=/usr/lib/unifi-video/data/db 64-bit host=9342c6108066
2018-10-13T20:12:37.116+0200 I CONTROL  [initandlisten] db version v3.4.17
2018-10-13T20:12:37.116+0200 I CONTROL  [initandlisten] git version: 7c14a47868643bb691a507a92fe25541f998eca4
2018-10-13T20:12:37.116+0200 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2n  7 Dec 2017
2018-10-13T20:12:37.117+0200 I CONTROL  [initandlisten] allocator: tcmalloc
2018-10-13T20:12:37.117+0200 I CONTROL  [initandlisten] modules: none
2018-10-13T20:12:37.117+0200 I CONTROL  [initandlisten] build environment:
2018-10-13T20:12:37.117+0200 I CONTROL  [initandlisten]     distmod: ubuntu1604
2018-10-13T20:12:37.117+0200 I CONTROL  [initandlisten]     distarch: x86_64
2018-10-13T20:12:37.117+0200 I CONTROL  [initandlisten]     target_arch: x86_64
2018-10-13T20:12:37.117+0200 I CONTROL  [initandlisten] options: { net: { bindIp: "127.0.0.1", http: { enabled: false }, port: 7441 }, storage: { dbPath: "/usr/lib/unifi-video/data/db", jo$
2018-10-13T20:12:37.132+0200 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=15586M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statisti$
2018-10-13T20:12:37.148+0200 E STORAGE  [initandlisten] WiredTiger error (17) [1539454357:148472][340:0x1543f8db2180], connection: /usr/lib/unifi-video/data/db/WiredTiger.wt: handle-open: $
2018-10-13T20:12:37.148+0200 I STORAGE  [initandlisten] WiredTiger message unexpected file WiredTiger.wt found, renamed to WiredTiger.wt.7
2018-10-13T20:12:37.149+0200 E STORAGE  [initandlisten] WiredTiger error (1) [1539454357:149074][340:0x1543f8db2180], connection: /usr/lib/unifi-video/data/db/WiredTiger.wt: handle-open: o$
2018-10-13T20:12:37.149+0200 I -        [initandlisten] Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 277
2018-10-13T20:12:37.149+0200 I STORAGE  [initandlisten] exception in initAndListen: 28595 1: Operation not permitted, terminating
2018-10-13T20:12:37.149+0200 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2018-10-13T20:12:37.149+0200 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-7441.sock
2018-10-13T20:12:37.149+0200 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2018-10-13T20:12:37.149+0200 I CONTROL  [initandlisten] now exiting
2018-10-13T20:12:37.150+0200 I CONTROL  [initandlisten] shutting down with code:100
2018-10-13T20:12:47.186+0200 I CONTROL  [main] ***** SERVER RESTARTED *****

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='UniFi-Video' --net='br0' --ip='192.168.10.60' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -v '/mnt/disks/programs/appdata/unifi-video/':'/var/lib/unifi-video/':'rw' 'pducharme/unifi-video-controller'

367800981e4d63ce68223372f10c967468ee2fca1b99a1f77acd4d40cb95555b

 

would it be possible to get the beta branch for the Video Controller brought up to 3.10.0 Beta 1?

 

Thanks

Edited by spyd4r

It is and has been for awhile, unless you're saying they changed the 3.10.0 beta 1 .deb file?

Has anyone found a way around the mongodb problems?

  • 3 weeks later...

Any updates? I reinstalled and stuck on "Starting Controller Services"

 

Starting unifi-video... (unifi-video) checking for system.properties and truststore files...

Edited by bluesky509

You're going to need to look into unifi video logs and help figure out the problem. My instance runs fine and w/o anything useful, nothing is going to change.

It looks like Ubiquiti is going proprietary with video.  From what I've read they are switching to Unifi Protect and with it you will not be able to setup your own NVR.  It looks like you will have to buy their Unifi CloudKey Gen2 Plus (which hoses a 2.5" hard drive) to record the video.  No word on what will happen to the Unifi Video software but it will likely be abandoned.  Here is a link to some discussion:

 

https://community.ubnt.com/t5/UniFi-Protect/Protect-for-Linux/td-p/2512166/page/2

Edited by RockDawg

  • Author
2 hours ago, RockDawg said:

It looks like Ubiquiti is going proprietary with video.  From what I've read they are switching to Unifi Protect and with it you will not be able to setup your own NVR.  It looks like you will have to buy their Unifi CloudKey Gen2 Plus (which hoses a 2.5" hard drive) to record the video.  No word on what will happen to the Unifi Video software but it will likely be abandoned.  Here is a link to some discussion:

 

https://community.ubnt.com/t5/UniFi-Protect/Protect-for-Linux/td-p/2512166/page/2

 

If it happen like they said, this docker will be not maintained anymore.  I plan on buying the CloudKey Gen2 Plus soon anyway.

  • 2 weeks later...

Is this right? Not sure why it needs 4.75 GB, or is it just a huge file?

 

image.png.e11b16b7daea1d6fc650a167628ce460.png

I ran the app called file activity. I show it hitting the .dat files many many times off disk3. I have the sara blueiris set to Yes for cache. 

 

Is there something I am missing? Trying to get it where 90% of the time my cache is used.

1 hour ago, scubieman said:

I ran the app called file activity. I show it hitting the .dat files many many times off disk3. I have the sara blueiris set to Yes for cache. 

 

Is there something I am missing? Trying to get it where 90% of the time my cache is used.

Cache yes means new files written to the share go to the cache if there is enough space, then moved to the array when the mover is activated.

 

If that is not what you want, turn on the help on the share settings page and read up on the different cache modes.

 

Keep in mind the mover will not move files that are open.

I do have it set to yes. However it is still reading off array instead of moving to cache for reading.

 

question is if a file is being read from array does it get moved to cache?

8 minutes ago, scubieman said:

I do have it set to yes. However it is still reading off array instead of moving to cache for reading.

 

question is if a file is being read from array does it get moved to cache?

I haven't been following but you seem to have misunderstood. Cache-yes are NOT moved TO cache. They are moved FROM cache. Cache-prefer is the setting to get moved TO cache.

 

10 minutes ago, jonathanm said:

Cache yes means ... moved to the array when the mover is activated.

 

If that is not what you want, turn on the help on the share settings page and read up on the different cache modes.

 

Keep in mind the mover will not move files that are open.

 

2 minutes ago, trurl said:

I haven't been following but you seem to have misunderstood. Cache-yes are NOT moved TO cache. They are moved FROM cache. Cache-prefer is the setting to get moved TO cache.

 

 

Understood thank you!

  • 1 month later...
  • Author
2 hours ago, Jomp said:

Is there any way to get the beta version updated to beta3, up from the current beta1? I would love to enable the new motion algorithm. 

 

“The instructions to enable the algo in 3.10 beta1 were the same but in beta3 they added it to the GUI and the camera firmware is newer.”

 

https://community.ubnt.com/t5/UniFi-Video/How-is-this-is-motion-detection-feature-in-2018/td-p/2601915

 

 

Hi, I just triggered a build on Beta branch with the 3.10.0-beta.3.  Should be available soon, when Docker finish building it.

 

-EDIT-

 

Should be available now.

Edited by Pducharme

57 minutes ago, Pducharme said:

 

Hi, I just triggered a build on Beta branch with the 3.10.0-beta.3.  Should be available soon, when Docker finish building it.

 

-EDIT-

 

Should be available now.

 

 That was speedy, thank you very much! Hopefully this helps with all the annoying illumination change recordings..

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.