28
Connecting to Jellyfin on a computer thats using VPN
(lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Aug 2023
28 points (96.7% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54390 readers
206 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
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?
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)