Help routing a container through VPN

October 21, 20241 yr

Not sure if this is the right place?

I have qbittorrent-vpn set up usiong protonvpn. I have checked using curl ifconfig that the qbit runs through VPN and everything is working fine.

Now I am trying to set up Sabnzbd using linuxserver repo. I dont wanna use the sabz-vpn-binhex because it will use another slot on my protonvpn. So I am trying to route sabz through my qbit-vpn

Here is what I did:

Installed linuxserver's sabnzbd
It had a port conflict so re-assigned port 8080 to 8087. xxx:8080 runs by qbittorrent
Ran sabnzbd and it ran properly on port 8087. The port mapping App to Host shows 8080 -> 8087
I checked IP for sabnzbd and it showed my REAL IP, so no vpn as expected
Now I changed network type for sabnzbd to none, and added extra parameter as --net=container:binhex-qbittorrentvpn
Restarted sabnzdb and checked IP. Now it shows the correct VPN IP that I was expecting. This is the same IP that qbit shows and the one I used from protonVPN website. So looks like sabnzbd is routing correctly through the VPN.
SO FAR SO GOOD. Now comes the problem I am facing
I want to open the GUI for Sabnzbd, so according to the guides I need to define port mappings in the qbit-vpn container
So I go to qbit and add in port mapping with container port=8080 and host port=8087
But now when I restart both containers, the qbittorrent which earlier ran on xxx:8080, Now on xxx:8080, it opens the sabnzbd page. And if I go to xxx:8087, I get not found error
I even added 8087 in the VPN INPUT AND OUTPUT PORT in qbit container, but that didnt help.
Not sure what I am doing wrong, so anyone can help?
I even tried using the network set as qbittorrent network and removing the extra parameters. Same thing. :8080 opens my sabnzbd instead of qbittorrent