arch-delugevpn VS docker-qBittorrentvpn

Basically, I would like that few of my containers to use a proxy whenever they need to access the external world (e.g. Sonarr and its friends). At the moment, for Deluge I am using binhex docker image, an all in one solution for torrent, vpn and so on. Just to add an extra security layer, I would like to obfuscate from my ISP all the calls that the *Arr friends are doing to the usual search engines.

https://github.com/binhex/arch-qbittorrentvpn https://github.com/binhex/arch-delugevpn

Vpn killswitch Torrent clients: rutorrent deluge qbittorrent

Are you wanting to use your VPN for anything other than your torrent traffic? If not, an easier method might just be to grab an container that has VPN+torrent client in one. Like this: https://github.com/binhex/arch-delugevpn

I'm using deluge and works perfectly with VPN -> https://github.com/binhex/arch-delugevpn

I've tried the below, but they all seem to max out the download at 1MBps - binhex/arch-deulgevpn [https://github.com/binhex/arch-delugevpn] - dyonr/qbittorrentvpn [https://hub.docker.com/r/dyonr/qbittorrentvpn/] - markusmcnugen/qbittorrentvpn [https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/]

Have you looked at the discussed issues? Maybe ask there.

I am using PIA as my VPN, and I followed this guide here so I can mask my IP. Since Deluge is using port 8112, I removed that from the script. My container does start up without errors, but when I run a curl for my IP, it shows as my IP which I don't want. I'm having trouble figuring out where I've gone wrong so that my VPN is working properly while using Deluge, and my internet search just keep bringing me to the same guide I followed.

Looking at the Github issues for the container many seem to be in the same situation as you: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/issues There doesn't seem to be any activity from the developer either.

In terms of downloading your "Linux ISO's" automatically, I highly recommend setting up a qbittorent/vpn combo docker container, such as this one. There's also an entire set of programs with docker containers youll see referred to as the "*arr" stack, which help to manage your collection, as well as automatically download your selected media as it becomes available. These are a bit trickier to set up, but once you have everything configured and running, they are a godsend.

Looking around I found that someone raised an issue about this on the project's github page here: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/issues/14 However, the only answer is:

So here's the situation. I have a seedbox at home. It is currently running this docker image: https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/ Which runs qBittorrent and OpenVPN. It's set up so that all of the torrenting traffic goes through the VPN while the rest of my seedbox can be used for other things without having to worry about the VPN. I access this seedbox using the WebUI, which works fine whenever I'm on the local network.

Have Sonarr, Radarr, Sabnzbd, qBittorrent/VPN (NordVPN just for qBittorrent, not on Usenet connections) running in containers on the NAS using Docker Compose. Had OMBI also connected, but has been troublesome as of late for me. Newshosting as my usenet provider, NZBGeek for usenet indexing, Rargb and Nyaa for torrents. Just joined a few private trackers, but those are manually managed and seeding day and night.

qt bittorent (https://github.com/MarkusMcNugen/docker-qBittorrentvpn) - torrent with vpn in a browser. I love that I dont have to devote my box to it or mess with vpn state.

https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/ I just use this one with an openvpn profile

I've tried the below, but they all seem to max out the download at 1MBps - binhex/arch-deulgevpn [https://github.com/binhex/arch-delugevpn] - dyonr/qbittorrentvpn [https://hub.docker.com/r/dyonr/qbittorrentvpn/] - markusmcnugen/qbittorrentvpn [https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/]