search

dciancu / unifi-protect-unvr-docker-arm64

UniFi Protect UNVR Docker container for arm64
https://hub.docker.com/r/dciancu/unifi-protect-unvr-docker-arm64
21 stars 0 forks source link

Unifi Protect Setup - Page Not Found / Latest Protect 4.0.21 #1

Closed dciancu closed 1 month ago

dciancu commented 2 months ago

There is an issue with the latest version of Unifi Protect 3.0.26, in the console it says Setup, but when clicked it redirects to a Page Not Found (/protect/setup). Checking further, seems to be a user permission issue, despite the admin role of the user. As always, Unifi .0 versions are not very stable and have issues, which is why I recommended using the stable tag on this image.

The stable version using Protect 2.9.42 works without issues.

Linked issue: https://community.ui.com/questions/Protect-not-opening-on-UDR/6632372e-e02d-4622-95ba-08567be0a535

f434a5d4-0e06-4e27-bdd1-4c8e2c5e237f d48c6e39-9c14-4fce-9345-5e07203034fc abb7aa47-1307-48a0-8f4a-185b61e4c269

dciancu commented 1 month ago

Still the same in the latest version 4.0.21.

Screenshot 2024-06-01 at 00 56 08

InfoX1337 commented 1 month ago

@dciancu Daniel, I've finally found the fix, join the early adopters club on the ubiquiti website (https://account.ui.com/profile), so that you are enrolled into the Early Access programme, then update the protect app to version 4.0.31. After the update it works like a charm. If you know how to update the Unifi OS version, please LMK. Im super interested in learning how to do that kind of stuff with UniFi software

dciancu commented 1 month ago

Hi, thank you for the tip, glad that this will be solved in a future release of Protect. Anyhow, I still think .0 versions are not very stable, which is the same experience I had with UniFi Network.

Unifi OS can not be updated inside the container image, because the updater downloads a firmware which it wants to flash to a non existing flash memory. Thus the way to update Unifi OS is to build the image, see the README for more info. If you can find the URL of the Unifi OS in Early Access program, then you can use FW_URL env var to build the image with that firmware.

I have set up auto-builds for this image, and when a new Unifi OS and/or Protect is released, the images will be rebuilt automatically.

InfoX1337 commented 1 month ago

Hi, thank you for the tip, glad that this will be solved in a future release of Protect. Anyhow, I still think .0 versions are not very stable, which is the same experience I had with UniFi Network.

Unifi OS can not be updated inside the container image, because the updater downloads a firmware which it wants to flash to a non existing flash memory. Thus the way to update Unifi OS is to build the image, see the README for more info. If you can find the URL of the Unifi OS in Early Access program, then you can use FW_URL env var to build the image with that firmware.

I have set up auto-builds for this image, and when a new Unifi OS and/or Protect is released, the images will be rebuilt automatically.

Thanks, didn't notice the build script. Will try it out, Thanks!

dciancu commented 1 month ago

@InfoX1337 Just realised FW_URL env var was not working as it was not being passed as build-argument to the firmware dockerfile. I have just fixed that (b1d4652). Let us know if UnifiOS firmware is also available in Early Access program.

InfoX1337 commented 1 month ago

@dciancu Will let you know soon, didn't get around to trying to build it myself yet.

dciancu commented 1 month ago

@InfoX1337 If you encounter any problems building, please let me know. Basically you just need to run build.sh script. With a custom FW_URL that would be FW_URL='https://ui.com/location-of-firmware' ./build.sh.

dciancu commented 1 month ago

The images have just been rebuilt, and this issue seems to be fixed now in the latest version of Protect 4.0.33 (edge tag).

npaolini-8 commented 1 month ago

Wanted to let you know that enabling functionality for edge let me adopt my cameras, thanks!