Closed sonicsjuuh closed 1 year ago
Hi,
Please try this run command:
docker run -d --name unifi-protect-x86 \
--tmpfs /srv/unifi-protect/temp \
-p 7080:7080 \
-p 7443:7443 \
-p 7444:7444 \
-p 7447:7447 \
-p 7550:7550 \
-p 7442:7442 \
-m 2048m \
-v "/mnt/user/Unifi Protect/unifi-protect-db":/var/lib/postgresql/10/main \
-v "/mnt/user/Unifi Protect/unifi-protect":/srv/unifi-protect \
markdegroot/unifi-protect-x86:latest
The web interface should run at https://localhost:7443/
but http on port 7080 might also work.
The MemoryLeak could be fixed with the -m 2048m
in the run command, but should not cause problems starting protect. When the initial setup is stuck at the loading screen you posted, try restarting the container.
The MemoryLeak could be fixed with the
-m 2048m
in the run command, but should not cause problems starting protect. When the initial setup is stuck at the loading screen you posted, try restarting the container.
That does remove the error. But the interface is still giving me the "Connecting to your NVR..." with the endless loading icon. :)
Maybe something to do with connection to STUN servers that are not working (UDP port 3478)?
Clear out your storage folders and recreate the container.
I managed to install the docker as per https://www.youtube.com/watch?v=a-VjH5M-8O0, thanks for the work @markdegrootnl !
I'm also testing it out in consideration to purchase some Unifi cams to utilize my existing Synology NAS.
Did you manage to connect your mobile app to the NVR? Unfortunately only the webgui is reachable on the LAN via 7443. Cloud remote access is enabled and I forwarded it on my router just in case but to luck over the internet neither, despite the login screen on the app showing the NVR with a green online icon. (just concerned if it's already locked down to verify the hardware to be a CKGen2P).
While container running and webgui reachable
While container is stopped
UPDATE strange before remote access enabled just fine, now when disabling and re-enabling I get this error.
Then refreshed the page and then it enabled again, but app login still won't work. :(
Turns out the current mobile app v 1.3.15 is having issues https://community.ui.com/questions/android-protect-app-not-connecting-to-controller-393222/e35ca485-a6b3-424f-9e7b-5eab5e9b9529
I managed to connect via v1.3.8 at last, over LAN and internet.
Nevertheless makes me concerned about this basic connection issue given other users reported this issue using their CloudKeyGen2+.
Turns out the current mobile app v 1.3.15 is having issues https://community.ui.com/questions/android-protect-app-not-connecting-to-controller-393222/e35ca485-a6b3-424f-9e7b-5eab5e9b9529
I managed to connect via v1.3.8 at last, over LAN and internet. Nevertheless makes me concerned about this basic connection issue given other users reported this issue using their CloudKeyGen2+.
Did you do anything special? Can i maybe see you unraid container setup page? Mine is working via cloud via a webbrowser, but the app is "unable to connect to the cloud key"
As mentioned I run the container on my Synology NAS, see YT video I posted.
Did you manage to enable remote access in the backend and tried the same app version?
My biggest fear is whether camera's firmware can auto update to a fw which might stop working with that old self hosted Protect version, being forced to buy a CKG2+.
Hi,
Turns out i was using the wrong version of the app, 1.3.8 is need. But it works now! Thanks for pointing that out.
Thanks for pointing out the version problem. Had the same aswell :D
Any plans to release a container with the newest version ?
Version 1.13.3 is the latest version UniFi has published for x86.
@sonicsjuuh did you ever get the instant running?
@sonicsjuuh did you ever get the instant running?
That's what I'm struggling with, too. I'm running version 1.5.2 of the UniFi Protect app on iOS 15 Beta 3. The docker is running on my Synology NAS and is set up per the YouTube video. I'm able to access the web interface for UniFi Protect via my computer's web browser but the iOS app can't find the console.
@martinjuhasz Sorry for the late respons. I did not get it running. I bought an UDM Pro some time ago with the doorbell and some cams because i really wanted to test out the platform to it's maximum. So i can't comment on it working or not.
It looks like there was an issue with the base image or one of the packages. After rebuilding the docker-image the "Connecting to your NVR..." issue is fixed.
I've just pushed a new version of the image to docker hub. Please try again with this version and let me know if it's fixed.
It looks like there was an issue with the base image or one of the packages. After rebuilding the docker-image the "Connecting to your NVR..." issue is fixed.
I've just pushed a new version of the image to docker hub. Please try again with this version and let me know if it's fixed.
Sorry, but it doesent seem fixed. I can logon fine in my browser Chrome on my Android phone, on home network, both lan and remote (ddns), But not on my laptop or stationary pc....? Tried different browser aswell... Chrome, edge and Firefox
To others trying to connect Instant... I bealive that its because we cant get latest Android/IOS app working with this image. If am not wrong the camera must be paired witth Bluetooth, but the old Android(1.3.8) app does not support it... :/ Maybe IOS does? I think Ive heard someone managed...
I had the same issues... so I did "network_mode: host" in my docker-compose.yaml and it fixed it.
I think we're discussing two different issues in this topic:
network_mode: host
. If you Adopt the Protect server with your UI.com Account during the setup, the app should connect not matter what.I think we're discussing two different issues in this topic:
- In the Webui, you get a blue screen with the text "Connecting to your NVR...". This should be fixed with the latest docker image.
- Newer versions of the Protect app for iOS and Android can't find/discover the Protect server. This might be due to UniFi trying to discover the protect server via Bluetooth or broadcasting network packets. Bluetooth discovery will never work with this Docker image. Network discovery might work, but only when using
network_mode: host
. If you Adopt the Protect server with your UI.com Account during the setup, the app should connect not matter what.
Yes you are right. . Sorry I was not detailed enough, my English is not the best :)
I still, with the new Docker Image get the blue screen Loading NVR when I try to logg in on all of my PC`s with WIN10. Tried different browsers (FF, edge, chrome). Tried my son´s pc aswell. But it works on my android phone using chrome browser...
All versions above 1.3.8 on Android Protect app cant connect. I have adopted to UI.com I believe it needs a version higher then 1.3.8 in order to connect Instant camera using bluetooth.
So it works, but only with v1.3.8 android protect app, but cant add instant camera.
Meybe I am doing something wrong. I see there is linked above to a YT tutorial. I have not done any ssh, only installed image with docker... I will try again.
Hope this makes sence, and thanks for your hard work @markdegrootnl
Hi,
first of all thanks for all the great work @markdegrootnl !
@Gizmopower1 issue nr 1 could be related to this: https://community.ui.com/questions/Google-Chrome-NET-ERRCERTREVOKED-for-UNMS/1947bccb-07df-4134-8c7f-fc01bf4b187d Try accessing with http on port 7080
Issue nr 2
I followed the youtube video because I am also running it on a Synology Diskstation. I have it running with network_mode: host
I have a G4 Doorbell and a G3 Instant Using an Apple device (with latest version of the App) I was able to add both devices. Using my Android device (with App 1.3.8) I was able to add the G4 Doorbell but it was unable to find the G3 Instant. (When adopting the Doorbell it automatically asked if I wanted to add the device on Apple and Android) Trying to manually adopt the G3 on android I noticed the it is not in the Camera list. So my guess is the 1.3.8 doesn't know this camera and therefore cannot add it to your system.
After adding the G3 Instant with an Apple device it works perfectly in the Android device with App 1.3.8
@arjanrenting Thank you for answering. Now I really know that it should work with Instant camera! Followed this tut: https://www.youtube.com/watch?v=a-VjH5M-8O0
I cant get the container running using --network="host" \
It just stops.
If I use the ports setting:
-p 7080:7080 \
-p 7443:7443 \
-p 7444:7444 \
-p 7447:7447 \
-p 7550:7550 \
-p 7442:7442 \
it works, but still loading blue screen Port 7080 also loading blue screen What am I doing wrong?
docker run -d --name unifi-protect-x86 \
--tmpfs /srv/unifi-protect/temp \
--network="host" \
-m 2048m \
-v /volume1/docker/unifi-protect-db:/var/lib/postgresql/10/main \
-v /volume1/docker/unifi-protect:/srv/unifi-protect \
markdegroot/unifi-protect-x86:latest
Cool, i was able to connect after updating (not sure if it had worked before). I still was unable to discover it (even with host mode) locally so i connected to my unifi account which then let me connect. This is fine for me as i only wanted this instance to configure my UVC G3 Instant. Using the latest iOS version of protect i was able to setup the wifi access for the Instant. Then it got stuck when trying to name the camera. But it is in my wifi now, which means i could access the http interface of the camera itself to configure it. Sad thing is, i cant see RTSP settings in there :(
There isn't local rtsp (standalone) in the uvc-instant. I have managed to get SSH direct into the camera now and am trying to see what I can enable, hack etc ;)
@k0d awww thats too bad. :(
I had the same issues... so I did "network_mode: host" in my docker-compose.yaml and it fixed it.
Could you tell me how to do this? Could try and see if it fixes my issue :)
@Gizmopower1 you can run it like this:
docker run -d --name unifi-protect-x86 \
--tmpfs /srv/unifi-protect/temp \
--network="host" \
-m 2048m \
-v unifi-protect-db:/var/lib/postgresql/10/main \
-v unifi-protect:/srv/unifi-protect \
markdegroot/unifi-protect-x86:latest
or remove all the port references in your docker-compose file and add network_mode: "host"
.
Also, to be absolutely sure you're using the latest docker image, run:
docker pull markdegroot/unifi-protect-x86:latest
@Gizmopower1 you can run it like this:
docker run -d --name unifi-protect-x86 \ --tmpfs /srv/unifi-protect/temp \ --network="host" \ -m 2048m \ -v unifi-protect-db:/var/lib/postgresql/10/main \ -v unifi-protect:/srv/unifi-protect \ markdegroot/unifi-protect-x86:latest
or remove all the port references in your docker-compose file and add
network_mode: "host"
.
@markdegrootnl When i run like that, the container stops after 7 sek. :/
@Gizmopower1 Could you run it without the -d
to see the output? Anything there that might give info why this happens? Maybe also add --privileged
and remove -m 2048m
just to try.
Output removing -d
database exists
Removed stale pid file.
su: System error
Database does not exist
mount: /srv/unifi-protect/temp: cannot mount tmpfs read-only.
CONFIG LOADED : /usr/share/unifi-protect/app/config/config.json
workers pool Read
is set to 4 concurrent workers
workers pool Write
is set to 8 concurrent workers
workers pool Transcode
is set to 8 concurrent workers
workers pool DnsResolve
is set to 16 concurrent workers
workers pool Misc
is set to 1 concurrent workers
workers pool Global
is set to 1 concurrent workers
workers pool Serve
is set to 106 concurrent workers
Cannot find module 'pg-native'
CONFIG LOADED : /usr/share/unifi-protect/app/config/config.json
Could not connect to database postgres...
RECOVERY MODE
Fetching recovery script : http://dl-origin.ubnt.com/unifi-video/internal/recover?v=1.13.3&mac=
Executing recovery script : /srv/unifi-protect/recover
@Gizmopower1 Did you execute the following on the folder you created for docker? chown 101:101 "/mnt/user/Unifi Protect/unifi-protect" chown 999:999 "/mnt/user/Unifi Protect/unifi-protect-db"
Without executing it it wouldn't create files in the 2 directories. Do you have files created there?
Also removing everything and start over helps.
Stop your docker image and execute docker volume prune
.
My log looks like this.
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale "C".
The default database encoding has accordingly been set to "SQL_ASCII".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /var/lib/postgresql/10/main ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... Etc/UTC
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
Success. You can now start the database server using:
/usr/lib/postgresql/10/bin/pg_ctl -D /var/lib/postgresql/10/main -l logfile start
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
Database does not exist
mount: /srv/unifi-protect/temp: cannot mount tmpfs read-only.
CONFIG LOADED : /usr/share/unifi-protect/app/config/config.json
2021-08-05T20:29:23.732Z - error: Watchdog fails to open log file Error: ENOENT: no such file or directory, open '/srv/unifi-protect/logs/watchdog.log'
2021-08-05T20:29:23.733Z - info: Initializing rollbar
workers pool Read
is set to 4 concurrent workers
workers pool Write
is set to 8 concurrent workers
workers pool Transcode
is set to 4 concurrent workers
workers pool DnsResolve
is set to 16 concurrent workers
workers pool Misc
is set to 1 concurrent workers
workers pool Global
is set to 1 concurrent workers
workers pool Serve
is set to 110 concurrent workers
Cannot find module 'pg-native'
CONFIG LOADED : /usr/share/unifi-protect/app/config/config.json
Certificate /srv/unifi-protect/data/unifi-protect.crt not found.... generating
Device certificate /srv/unifi-protect/data/devices.crt not found.... generating
2021-08-05T20:29:35.840Z - info: Parent receives startup-init
Thu, 05 Aug 2021 20:29:49 GMT sequelize deprecated String based operators are now deprecated. Please use Symbol based operators for better security, read more at http://docs.sequelizejs.com/manual/tutorial/querying.html#operators at usr/share/unifi-protect/app/node_modules/sequelize/lib/sequelize.js:245:13
2021-08-05T20:30:00.770Z - info: Parent process received startup-complete.
Yes, the database is created. Files are in both unifi-protect and unifi-protect-db folders... Done the chown as well.
This allows container to run properly, but blue loading screen.
docker run --name unifi-protect-x86 \ --tmpfs /srv/unifi-protect/temp \ -p 7080:7080 \ -p 7443:7443 \ -p 7444:7444 \ -p 7447:7447 \ -p 7550:7550 \ -p 7442:7442 \ -m 2048m \ -v /volume1/docker/unifi-protect-db:/var/lib/postgresql/10/main \ -v /volume1/docker/unifi-protect:/srv/unifi-protect \ markdegroot/unifi-protect-x86:lates
Output is:
Database exists, checking ownership
Database is already owned by unifi-protect
mount: /srv/unifi-protect/temp: cannot mount tmpfs read-only.
CONFIG LOADED : /usr/share/unifi-protect/app/config/config.json
workers pool Read
is set to 4 concurrent workers
workers pool Write
is set to 8 concurrent workers
workers pool Transcode
is set to 8 concurrent workers
workers pool DnsResolve
is set to 16 concurrent workers
workers pool Misc
is set to 1 concurrent workers
workers pool Global
is set to 1 concurrent workers
workers pool Serve
is set to 106 concurrent workers
Cannot find module 'pg-native'
CONFIG LOADED : /usr/share/unifi-protect/app/config/config.json
Sat, 07 Aug 2021 12:17:58 GMT sequelize deprecated String based operators are now deprecated. Please use Symbol based operators for better security, read more at http://docs.sequelizejs.com/manual/tutorial/querying.html#operators at usr/share/unifi-protect/app/node_modules/sequelize/lib/sequelize.js:245:13
I have done docker volume prune
When adding --privileged and removing -m 2048m Still stops after 10sek..
output is:
database exists
Removed stale pid file.
su: System error
Database exists, checking ownership
Database is already owned by unifi-protect
CONFIG LOADED : /usr/share/unifi-protect/app/config/config.json
workers pool Read
is set to 4 concurrent workers
workers pool Write
is set to 8 concurrent workers
workers pool Transcode
is set to 8 concurrent workers
workers pool DnsResolve
is set to 16 concurrent workers
workers pool Misc
is set to 1 concurrent workers
workers pool Global
is set to 1 concurrent workers
workers pool Serve
is set to 106 concurrent workers
Cannot find module 'pg-native'
CONFIG LOADED : /usr/share/unifi-protect/app/config/config.json
Sat, 07 Aug 2021 12:48:54 GMT sequelize deprecated String based operators are no w deprecated. Please use Symbol based operators for better security, read more a t http://docs.sequelizejs.com/manual/tutorial/querying.html#operators at usr/sha re/unifi-protect/app/node_modules/sequelize/lib/sequelize.js:245:13
Very similar situation here, installed into Synology NAS. If I set -network="host" it doesnt work, the container doesn't load, but if i leave ports it works. I can connect to admin panel from my android phone but not PC, also it does work with android app version 1.3.8, the latest version is asking for a Cloud KEY GEN 2 Plus. I can see these messages in the chrome console while I see blue screen and "Connecting to your NVR..." message, maybe those could track down where is the issue:
I'm not 100% certain, but I believe, when you don't use network="host" it thinks the only IP is the 172...* one from the docker container. web-rtc then sends that as the only IP that your browser can connect to, this means it will fail...as your computer can't connect to that IP.
But...when you connect with network="host", it will know your networks IP...and it can then connect.
I guess...with the android app...it figures out your IP through the cloud.
I don't have a solution yet...but this is just some info for you...
Oh...and the container probably fails to load with network="host" because it wants to use some ports that NAS is already using...port 80/443 likely.
Hi, for those running this container in Synology NAS and having an issue with network="host", I have found a way to run it. What I did I have created a virtual machine in Virtual Machine Manager, in my case it was Ubuntu 18 without GUI, installed docker there, and ran command:
docker run -d --name unifi-protect-x86 \ --tmpfs /srv/unifi-protect/temp \ --network="host" \ -m 2048m \ -v /home/your_name/unifi/unifi-protect-db:/var/lib/postgresql/10/main \ -v /home/your_name/unifi/unifi-protect:/srv/unifi-protect \ markdegroot/unifi-protect-x86:latest
And now it works without any issues, I can connect from my browser, from iPad, and the phone, after some testing it seems to run just fine. This solution is limited because I'm not sure if all Synology NAS supports virtualization on virtual machine manager, but this solution works for those who have it.
Still not able to run --network=host
But it´s ok! I have it running in docker on synology and using Android app 1.3.8 and https://protect.ui.com/ on pc
I manage to add Instant G3 camera with an IphoneXS and latest protect app. :)
Now another issue, or question. I am trying to add Unifi-protect to Homey.
When I try to log in from app in Homey, I get an error saying: Error: Invalid x-csrf-token header.
Anyone know what this error is, and can I get around it?
I know that people using the unifi dream machine, or unifi keygen2 can log on protect with Homey without problems.
I keep getting this error:
` This user must also own the server process.
The database cluster will be initialized with locale "C". The default database encoding has accordingly been set to "SQL_ASCII". The default text search configuration will be set to "english". Data page checksums are disabled.
initdb: could not change permissions of directory "/var/lib/postgresql/10/main": Operation not permitted fixing permissions on existing directory /var/lib/postgresql/10/main ... `
On Ubuntu 20.04 Docker I tried these: chown 101:101 "/docker/unifi-protect" chown 999:999 "/docker/unifi-protect-db"
But still it doesn't work. Just shuts down immediately after starting the container.
I have the Docker container running now for a few days and I can connect to it via the Unifi Protect app on my iPhone, iPad, and browsers. But I have 2 issues currently:
Hi Guys
first of all thanks for all the great work @markdegrootnl !
I have installed the protect all working well except the microphone, i can hear the person at the door but he cant hear me. WiFi signal is 100% on the same VLAN, alerts are working. it happen before i had to restart the G4 and the Mic came back, but now restart wont help. any idea what is the issue or what can i try? also does anyone know the port number the Mic use? thank you
@sonicsjuuh
Was wondering if you could post your unraid docker template? I'm having issues getting it to even run.
Thanks!
That worked for me.
As mentioned I run the container on my Synology NAS, see YT video I posted.
Did you manage to enable remote access in the backend and tried the same app version?
My biggest fear is whether camera's firmware can auto update to a fw which might stop working with that old self hosted Protect version, being forced to buy a CKG2+.
Are you still running version 1.3.8 ? Im getting the same error you did in 1.3.8
As mentioned I run the container on my Synology NAS, see YT video I posted. Did you manage to enable remote access in the backend and tried the same app version? My biggest fear is whether camera's firmware can auto update to a fw which might stop working with that old self hosted Protect version, being forced to buy a CKG2+.
Are you still running version 1.3.8 ? Im getting the same error you did in 1.3.8
Nevermind i had a dns manager running on my phone. When i disabled it i got it working.
I just installed the docker-image on my Synology NAS, and can install and adopt the application. However, i can't connect the iOS app to the console, it isn't discoverable.
Any ideas what i'm missing?
@rkops-bd Did you connect the controller to your unifi account? Maybe try that.
@rkops-bd Did you connect the controller to your unifi account? Maybe try that.
If you mean that the controller is adopted, yes. The strange thing is, is that the IP-adress of the controller isn't visible in the gui. Is that normal? And it says, that there is no update availble, but versio 1.20.* is already available at UI
This is the x86 (amd64) version. UniFi stopped supporting x86 at version 1.13.3, so that's why it shows no update.
Hello,
I have the same issue like @rkops-bd. Network is configured as host accessible via 7080 http and 7443 https Can't connect via the apps (iOS and Android) Controller 1.13.3 Web UI 1.20.0 Latest app version
My controller is connect to my unified account.
Any suggest ?
Thank you
use this config worked for me
docker run -d --name unifi-protect-x86 \
--tmpfs /srv/unifi-protect/temp \
--network="host" \
-p 7080:7080 \
-p 7443:7443 \
-p 7444:7444 \
-p 7447:7447 \
-p 7550:7550 \
-p 7442:7442 \
-m 6144m \
-v unifi-protect-db:/var/lib/postgresql/10/main \
-v unifi-protect:/srv/unifi-protect \
markdegroot/unifi-protect-x86:latest
@markdegrootnl
Ding my utmost here to get this working on docker desktop MAC. I too have the blue screen endlessly searching for "the NVR"
If I run as you describe in your reply docker run -d --name unifi-protect-x86 \ --tmpfs /srv/unifi-protect/temp \ -p 7080:7080 \ -p 7443:7443 \ -p 7444:7444 \ -p 7447:7447 \ -p 7550:7550 \ -p 7442:7442 \ -m 2048m \ -v "/mnt/user/Unifi Protect/unifi-protect-db":/var/lib/postgresql/10/main \ -v "/mnt/user/Unifi Protect/unifi-protect":/srv/unifi-protect \ markdegroot/unifi-protect-x86:latest
I get en error: The path /mnt/user/Unifi Protect/unifi-protect-db is not shared from the host and is not known to Docker. You can configure shared paths from Docker -> Preferences... -> Resources -> File Sharing. See https://docs.docker.com/desktop/mac for more info.
Even if I try: docker run -d --name unifi-protect-x86 \ --tmpfs /srv/unifi-protect/temp \ -p 7080:7080 \ -p 7443:7443 \ -p 7444:7444 \ -p 7447:7447 \ -p 7550:7550 \ -p 7442:7442 \ -m 2048m \ -v "/mnt/user/Unifi Protect/unifi-protect-db":/private/var/lib/postgresql/10/main \ -v "/mnt/user/Unifi Protect/unifi-protect":/srv/unifi-protect \ markdegroot/unifi-protect-x86:latest
There is the same error in return
If I add those paths to the json file in docker manually, and re-run, it shortly loads, but exits again.
database exists
Database does not exist
CONFIG LOADED : /usr/share/unifi-protect/app/config/config.json
mount: /srv/unifi-protect/temp: permission denied.
workers pool Read
is set to 4 concurrent workers
workers pool Write
is set to 8 concurrent workers
workers pool Transcode
is set to 4 concurrent workers
workers pool DnsResolve
is set to 16 concurrent workers
workers pool Misc
is set to 1 concurrent workers
workers pool Global
is set to 1 concurrent workers
workers pool Serve
is set to 110 concurrent workers
Cannot find module 'pg-native'
CONFIG LOADED : /usr/share/unifi-protect/app/config/config.json
Fri, 04 Feb 2022 15:25:58 GMT sequelize deprecated String based operators are now deprecated. Please use Symbol based operators for better security, read more at http://docs.sequelizejs.com/manual/tutorial/querying.html#operators at usr/share/unifi-protect/app/node_modules/sequelize/lib/sequelize.js:245:13
What can I try here?
Hey Mark,
First of all thank you for constructing this docker so we can try this out. I'm looking for a way to use Unifi Protect because i wanted to buy a Unifi doorbell and maybe some camera's. There is little hope (so says the internet) in an easy to use docker that's "plug-and-play" so i've started using my basic command knowledge to give it a go and use your docker.
I'm using Unraid as server so i'm trying to get this to work on my device.
Here's where i'm at:
I've installed the docker succesfully, remapping the ports, using bridge because the docker needs internet and giving my files the correct accessability
I think i edited the commands correctly. /mnt/user/Unifi Protect is the map i use for all of this. Let me know if i did something wrong here. I also did a 'chown' for 101 and 999.
My docker runs. But i can't connect at port 7447. There is nothing there. When i use 7080 i do get the webgui. I start the small setup. And then it gives me a blue screen that says 'Connectinto your NVR...' and it stays like that forever.
This is the log from my unraid server:
Maybe it has something to do with the "Possible EventEmitter memory leak"? No clue. i'm not super qualified for this :). Any help would be great.
Thank you and let me know if you need more info.