I have been torrenting the same primitive way for a long time. Turn on a VPN, open up a browser I only use for this purpose, go to tpb or yts, grab my movie, and shut it all down when the movies over.

I've only updated my torrent client in this time, the method has not evolved.

Now im interested in self hosting jellyfin with an arr stack, with the end goal being to share it with friends and family outside my lan. I'd like to use docker containers so its all containerized, and of course keep it safe and secure.

What kind of set up, from hardware to software, would you recommend to get this going? Any guides in particular? I'm especially iffy on allowing remote access for non-tech savvy family (like a roku app), so any tips/guide recs for that would be helpful.

I've been searching around some and I've found a lot of resources but I'd like to get the opinions of people in here before diving in.

I have some beginner questions, for example: if I have the arr stack running in docker with a vpn, can I browse the internet non-anonymously on that same machine without compromising identifying details, assuming qbittorrent is configured to only move traffic through a VPN? (I'm wondering if I need a dedicated piece of hardware to run everything safely)

Tldr: Suggestions or guides for beginner setting up jellyfin/arr/ remote access for family?

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

[–] GnuLinuxDude@lemmy.ml 2 points 1 day ago

The VM is Debian Linux with a basic XFCE UI (for a system tray + notification widget) via QEMU/KVM which I run through virt-manager. Most unnecessary packages are removed or not installed in the first place. This is so that I can browse the sites, again, in a fool-proof manner. I share a directory from my host OS to the VM, which mounts it on boot in the fstab. This prevents me from downloading into the guest VM's disk image and having to keep dealing with that file getting overly big. In the past I've done a Samba share but recently I've just been using direct shared memory/filesystem and that seems to work OK, too.

As a bonus to this setup, I can use Microsocks in the VM to also proxy a profile in Firefox to get VPN coverage in a specific Firefox profile. I use this when watching on streaming sites instead of trying to watch within the VM, since there is considerable overhead to doing that.

And that's it, really. My VPN killswitches the VM if it ever experiences a connection interruption. And Qbittorrent is set up to use the VPN interface, as well. I use the aforementioned automatic torrents management feature to sort things when they're done downloading.

I should state that there are some obvious downsides to this setup. The first is now I have to overcommit disk space and RAM to keep and run a guest VM. You want enough to be able to run updates and the software in the VM without running into a wall. The second is that there does seem to be a CPU penalty when downloading files (maybe it's because of the way I'm sharing the downloads directory into the VM with virtiofs?)