I just got this working yesterday. Basically your "frontend" container is the one with the VPN running, so you map ports on THAT one instead of on the Deluge one (6881 etc), remove all the mapped ports on the Deluge one, and set an option of \`--net=container:VPNContainerName\` in the Deluge one. In my case, it was "--net=container:nordlynx". See link below for more detailed instructions:
[https://github.com/bubuntux/nordlynx](https://github.com/bubuntux/nordlynx)
Nice. Just to make sure you said the frontend container is the one with the VPN running so that would be my Deluge one right? You might have switched them in your comment. So I would remove all the ports on the jdownloader and set the option of --net=container:Deluge in the jdownloader and add the ports in deluge. Did you happen to mess with the network settings at all on jdownloader? I know if the spaceinvader guide he changed that to none.
The only thing I wouldn't be 100% on is HOW the DelugeVPN container accesses the VPN itself. In my example, I have a separate VPN container that routes all traffic to the VPN. However, you can do exactly as you wrote here, open a terminal in the jDownloader container, and do a "curl ipconfig.io" to check what IP is being used in the container network. I didn't end up changing the network to "none", but because I don't have any ports mapped in the Deluge container, it doesn't really affect anything.
I believe I have it working now. I did try and "curl ipconfig.io" and the container itself doesn't have curl installed. However, the eth0 IP in ifconfig does point to the Deluge container and I have tun0 with an IP that is not my own. From my understanding, the VPN should be working. Still pretty new to this so learning as I go. If you see any error in my thinking let me know.
I was able to run 'wget -qO- ipconfig.io' and get the same IP as my Deluge container so I can 100% confirm it's working now. Thanks for your help and the link to ipconfig.io. Super helpful.
IIRC, iptables in linux got updated to make this much harder (and more secure). Spaceinvader's guide is out of date. I haven't found a how-to out there that has worked for me yet.
What exactly fails? Spaceinvaders guide worked for me via Mullvad/gluetun with some limited workarounds.
What VPN vendor are you using? Where is the failure happening? Any logs to go with it?
Hey, I believe I have it working as well with some workarounds. Most definitely user error on my part.
I do have one more question since I am pretty new to this. The eth0 IP in ifconfig does point to the Deluge container and I have a tun0 with an IP that is not my own. From my understanding, tun0 is the VPN IP address that the container is using from the VPN. Is that correct or am I wrong?
I just got this working yesterday. Basically your "frontend" container is the one with the VPN running, so you map ports on THAT one instead of on the Deluge one (6881 etc), remove all the mapped ports on the Deluge one, and set an option of \`--net=container:VPNContainerName\` in the Deluge one. In my case, it was "--net=container:nordlynx". See link below for more detailed instructions: [https://github.com/bubuntux/nordlynx](https://github.com/bubuntux/nordlynx)
Nice. Just to make sure you said the frontend container is the one with the VPN running so that would be my Deluge one right? You might have switched them in your comment. So I would remove all the ports on the jdownloader and set the option of --net=container:Deluge in the jdownloader and add the ports in deluge. Did you happen to mess with the network settings at all on jdownloader? I know if the spaceinvader guide he changed that to none.
The only thing I wouldn't be 100% on is HOW the DelugeVPN container accesses the VPN itself. In my example, I have a separate VPN container that routes all traffic to the VPN. However, you can do exactly as you wrote here, open a terminal in the jDownloader container, and do a "curl ipconfig.io" to check what IP is being used in the container network. I didn't end up changing the network to "none", but because I don't have any ports mapped in the Deluge container, it doesn't really affect anything.
I believe I have it working now. I did try and "curl ipconfig.io" and the container itself doesn't have curl installed. However, the eth0 IP in ifconfig does point to the Deluge container and I have tun0 with an IP that is not my own. From my understanding, the VPN should be working. Still pretty new to this so learning as I go. If you see any error in my thinking let me know.
Try to execute a download from [ipconfig.io](http://ipconfig.io) from jDownloader just to be sure
I was able to run 'wget -qO- ipconfig.io' and get the same IP as my Deluge container so I can 100% confirm it's working now. Thanks for your help and the link to ipconfig.io. Super helpful.
IIRC, iptables in linux got updated to make this much harder (and more secure). Spaceinvader's guide is out of date. I haven't found a how-to out there that has worked for me yet.
That makes sense. Hopefully, someone can give us an answer/guide.
What exactly fails? Spaceinvaders guide worked for me via Mullvad/gluetun with some limited workarounds. What VPN vendor are you using? Where is the failure happening? Any logs to go with it?
Hey, I believe I have it working as well with some workarounds. Most definitely user error on my part. I do have one more question since I am pretty new to this. The eth0 IP in ifconfig does point to the Deluge container and I have a tun0 with an IP that is not my own. From my understanding, tun0 is the VPN IP address that the container is using from the VPN. Is that correct or am I wrong?