qBittorrent Not Downloading: 10 Proven Fixes for Seedbox Users (2026)
qBittorrent is one of the one-click clients you can run on EvoSeedbox alongside our default ruTorrent setup. When torrents stall at 0%, crawl, or throw tracker errors, the cause is almost always one of a handful of things: no seeders, a queue/connection limit, disk exhaustion, or a stale resume file. Work through these ten fixes in order — they go from “most common and instant” to “last resort” — and you’ll clear the vast majority of stuck-download problems without opening a support ticket.
Fix 1: Check If the Torrent Has Seeds
The single most common reason for “not downloading”: nobody is sharing the file. Look at the Seeds column. The format is connected(total) — so 0(0) means zero seeders exist in the swarm, and no client on earth can download from an empty swarm. 0(5) means five seeders exist but you haven’t connected yet (give it a few minutes, or force reannounce — Fix 3). If the total is genuinely 0, the torrent is dead; find a better-seeded copy. On private trackers, a dead torrent may still be reseedable via a re-seed request.
Fix 2: Restart qBittorrent
The simplest fix, and it resolves more than you’d expect. Restart qBittorrent from your seedbox dashboard (click Restart next to the app). This drops stuck peer connections, re-reads the config, and forces fresh tracker announces. If the Web UI itself is unresponsive or timing out, a restart is the right first move before you assume the torrent is the problem.
Fix 3: Force Reannounce to Trackers
Right-click the stuck torrent → Force reannounce. This tells the tracker to send you a fresh peer list immediately instead of waiting for the next scheduled announce interval (often 30 minutes). Useful right after adding a torrent, after a restart, or whenever Seeds shows a total above 0 but you’re connected to none of them. You can also add public trackers to a torrent (right-click → Edit trackers) to widen the peer pool — but never do this on a private-tracker torrent, it will get you banned.
Fix 4: Check Disk Space
qBittorrent pauses downloads the moment it can’t allocate space, and it often does this silently or with a vague error. Check your HDD quota in the seedbox dashboard. Remember qBittorrent may pre-allocate the full torrent size up front, so a 40 GB torrent needs 40 GB free even at 0% downloaded. If you’re near quota, delete completed torrents you’ve already grabbed, or upgrade your plan for more storage.
Fix 5: Disable Download Speed Limits
Go to Tools → Options → Speed. Make sure Global download rate limit is set to 0 (unlimited). The sneaky one here is Alternative speed limits — if the scheduler enabled them, or you toggled the turtle icon in the status bar by accident, your speeds get throttled to the alternate values with no obvious warning. Check both the scheduler settings and the turtle icon at the bottom of the Web UI.
Fix 6: Check Connection Limits
Under Tools → Options → Connection, limits that are set too low will starve your torrents of peers. Sensible seedbox values:
- Global maximum connections: 500
- Maximum connections per torrent: 100
- Global maximum upload slots: 50
- Maximum upload slots per torrent: 10
Because a seedbox sits on a fast, unmetered line, you can run higher connection counts than you would at home. If you have hundreds of torrents loaded, though, don’t push the global maximum into the thousands — you’ll spend CPU on connection churn rather than throughput.
Fix 7: Enable Protocol Encryption
Under Tools → Options → BitTorrent, set Encryption mode to Allow encryption (accepts both encrypted and plain peers — the safe default) or Require encryption (encrypted only). Some peers and networks refuse or filter unencrypted BitTorrent, so Allow maximises the number of peers you can talk to. Require is more private but shrinks your usable peer pool, so only choose it if you specifically need it.
Fix 8: Check the Torrent’s Status
The status column tells you exactly what qBittorrent is doing. Read it before assuming something’s broken:
- Stalled — Connected to the swarm but no peers currently have pieces you need (or none are responding). Usually a seeder problem, not a config problem.
- Checking — Re-verifying file hashes, normal after a restart or a move. Let it finish; it will resume on its own.
- Error: Tracker connection failed / unreachable — Tracker is down, the announce URL is wrong/expired, or (on private trackers) your passkey is stale. Re-download a fresh .torrent from the tracker.
- Queued (dl) — Your active-download limit is reached and this torrent is waiting its turn. Raise Maximum active downloads under Options → BitTorrent → Torrent Queueing, or disable queueing entirely.
Fix 9: Clear the Stuck Torrent’s Resume Data
A corrupted .fastresume file can pin a torrent in a broken state that survives restarts. Stop qBittorrent, SSH into your seedbox, and go to ~/.local/share/qBittorrent/BT_backup/. Each torrent has a matching .torrent and .fastresume pair named by info-hash. Delete only the .fastresume for the stuck torrent (leave the .torrent), then start qBittorrent — it will re-check the data and rebuild resume state. Back up the folder first if you’re unsure, and never delete files while qBittorrent is running.
Fix 10: Reinstall qBittorrent
Last resort, when settings are corrupted beyond a quick fix. Reinstall from your seedbox dashboard. This resets configuration to defaults; your downloaded files remain in your storage. After reinstalling, re-apply the recommended settings below and re-add your torrents. If a reinstall doesn’t fix it, the problem is almost certainly external (dead swarm, tracker outage, or quota) rather than the client.
qBittorrent Recommended Settings for Seedbox
These defaults work well on a seedbox’s fast connection. Adjust encryption and DHT based on whether your tracker is public or private.
| Setting | Recommended value | Why |
|---|---|---|
| Global download rate limit | 0 (unlimited) | Let the seedbox line run at full speed |
| Global upload rate limit | 0 (unlimited) | Maximise ratio on a fast line |
| Max connections (global) | 500 | High peer count without CPU churn |
| Max connections per torrent | 100 | Plenty of peers per swarm |
| Max active downloads | 10 | Avoid too many torrents queued |
| Max active uploads | -1 (unlimited) | Keep seeding everything |
| Max active torrents | 50 | Balance throughput vs. overhead |
| Encryption | Allow encryption | Widest peer compatibility |
| DHT / PeX / LSD | ON for public trackers | Finds more peers on public swarms |
| DHT / PeX / LSD | OFF for private trackers | Required — leaving them on can get you banned |
The DHT/PeX distinction matters most: public trackers benefit from DHT, PeX, and Local Peer Discovery being ON because they help you find peers. Private trackers almost always require them OFF — leaking peers outside the tracker violates their rules and can get your account banned.
Related Guides
- ruTorrent Getting Started — set up EvoSeedbox’s default client
- Why Is My Seedbox Slow? — diagnose speed problems beyond one torrent
- Common Torrent Client Errors — tracker and hash-check error fixes
- Deluge Definitive Guide — if you’d rather run Deluge instead
Frequently Asked Questions
Why does qBittorrent show “downloading” but the speed is 0 KB/s?
You’re connected to the swarm but no connected peer currently has the pieces you need, or the seeders are throttled/offline. This is different from “Stalled.” Try Force reannounce (Fix 3), confirm the Seeds total is above 0, and make sure no speed limit or the turtle icon (Fix 5) is active. If it persists, the swarm simply has no available upload capacity right now.
Is qBittorrent better than ruTorrent on a seedbox?
Neither is strictly “better” — they suit different workflows. ruTorrent is EvoSeedbox’s default and integrates tightly with our dashboard, plugins, and App Doctor monitoring. qBittorrent has a cleaner built-in Web UI and a familiar desktop-style interface many users prefer. Both handle the same torrents; pick the interface you like. See our ruTorrent getting started guide if you want to compare.
Why do my downloads stop as soon as they hit 100%?
That’s expected — the download is finished and the torrent switches to seeding. If it shows “Completed” and stops uploading too, check that you haven’t hit a ratio or seeding-time limit under Options → BitTorrent → Seeding Limits, and that DHT/PeX are configured correctly for your tracker type.
Do I need to configure a listening port on a seedbox?
On EvoSeedbox, qBittorrent is pre-configured with a working listening port when you install it, so you normally don’t touch this. If you migrated a config or changed the port manually and downloads stopped, revert to the assigned port rather than picking a random one — an unreachable port limits you to outgoing connections only, which cripples speeds.
My private-tracker torrent won’t download even though it has seeds. What’s wrong?
Usually a stale passkey or an expired .torrent file. Private trackers embed a personal passkey in the announce URL; if you re-registered, reset your key, or the torrent is old, the tracker rejects your announce. Delete the torrent (keep the data), download a fresh .torrent from the tracker site, and re-add it. Also confirm DHT/PeX/LSD are OFF.
Could my seedbox itself be the problem instead of qBittorrent?
Occasionally. If every torrent across every client is slow — not just one — the bottleneck may be disk, quota, or network rather than qBittorrent settings. Our why is my seedbox slow guide walks through diagnosing that. For client-level error messages specifically, the common torrent client errors guide covers the tracker and hash-check errors you’ll also see in qBittorrent.
Still stuck after all ten fixes? The problem is usually the swarm or a full disk, not your client. If you’re tired of dead torrents and want more storage headroom, EvoSeedbox runs qBittorrent as a one-click app on fast, unmetered servers with App Doctor self-healing monitoring — see our plans starting at $5/mo and spin up qBittorrent in one click.
Head of Operations Evoseedbox
Tim Michels writes and maintains the EvoSeedbox wiki and blog — setup guides and automation tutorials for Plex, the *arr stack, Usenet, and more, backed by hands-on experience running the EvoSeedbox fleet.
