Hello people I have a Jellyfin server running on an Ubuntu laptop. But I am also using Mullvad VPN on that laptop for torrenting purposes. Is there a way that I can access the Jellyfin server from another computer in my home network and keep the VPN running at the same time?
Probably if you split tunnel the vpn connection from mullvad to your torrent application and not run the vpn for the entire laptop’s network stack this could be done.
Alternatively, dockerize the entire vpn+torrent (+jellyfin) setup? That way the container gets the vpn but you can still access using your host ip for jellyfin.
Seconding dockerizing the torrent client with a VPN. My approach was using a gluetun container (https://github.com/qdm12/gluetun) and pointing qbittorrent to use that container’s network adapter
I’ve been hearing a lot about it but never tried it, have some experience with docker through uni work but what would be the advantages of using a container for torrents?
The biggest advantage is ease of setup and its recommended by many guides, especially if you are interested in *arr stack (google “servarr wiki” - next level torrenting).
For VPN and torrenting, Id suggest switching to airvpn or any other that supports port forwarding (mullvad got rid of it recently).
If you setup torrent client and VPN using gluetun container, you can hide trafic for torrents only (or whatever services you want). Then you can install wireguard server and use that to connect remotely to your jellyfin. At least I have it like that
Thanks I’ll look into it, also what are the advantages of being able to do port forwarding via VPN?
Also do you know any good tutorials on setting this stuff up as I have limited experience on containers and stuff?
Port forwarding = better connection = more upload. Im no expert, but without PF you cant connect to everyone. Its kinda important for any proper private tracker, but you can use torrents without one. I like mullvad a lot, but airvpn cost even less and have PF, so easy decision to switch.
Yeah servarr wiki. Well starting with containers and setting everything up was a lot of work for me, but deffo worth it. Next level of torrenting/media server, I would never go back.
You basically install docker and docker-compose, then you can install portainer (also docker container) and use it to install everything else in a user friendly gui. You fill your yaml file with all settings for sonarr, radarr, prowlarr, qbittorrent, etc, and just load it in portainer stacks.
Thanks for the answer, I’ll look into setting them up when I get home
I’m planning on doing this personally, as my setup is a bit complex (Protonvpn doesn’t have port forwarding on wireguard supported very well on Linux, so I have some helpers running that make it work). Setting this up each time (and on each computer I want to torrent on) is a bit of a pain. If you do all of your setup and dockerize it, you can just pull the container on each new install/machine (0 setup)
can also look into haugene/docker-transmission-openvpn
it’s transmission that won’t run unless it’s connected to the VPN
That’s a cool kill switch implementation, thanks for the repo. I tested my qbittorrent setup by shutting down the VPN container and it stopped all network connections in the qbit container