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.

Solution in the end was to just find a pre-created docker image that handled both I used https://github.com/binhex/arch-delugevpn but there seem to be qbittorrent equivalents out there.

Check it out, read the full page and have another go: https://github.com/binhex/arch-delugevpn

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

Is arch-delugevpn still a popular route to go? Would like to use deluge or qbittorrent if possible.

DSM 7.1.1-42962 Update 3 was auto-installed on my DS220+ last night and today I can't access the web UI for binhex arch-delugevpn.

Seeing how the latest docker image arch-delugevpn doesn't work in DSM 7 (Kernel Too Old Message), what is the last known working version of Arch-Delugevpn that does work in DSM 7?

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.

I'm trying to deploy the markusmcnugen/qbittorrentvpn image but I'm having issues.

- Docker container https://github.com/MarkusMcNugen/docker-qBittorrentvpn

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.

why not use qbittorrentvpn. Auto kill switch, etc. https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/

Hey all, I'm pretty decent with normal networking on routers and switches, etc. but I know very VERY little about iptables. I am trying to fix an issue with a qBittorrent + VPN container. The VPN includes a script setting up a bunch of iptables rules to prevent leaks outside of the VPN. Script is located here: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/blob/focal/qbittorrent/iptables.sh

Been having issues with docker ever since I first tried it, I can't for the life of me access it on the supposedly open ports. Tried setting up this docker for usage in my home plex server with arr services.

I went with the qbittorrentvpn container.

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.