arch-qbittorrentvpn VS arch-sabnzbdvpn

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.

Vpn killswitch Usenet clients: sabnzbd

I use a preconfigured docker, binhex/arch-sabnzbdvpn, if that's an option for you. Really easy to set up. https://github.com/binhex/arch-sabnzbdvpn

Torrents and Usenet downloads are wrapped with a VPN, and I use PIA. If you use something else, you'll want to tweak things as described here. Regardless, even if you use PIA, you need to get the opvn files and add them to the correct directory. The link provided goes into detail. Note that only torrents require port forwarding.