this post was submitted on 17 Mar 2024
45 points (88.1% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54424 readers
1128 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
Ko-fi Liberapay

founded 1 year ago
MODERATORS
 

Transmission is just giving me more and more problems. Anyone have any recommendations?

you are viewing a single comment's thread
view the rest of the comments
[–] byrona@lemmy.world 5 points 7 months ago (1 children)

I use qbit in a docker container which just provides the web UI but it works great for me

[–] HotChickenFeet@sopuli.xyz 4 points 7 months ago* (last edited 7 months ago) (1 children)

And in this setup you can fairly easily use gluetun to force all its traffic through VPN

[–] Reverendender@sh.itjust.works 2 points 7 months ago (1 children)

So this would allow the rest of my system to not have to use VPN while forcing the torrent client TO use VPN?

[–] HotChickenFeet@sopuli.xyz 2 points 7 months ago

Correct.

With normal split tunneling you can normally do something like this anyways, but it can be finicky to configure, and easy for something like DNS, etc to access the internet without your VPN in the middle. And sometimes if your VPN fails to connect, you could be connecting without your VPN.

By using docker with gluetun + qbit (I believe docker images for this setup exist already) you can force it to use only your VPN, and if the connection fails then your bittorrent client can't connect. With gluetun all your bittorrent traffic would flow through your VPN, but there's a way it can be configured to allow only your webui port to be accessed locally on your network