Decomplicating my setup (sh.itjust.works)

submitted 2 years ago by HumanPerson@sh.itjust.works to c/piracy@lemmy.dbzer0.com

16 comments fedilink hide all child comments

Hi. I am currently pirating on a dedicated server (Debian 12) running i2p, jellyfin, qBittorrent-nox, and a vpn. I tried mullvad for a bit but need to get air VPN set up now. My current setup to actually get content to jellyfin is this:

Try to find it on i2p, if there skip to step 4
SSH into server and turn on vpn + qBittorrent
Torrent Linux ISOs
SSH again and copy the file into jellyfin (really space inefficient, would love a solution to this in particular without shitloads of symlinks.)
Rename files to work with jellyfin
Login to jellyfin and refresh libraries
If Linux ISO not on i2p, cross seed

Obviously this sucks. I know *arr would help, but I don’t know how to set up a VPN to not interfere with jellyfin connections to outside of LAN.

How would you go about automating this? Do you think I am a complete idiot going about it all wrong? (I know I do) Have any of you found a solution to vpns interfering with jellyfin?

you are viewing a single comment's thread
view the rest of the comments

[-] zerodawn@leaf.dance 5 points 2 years ago

The arrs would be your best bet to reduce your input. If i'm not mistaken you can run them all through docker including a version of qbittorrentb that's bound to a vpn and the only way it access the internet is through that vpn. Or you could split tunnel your vpn and bind your qbittorrent to it and bipass your jellyfin instance.