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?
Can you elaborate on using a socks proxy? I assumed you would get an isp letter if you used one because people always recommended vpns.
Edit: also I don’t want to use tailscale or plex because proprietary. I’m not sure if it’s with mentioning because it looks like plex and plain router port forwarding will work for me.
Headscale is a self hosted version of tailscale, if you’d like to keep it as an option
I remember that there is a FOSS option, I just don’t see the need for it. My main issues are not being able to run my clear web torrents all the time and having duplicate files. I think I just need to spend a five hours typing simple but slightly too complicated to automate commands in the terminal to fix this.
Everyones process is a little different but that sounds unnecessarily complicated. See my other comment about the arrs through docker. You could probably do it all in a single compose file.
Tailscale isn’t necessary, it’s just what I use for remote access. And you can use Jellyfin/Emby/Kodi with Radarr too, it’s not specific to Plex.
SOCKS5 proxy keeps the letters away (I live in NYC). I’ve read that it’s because ISP’s don’t bother actually monitoring torrent traffic. They only act when a copyright holder reports your IP for piracy. So if you hide your IP then they can’t see you.
A proxy is not encrypted, to be clear. But it turns out encryption isn’t actually necessary if you just want your ISP to stop bugging you. If laws change and torrenting becomes more dangerous, I’ll probably switch to a proper VPN. But a proxy is faster and easier.
Not OP, but this is good info. I’m going to be doing something like this over the course of the next few days, and these are good details. Thank you.
NP. I used this guide: https://youtu.be/LD8-Qr3B2-o?si=xneR6WNoEb5ND6xm
Here is an alternative Piped link(s):
https://youtu.be/LD8-Qr3B2-o?si=xneR6WNoEb5ND6xm
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.