So I’ll start by admitting that I shot myself in the foot a bit by installing nixos (I’m willing to move to any Linux because that’s what I’m familiar with) on what I hope to make my dedicated NAS computer. I have quite a bit of Linux experience doing normal computer things locally, but damned if networking isn’t a completely different ball game and you have to admit the documentation for this stuff can be a little on the obtuse side!

Long story short I’m looking for a solution I can roll out in just a couple hours for setting up a jellyfin with the *arrs and whatever torrent web UI I don’t care, which has sane defaults, will let me easily manage it remotely, and will definitely pipe all torrent activity through my mullvad VPN. I’ve been using qbittorrent because it lets you define a network interface and if the VPN isn’t available it will just stop. I’d like to ensure this always happens because my ISP is very touchy.

I’ve found a docker with the *arrs and jellyfin but it uses PIA for the VPN and I don’t know how to change that, and I also don’t know how to import my existing library because sonarr keeps misidentifying everything when I try. I know nothing about docker and at this point am too pissed off at it to want to learn either (really I just need a video/document that explains what docker is and does and gets to the point you know? I haven’t had much luck)

Also I’ve never been able to get any kind of file server working except sshfs on this network.

I have it so tantalizingly, obnoxiously close to working how I want, there’s just always something that breaks on me and I’m out of mental energy for this project and I’d like something that works. What do you people do?

If this is the wrong place to post this or there exists a better one, I apologize. Or if you do decide to put up with my essentially vent posting I appreciate it!

  • JustEnoughDucks@feddit.nlEnglish
    2·
    11 months ago

    For the VPN issue: Transmission + wireguard or Transmission + OpenVPN containers will do what you need.

    They don’t allow transmission to access the network unless it is through the VPN. You can test by using the torrent magnet at ipleak.net

    For the *arrs, you will have to import all of your existing files manually, assuming they don’t have the standard format like mine didn’t (movie.title.year.encoding-uploader)

    You do not need a vpn on the *arrs and jellyfin. They are not doing anything illegal. However, you should only run jellyfin on your local network or have a router/server-based VPN to log into from the outside. Hosted domains and proxies have a variety of TOS that will generally be violated if you stream jellyfin. The standard containers would be fine.

    If you are only running on your local network anyway, just find someone’s raw docker-compose that is all set up (avoid traefik/ngnix/proxmox unless you want to dive into server management) and learn the 6 lines or so you will have to change to get it set up on your own system like volume paths for your media. Then you can just ‘docker-compose -f path/to/compose.yml up -d’ and everything will be running. Then you need to add the DOCKER IP addresses and API keys to each *arr from transmission in the GUI and they have a test button that will show that it is ok. Done.