ontosan

No error anymore! Thank you so much for your time! (not just today, in general!)

Not for me. ghcr.io/binhex/arch-sabnzbdvpn

I get the same error/notification with the VPN version on unraid. Latest update didn't help.

Exactly the nudge I needed, I found the HA docs and the Frigate docs but didn't look for HACS docs. Thanks so much, it works! And to be fair, I did mention I run HA as a docker container in Unraid :-)

Can someone please point this noob in the right direction? I've bought two Tapo c110 cameras and wanted to integrate them into my unraid server. I've setup Frigate through the community applications and got my two cameras working through rtsp. All great. Then I set up mosquitto and tried to link it to Frigate and my Home Assistant docker container for notifications. I did not get this to work. After trying for a while I found out that there's a blueprint for HA. But this blueprint requires a frigate add on in HA installed through HACS. HA on Unraid doesn't have HACS and now I'm stuck. Can someone point me in the right direction?

Since I've done the unRAID stable 7.2.0 update I couldn't connect to this container anymore through tailscale (plugin) while it has worked flawless for months before the update. I've read that I should add the tailscale ip address of my tailnet to the LAN_NETWORK value in the containers settings and I've tried that without luck. I also tried "100.64.0.0/10" for all tailscale IP's and that did seem to work. I did have to make a change to my sabnzbd "external access" settings though. This was set to "API without configuration" and I had to set it to "full webinterface" to get into the webinterface. Seems logical, but strange that it has always worked without these extra steps. My guess is that when I disable Magic DNS in tailscale and add my tailnet's IP again, it'll work. But my question is; What changed in unRAID version 7.2.0 vs 7.1.14 that makes it so much harder to use tailscale with this container? I don't really want to disable Magic DNS since all my bookmarks use it. EDIT: After typing all this I noticed the different IP's of all tailscale devices. I've added these individual IP addresses with the addition of "/32" to the LAN_NETWORK value in the container settings and now it works again. So I guess I can use this solution and keep Magic DNS on.

I'm looking for advice for the following situation: I currently run a 1TB SSD as my cache drive but decided to go with a nvme drive because I need the sata port and because it should make the server run faster. My appdata share was on cache, so I put that on array as secondary and let mover do it's thing. After it was done I noticed there was still 52gb of data left on the cache drive. By this time I remembered that I put the docker.img file (40gb) on the cache drive as well, but as I'm looking at how to get it back to the array I'm a little hesitant since I just had to rebuild my docker.img because of a dumb accident corrupting it. After reading a little, I understand the standard is that the docker.img file is on the system share and you setup mover to put the entire system share on the cache, correct? What I found is that in my docker settings I have this path pointing to the docker.img file: Docker vDisk location: /mnt/cache/system/docker/docker.img While the system share is on "array" only. How do I solve this without having to rebuild the docker.img file again?