VPN with Docker Deluge Not Working

[JDubs95]

I am new to Deluge and trying to get my VPN working on it so that my other containers can link to it and use it as well.

- I have setup a new OpenMediaVault v7 VM
- I use PIA as my VPN provider.
- I have added a new container in OMV using the latest Deluge via: lscr.io/linuxserver/deluge:latest
- I've spent several hours browsing these forums, reddit, and reading through other forums trying to understand how to configure this container to use my VPN. Below is the best combination of everything I have found, but when I turn on the container and check my torrent ip, it's not running through my VPN. I did read one article where someone said to use SOCKS5 through my PIA, so I logged into PIA and got that setup, then logged into Deluge web ui and turned on the proxy using SOCKS5, entered in the ports and credentials and then checked the torrent ip again. It now shows up as coming from the Netherlands, so that would appear to be working. However, SOCKS5 is still not my VPN and I've read several cautions about not using SOCKS due to possible IP leakage; the VPN is the gold standard or even using SOCKS on top of the VPN. Regardless, I am still back at not knowing how to get the container to connect to my VPN. I am not sure if it's a syntax error or missing lines from my container text file (below), or if the VPN has to be configured within the Deluge web ui...?
- Another interesting note is that when powering on the container, it never creates an openvpn folder within the containers folder, which I had understood should be happening, so that I can drop in whichever ovpn files I want - much like I did with my qbittorrent-vpn container. I do know the VPN works, as I have it running in qbittorren-vpn and from my desired location.

Any additional help, insight or guidance is greatly appreciated! Thanks! JDub's

---
# https://hub.docker.com/r/linuxserver/deluge
services:
deluge:
image: lscr.io/linuxserver/deluge:latest
container_name: delugevpn
cap_add:
- NET_ADMIN
environment:
- PUID=1002
- PGID=100
- TZ=America/New_York
- DELUGE_LOGLEVEL=error #optional
- UMASK=000
- VPN_ENABLED=yes
- VPN_USER=*************
- VPN_PASS=*************
- VPN_PROV=pia
- VPN_CLIENT=openvpn
- STRICT_PORT_FORWARD=yes
- ENABLE_PRIVOXY=yes
- LAN_NETWORK=192.168.1.0/24
- NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
- DELUGE_DAEMON_LOG_LEVEL=info
- DELUGE_WEB_LOG_LEVEL=info
- VPN_INPUT_PORTS=1234
- VPN_OUTPUT_PORTS=5678
- DEBUG=false
volumes:
- /srv/dev-disk-by-uuid-b865bc0d-020d-4ee0-9983-e632a7f44ca4/Configs/delugevpn:/config
- /srv/dev-disk-by-uuid-b865bc0d-020d-4ee0-9983-e632a7f44ca4/Downloads/delugevpn:/downloads
ports:
- 6881:6881
- 6881:6881/udp
- 8112:8112
- 8118:8118
- 9118:9118
- 58846:58846
- 58946:58946
- 58946:58946/udp
restart: unless-stopped

[ambipro]

where did you see that linuxserver's deluge image has VPN capabilities?

https://docs.linuxserver.io/images/docker-deluge/


If you want to use openvpn, you would most likely be meaning to use binhex, or you would need to use a secondary gluetun implementation.

[JDubs95]

I guess I didn't, I just assumed. My buddy is running UNRAID and had a deluge container in docker and had a VPN working with it. Turns out, he was using binhex-delugue. So I had installed the binhex version, spent another 6 hours trying to get the VPN to work with that, but all the same issues as Deluge.

I then ended up discovering a container called gluetun and that did end up working for VPN. The only issue I've found since using gluetun, is that when other container's networking is pointed to the gluetun container (so that my other containers use the vpn setup in gluetun), the containers can't talk to each other. So in my case, all my 'arrs' containers are behind the gluetun's vpn and working. I can still connect to them over my LAN using their ports as well. However, radarr can't talk to prwolarr, sonarr can't talk to prowlarr, and overseerr can't talk to radarr nor sonarr. For whatever reason it works in my buddies UNRAID, but I am using OMV with Docker and it doesn't seem to work.

I did notice in portainer that the gluetun network is 'binded', not setup as 'host', so that was a suggestion from someone as to why maybe they can't talk to each other while behind gluetun, but now we're getting more into gluetun troubleshooting or just general Docker networking issues that fall outside the scope of these deluge forums. Nonetheless it's an interesting topic and started with my journey here in deluge.

[ambipro]

You'd want to have installed binhex-delugevpn.

The environmental variables are well documented on the container's docs, and there is an entire thread on the unraid forums specifically for support for these things, they're probably the ones you'd want to speak to if you decide to revisit the delugevpn container.

[JDubs95]

Yeah, been through all of that in the 6 hours I spent trying to get binhex-delugevpn working, but no dice. Most of those forums (I've found) are people using UNRAID, but I am using OMV and it's definitely not as intuitive/easy as UNRAID. I can't bring myself to do UNRAID though - too cookie cutter; that's probably why I am struggling so I guess I brought this all on myself.

Thanks for the reply's on this thread though! I might come back to this another time and try again.

Have a good week!

[ambipro]

You don't have to use the unraid docker implementation, many users will use compose still even running unraid. It's just slackware with docker and fusefs with a bit of lipstick.

The discussions on unraid's forums for it can easily be translated, they're just environmental variables and volumes and port mappings, it's not different, it's just a UI for docker that translates to a docker run command.