arch-qbittorrentvpn VS manual-connections

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.

Nope, those are here but they're clunky as heck

I don't know what to do with these PIA github files. https://github.com/pia-foss/manual-connections

WireGuard is much faster for me. See here for PIA and 3rd party scripts which can be used to create WireGuard config files.

There's a separate API you need to use after the link is up

If you're running a Linux server and want to automate it, PIA's automated connection scripts are here, and this script automatically runs those scripts, grabs the forwarded port and updates the config of your favorite client, then starts it.

I'm a bit partial to doing vpn with foss protocol and clients, without gui applications at all on mac and linux. PIA provides some nice resources to that end on their foss github page.

I set up PIA on my Ubuntu Server (which does not run 24/7) using the official Manual Connections repository, however with WireGuard, the authentication token runs out for me after a few days (since it expires when my server is turned off, then it can't get a new token when it turns back on), is there any way I can prevent this? It was working perfectly before the access token expired :p

https://github.com/pia-foss/manual-connections lists several, including mine

It's a bit of a pain in the butt, but I used the PIA manual connection script to generate a wireguard config file, and then I plugged that into gluetun and now it works great. Was easier than trying to config OpenVPN