Ericjr

Having the issue this morning.

Check the forum, binhex had to make a change to the deluge container and you need to change your sonar/radar to local host. details are in the comments near the end

Much appreciated. Thank you for all of your hard work.

I have deluge up and running with the new version. Sab/Radarr/Sonarr can all communicate and I changed everything to local host and added the additional ports. All good. I run curl they all come out of the VPN. Containers are connected to Deluge with --net=container:Delugevpn. I saw some other posts but no resolution on how to get Radarr/Sonarr to talk to plex for media updates that are not running through a VPN. I would prefer not to have plex run through the VPN. Any advice out there?

Thank you.

I've been reading some conflicting posts that say the dynamix trim plugin is required and others saying that unraid natively supports trim now. Should I be running the dynamix plugin for my SSD cache or is unraid taking care of it? If unraid has support for it natively is there anything I need to do to enable trim support or is it done automatically?

I finally figured it out. It wasnt an issue with my router or docker networking. My issue was with deluge. I added the wireguard lan (10.253.0.0/24) under Container Variable: LAN_NETWORK and it all works now.

I changed the subnet to 255.255.255.0 and insured that use nat was set to off. I’ve read through the threads. I’m not sure where I’m going wrong.

From the posts I saw from others in squids suggestion that was the subnet being used by the people that had it working. I would love to switch to ubiquity but I just dropped my fun money on this build and a pile of hard drives so it’s what I have to work with right now. If you have any ideas please let me know. I can route across networks just fine. It’s only the containers I run through deluge that I can’t access outside the Lan.

Squid, Thank you for the reply. I created a static route in my netgear router but I still am unable to connect to those containers. Screenshot attached of my router configuration. The Unraid machine's ip on the lan is the 10.0.1.20 I think I have everything else right though. I tried checking and unchecking the private box.

I connect to unraid remotely through WireGuard. When I have containers routed through delugevpn to private internet access I can access them on the Lan but not remotely when connecting through WireGuard. It’s only containers that are going through deluge. Any idea on what I need to change to be able to connect to those containers when outside the Lan?

This may or may not need to be in the docker containers section but I might be using wireguard to get this done at the "Settings" level so I'm posting it here. I've run docker containers through the Deluge vpn using Private internet access. They are switching to a new network and the Servers that provide port forwarding have for the most part gone dark except for the Czech server. To keep it short this is my question. Is there any way to connect to private internet access via wireguard and run docker containers through that VPN connection? I know how to do it with servers that support IP forwarding in deluge but those are going away. Any help is greatly appreciated. Thank you.