Diskstation Container Manager

[Aescleal375]

! Very docker nube here !
I have both UDM-Pro and a Synology NAS (920+). I'm sure that's not unique in any way!!!

I actually found out about this by browsing the Registry in Container Manager. THIS sounds like what I've been hoping for for about 2 years!
I don't know Docker very well at all, but I do run a number on my Synology. Can anybody help me get this up and running in Container Manager? Or point me to some documentation on how to get set up?

I run 6 other dockers this way (Portainer, Adguard, Homebridge, etc.)

I have a couple Unifi cameras, but even more Eufy cameras that I'd love to add in and manage from the same Unifi console.

Thanks!

[Aescleal375]

What I've accomplished so far but could really use some help!

In full discloser, it did run once for a prolong period (maybe 5 hours), but was mostly a still image that couldn't seem to refresh. So I rebuilt it and haven't been able to get running again since.

I get the container project set up.

• I get a certificate from my G3 Instant I use to keep an eye on my cat
• I generate at token from {UDM-Pro-IP}/proxy/protect/api/cameras/manage-payload
• I enable rtsp on a Eufy cam
• I build the compose.yaml using the UniFi-cam-proxy .yaml template (says it successful)
  After that the container start, and a minute later starts shutting off and on again until it just doesn't start any more.
  There are logs. I can provide if needed to help.
  It seems to be so close.

[andy83-projects]

@Aescleal375 interesting, /proxy/protect/api/cameras/manage-payload just redirects me to /protect/devices

[Aescleal375]

@andy83-projects Interesting. Are you logged in as admin before you open the path? That happens to me too, maybe the browser caches the page. But a purposeful Logon beforehand seems to work for me.

[andy83-projects]

Ya I tried even from an incognito page. I think my UDM is fully up to date.

…

On Tue, Aug 15, 2023, 21:22 Aescleal375 ***@***.***> wrote: Interesting. Are you logged in as admin before you open the path? That happens to me too, maybe the browser caches the page. But a purposeful Logon beforehand seems to work for me. — Reply to this email directly, view it on GitHub <#316 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANYNBQ276AXSHD2FYFXVANDXVQOF3ANCNFSM6AAAAAAZY46E34> . You are receiving this because you commented.Message ID: ***@***.*** com>

[Aescleal375]

8/22/2023:

First off, Koodos to keshavdv! This is a freaking awesome and ambition project that probably most Protect users will benefit from.

I hope you can keep the project active and your motivation strong!

Here's where I'm at trying to get set up:
-The container builds and starts.
-It shows up in Protect as awaiting adoption, long enough to click adopt.
-Soon after it goes offline and doesn't come back online.

I've tried resetting the container, rebuilding the project, etc. I've renewed the token time and time again... If this ever works, it will be the best body of work ever, to get non-unifi cameras actively running in the Protect console! Wow!

Does anybody have a working solution?

Thx

[Aescleal375]

Update:
A tweak in the yaml file seems to have made it stay up and running. Multiple client command I left out a / before client.pem. Putting the / back in fixed that part.

The new camera stays up and active, however does not update very often (more like still image) and is quite blurred most times.

Still looking for anyone who has successfully gotten this to run and provide some advice.

Thanks

[Aescleal375]

Does anybody have a working yaml file for RTSP cameras? Maybe there are tweaks I can make?

Thanks in advance!

[Aescleal375]

My yaml file:

version: "3.9"
services:
eufy-1-proxy:
restart: unless-stopped
image: keshavdv/unifi-cam-proxy
volumes:
- "./client.pem:/client.pem"
command: unifi-cam-proxy --host 192.168.2.1 --cert /client.pem --token "qQETFjLPwJOsWggsTUm7ck8TuCLETuLT" rtsp -s rtsp://uuuuuuu:[email protected]/live0

[Aescleal375]

This loads and stays active, but is still shots only and always horribly outdated.

[drinksomewhiskey]

I am a bit confused on the install myself. I created a project in container manager with the following compose:

version: "3.5"
services:
  proxy-1:
    container_name: unifi-proxy
    restart: unless-stopped
    image: keshavdv/unifi-cam-proxy
    volumes:
      - "./client.pem:/client.pem"
    command: >-
        unifi-cam-proxy
        --host 192.168.X.X
        --mac 'AA:BB:CC:00:11:22'
        --cert /client.pem
        --token XXXXXXXXXXXXXXXXXXXXXXX
        rtsp -s rtsp://192.168.201.15:8554/cam

The container builds but fails to run stating: Bind mount failed: 'volume1/docker/unifi-proxy/client.pem' does not exists.

Can anyone explain what files I need to place in my volume1/docker/unifi-proxy folder? I am following the installation guide https://unifi-cam-proxy.com and theres no mention of a client.pem file.

[Aescleal375]

I don't add an extra container name, just named by the proxy name [proxy-1]
Each time you rebuild, you should get a fresh token, they only last 30 minutes or so.
Mine builds and stays running. However, it doesn't refresh and each time you open it, it is just a still image.
Lastly, see screenshot of Docker folder. You need the client.pem file. I export mine from one of my existing Unifi cameras. It seems to work.

version: "3.9"
services:
eufy-1-proxy:
restart: unless-stopped
image: keshavdv/unifi-cam-proxy
volumes:
- "./client.pem:/client.pem"
command: unifi-cam-proxy
--host 192.168.2.1
--cert /client.pem
--token "uQETFjLPwJOsWggsTUm7ck8TuCLETuLT"
rtsp -s rtsp://G0thT7EaG:[email protected]/live0

[Aescleal375]

[drinksomewhiskey]

"Lastly, see screenshot of Docker folder. You need the client.pem file. I export mine from one of my existing Unifi cameras. It seems to work."

Thank you for the details. Can you please expand on how you exported the client.pem file from an existing camera?

I will give this a shot a report back.

[Aescleal375]

Hi drinksomewhiskey. I didn't bookmark what I used. You can google it though and find it pretty quick. My UI cameras are managed by my UDMPro. So for me I had to ssh into the UDMP and export from there. Again, I can look for it again, but you may find it just as fast yourself. It was actually a fast and painless process.

[Aescleal375]

Actually I did bookmark it after all. https://unifi-cam-proxy.com/
Step one is for the client.pem. Admittedly, I did fiddle with it some and you have to make it your own IP's and such, but moreover that's what you need to do.

What I did was "Forget" the camera in Unifi. And before readopting, I ssh into the IP address of the unifi cam with ubnt/ubnt and run: scp ubnt@:/var/etc/persistent/server.pem client.pem

That dumps the client.pem in your current directory on your computer. Then you just copy that to your folder on your NAS.
Rebuild your unifi-cam-proxy docker project with a new token key from (http://YOURUDMPROIPADDRESS/proxy/protect/api/cameras/manage-payload) and that should get you up and running.

It does for me except for the nagging camera stills issue I'm having.

[Aescleal375]

So here's the thing. I don't know how this camera works at all, since in Unifi it displays at 192.168.1.10, which is not a subnet on my network at all. It's not a vlan, it's not a subnet, it's not on my network. Yet, Unifi still sees the camera. That said, no matter how many times I rebuild, I still only get blurry still shots of my patio. It's a 2k camera and should be clear as a bell.

Anybody have any suggestions? I mean legit helpful suggestions! :P

[lindonm]

Yes that's normal, that's normal, that's the proxy advertising their IP's as that - I have the same. Also yes just blurry shots and no video - see the other issue threads, Unify have updated and the current proxy doesn't work with current version of Unify.