arch-qbittorrentvpn VS docker-qbittorrentvpn

Maybe you could try this one instead: https://github.com/binhex/arch-qbittorrentvpn

I got it to work with OVPN for the time being. I have no idea what I could have done differently with Wireguard though. There is an open issue on github involving Mullvad with Wireguard, maybe its related?

If you're planning on using a new VPN you'll need to update your docker container w/ the new VPN info (account, pass, wireguard/openvpn, etc) and that should do it. I've heard decent things about proton vpn and airvpn but I'm sure there are plenty of acceptable options out there, just not many with decent port-forwarding capabilities if you care about that. airVPN is a good vpn for port-forwarding, binhex's github has a walkthrough for setting up airVPN as an example, shouldn't be much different from how you setup mullvad

I recommend https://github.com/binhex/arch-qbittorrentvpn. Simply because dyonr seemingly abandoned the project in 2022.

Third, better, option: run something like this https://github.com/binhex/arch-qbittorrentvpn

So I'm running Radarr 4.4.4.7068 (docker) and a modified version of qBittorrent which includes a VPN (https://github.com/binhex/arch-qbittorrentvpn). When I add a file via Radarr, qBittorrent complies with the "Maximum Seed Time" selected in Radarr and marks the torrent as "completed". However Radarr doesn't remove it from qBittorent, even if the option "Remove completed" is enabled.

https://github.com/DyonR/docker-qbittorrentvpn is the container I use so I don’t see an easy way to use port forwarding with this method.

I am running this docker image on my raspberry pi (https://github.com/DyonR/docker-qbittorrentvpn) , which runs a qbittorrent over wireguard(client). I have setup a wireguard server on a vps.

Unless he stopped using GitHub idk https://github.com/DyonR/docker-qbittorrentvpn

After changing CIDR I decided to try one more thing. qBittorrentVPN , which previous also didn't work now works like a charm. It doesn't have kill switch hardcoded, so I had manually set them to my new CIDR and my local network. I only worry that other apps from TrueCharts might have hardcoded other CIDR bits witch may be a problem in the future But for now it's victory!

Ummm this sounds naive if you ask me but if you use Hetzner with a torrent client combined with vpn (e.g. https://github.com/DyonR/docker-qbittorrentvpn) you should be good to go. Hetzner isn't bad.

I run this one: https://github.com/DyonR/docker-qbittorrentvpn in my kubernetes cluster. It supports IVPN just fine (at least Wireguard, since I don't use OpenVPN). Once the WG tunnel is active, you should have an interface named "wg0" in the interface list: Tools->Options->Advanced->Network Interface. Select that and QBit will use that interface only (which means it won't communicate if the WG tunnel is down; which is what I want.

Your cheaper option but with some learning involved is to rent a hetzner for example, use swizzin in conjuction with something like a vpn for qbittorrent, some details: How to use a vpn with qbittorent? : qBittorrent (reddit.com) Also I believe there is a docker image, here is one: GitHub - DyonR/docker-qbittorrentvpn: Docker container which runs a qBittorent-nox client with an optional WireGuard or OpenVPN connection Hetzner is in no way public torrent friendly, which is why public trackers must be used only behind a reliable kill-switch vpn option.

The qBit + VPN is a Docker container that uses Wireguard or OpenVPN to route only the qBittorrent traffic through the VPN. It also has a kill switch built in. The project readme can probably explain how it works better than I can

You can request further assistance here: https://github.com/DyonR/docker-qbittorrentvpn/issues