To be clear, this is just a joke, and I don’t look down on direct downloading. It absolutely has its place, and sometimes I do it myself if it’s just faster to download a file directly. Torrenting is just so much more convenient, though, especially when using Jackett’s manual search.
I would like to set up an .arr stack that dumps files into my OMV NAS, where Jellyfin can pick them up, but I want the torrent traffic to go through my Proton VPN. Is this a common configuration, or should I be doing something differently?
If you are in the docker ecosystem, this is fantastic https://github.com/haugene/docker-transmission-openvpn
You can configure sonarr and radarr around this so that when the torrents are completed, they are renamed and placed in the nas as well as send a webhook to jellyfin to let it know it has been added (instead of it having to to do a manual search)
Not uncommon. I run wireguard in a docker container for Mullvad and then set my qBittorent container to use the network of the wireguard container. If you do something like this you’ll need to set routing rules on the VPN so the web interface of your torrent client is accessible over your LAN for the *arr stack. The wireguard docs have a decent guide on how to do this, shouldn’t be a problem on OpenVPN either.
Right now I have everything going through Tailscale, it’s just my desktop that goes through Proton when I’m torrenting manually like it’s 2011. Idk, old habits die hard, ig
Yep, that’s what I’m doing (except different NAS). I’ve got the Proton connection at my firewall, but you can use a gluetun container and route your other containers through that as well.
This is excellent to know, thank you.
I think you may have replied to the wrong post? At least you still received an answer, though, lol.
I probably shouldn’t have hijacked, my apologies
No problem.