Hello community,

 

I have been trying to wrap my head around this one for a while and am at my wits end. To start:

 

I have successfully routed my SABNZBD  container through my Deluge (VPN) container by following the SpaceInvaderOne videos, as well as some tips and trick I have picked up through researching different articles online. This was done a little over a year ago. 

 

What I believe I did for this outcome:

Downloaded Sab, configured it to work properly without being run through a VPN. Downloaded Deluge, configured it to work properly without any containers running through it.

 

Then on Sab:

 

Left click icon and 'Edit' container and toggle advanced view (top right).
In 'Extra Parameters' enter --net=container:binhex-delugevpn
Go to 'Network Type' and select 'none'.

Click on 'Apply'.

 

Then in Deluge:

 

Left click icon and 'Edit' container and toggle advanced view (top right).
Click on 'Add another Path, Port, Variable, Label or Device' and add in a 'config type' of 'port'.
Enter in the applications Web UI port for 'Container port' from your list taken earlier in step 4.

Edit 'VPN_INPUT_PORTS' env var and put applications Web UI port numbers for the 'Container Port' in the 'value', if multiple ports required then use a comma to separate.

Click on 'Apply'.

 

I didn't have to remove the SAB port from the SAB template, I just added the SAB port to the Deluge VPN_INPUT_PORTS and added another Port variable pointing to Sab, and it worked.

 

After applying these configurations, checking 'curl ifconfig.io' in Sab's terminal (displayed Deluge's IP). WebUI wasn't working, but I could access it by navigating to the host's IP and Sab's configured port. Great. (a weird occurrence, was that Sab would not start directly after these configuration changes. It seems as if Sab needed to wait almost a couple minutes for Deluge to do something in order for Sab to start.) Oh well. after rebooting the server both Deluge and Sab came up within a normal amount of startup time. Both are operational, and Sab traffic is run through Deluge. I'm happy. 

This is where my confusion starts. After trying to go through these same EXACT steps to route another container (binhex-lidarr) through Deluge.. neither SAB or Lidarr will start. Deluge starts no issue with normal operation. But when trying to start either lidarr or sab I get a "no such container" error. I thought to myself, okay wait a few minutes to let Deluge do what it needs to do to allow these containers to start (similar with what I experienced just with Sab after configuring Sab to run through Deluge.) Well after about 10 minutes, the container still would not start.

 

What am I missing here? My end goal is to get my entire ARR setup run through Deluge. Is this even possible? It seems that when I add another container to my Deluge VPN container, everything by Deluge stops working. I will link configs and templates below (these will be pictures of how Sab is configured with Deluge, I removed the Lidarr configs to get things working again). Any help would be much appreciated. 

 

Side-Note **Notice on docker allocations that my Sab port is the same as my Lidarr port. This may be the cause? I went ahead and tried changing my Lidarr port to 8687, but that in turn changed my Sab port to 8687. Is this by design? Or why is my Sab port changing to the port I configure my Lidarr port to?**

Edited April 17, 20251 yr by propaganda_710

This is a picture of my docker allocations when I have configured Lidarr to run through the VPN container (same steps taken when I successfully routed SAB through Deluge). The questions marks next to the container network (container:???) is probably my issue. Any ideas?

 

The easiest way to route dockers through another dockers containers VPN is to simply set the network type to "conatiner" and set the container to the dockerVPN

 

For Sabndbz you should set the following up like this except where I have gluetunvpn, you change your's to DelugeVPN.

 

After that, you have to edit your deluge container template and add the WebGUI ports for Sabnzbd like this:

 

That's it. You're done.

 

It should look like this: (i use qbit but yours will say sabzndb)

 

(you should see 8080 for sab here)

 

Edited April 17, 20251 yr by MowMdown

@MowMdown

Thank you for your reply. I am not on Unraid 7.0 just yet ( I am on 6.12.15 ) so the 'Container' option as the network in the container template is not available. Although, I did figure it out...

Annoyingly enough, I don't think I was waiting long enough for Deluge to make those container connections? I am not sure. I cleared my cache after making the configuration changes to Lidarr and waited about 5 ish minutes. After waiting, I noticed that my docker network changed from 'container:???' to 'container:deluge-vpn.' After I noticed this change, webgui wasn't working but manually typing in the ip address and port did! 

 

After this showed successful, I mirrored that configuration with Radarr, Sonarr, and Prowlarr. Waited about 5 minutes, and all three showed container:deluge-vpn under the docker network column. Curl ifconfig.io was showing Deluge's IP for all containers. All seem to be working. Woohoo! Apparently I wasn't being patient enough. 

 

This sparks another question though. Whenever I decide to upgrade to Unraid 7.0. Is the way I have this configured going to break anything? Being that the new 'container' option in the network portion of the template is now available in 7.0... will the route I went in 6.12.15 be rendered ineffective? I am now afraid to upgrade to 7.0 in fear of breaking everything I just worked out.

 

Thank you for your continued support!