qBitTorrent
this post was submitted on 17 Mar 2024
46 points (88.3% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54819 readers
326 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 2 years ago
MODERATORS
I use qBittorrent everywhere. It's really good.
I'm running qBittorrent on my Plex server which runs MacOS. It's been reliable for me.
I gave qbittorrent a whirl. It's dynamite. Blows Transmission out of the water.
Try deluge, it’s been pretty bulletproof for me once configured.
Deluge?
I use qbit in a docker container which just provides the web UI but it works great for me
And in this setup you can fairly easily use gluetun to force all its traffic through VPN
So this would allow the rest of my system to not have to use VPN while forcing the torrent client TO use VPN?
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
Honestly, what i do is install docker using brew and spin up a saltbox instance on localhost. You can always bring it down by telling docker to stop but it's way better and it's containerized.
edit: let me know if you need help.
I know some of those words!
Lol whatcha need help with?
I use qbittorrent or/and aria2 everywhere
I've never head a single problem with Transmission on Sonoma, check your system.
I've been using it since Tomato died. Transmission chokes on torrents with lots of trackers that fail to connect. If you go in and remove them, its performance and responsive improves greatly.
Outside of those small things, it's solid and a universal app.
Huh.
I regularly manually add this list of trackers to torrents, I'd say most of my torrents have 120+ trackers in their list. Never noticed any issues.
The only issue I ever noticed is that sometimes the layout of the filter bar breaks, but you can fix it by just disabling/renabling the filters, so just a cosmetic issue that can be fixed with a double click.
The download page for qbittorrent says that MacOS is "barely supported". Is docker reasonably accessible for Mac? You could use that to get qbittorrent.
Just try it. If "barely suppoted" gets you the current stability, them kudos to the devs. I haven't had a single crash in recent years. Sure Transmission has a nicer minimalistic UI, but it lacks a lot of qbittorrent's features.
I have never tried this one because of that lack of support
Transmission :P
If you're having issues with Transmission most likely the problem is in another thing... like an hard drive or some other piece of software.
Nah, Transmission just gets kinda buggy when its loaded with hundreds of torrents. Its fine for light use (or perhaps if you have a ton of RAM). But it definitely gets laggy and occasionally unresponsive after running a few days.
Tell me something, what's the state of those torrents?
Seeding
This might be caused by your I/O reaching the limits while doing random reads. Reducing the amount of peers you connect to may fix the problem.
Deluge never let me down