Download Clients
Download clients are the backbone of any automated media setup. QuickBox Pro provides a comprehensive selection of BitTorrent clients, Usenet downloaders, and general download managers—all pre-configured with secure nginx reverse proxies, per-user isolation, and seamless integration with your *arr applications.
BitTorrent Clients
Usenet Clients
General Download Managers
Key Features
🔒 Secure by Default
nginx reverse proxy, per-user isolation, and encrypted passwords
🔗 Seamless Integration
Pre-configured for Sonarr, Radarr, and other *arr applications
📊 Web Interfaces
Access and manage downloads from any device via browser
⚡ Compiled Packages
Optimized builds with latest libtorrent, Qt6, and Boost
👥 Multi-User Support
Each user gets isolated configs, ports, and systemd services
🔄 Easy Updates
Single command updates via qb update without losing settings
Choosing the Right Client
BitTorrent Client Comparison
| Client | Best For | Web UI | Resource Usage | Complexity |
|---|---|---|---|---|
| qBittorrent | All-around use | Built-in | Medium | Low |
| Deluge | Plugin workflows | Built-in | Low | Low |
| Transmission | Beginners | Built-in | Very Low | Very Low |
| rTorrent | Power users | Via ruTorrent/Flood | Low | High |
| ruTorrent | rTorrent users | Yes (PHP) | Low | Medium |
Detailed Recommendations
🎯 qBittorrent
Choose if: You want a feature-rich client with excellent Web UI, integrated search, and RSS support. Best all-around choice.
🔌 Deluge
Choose if: You need plugin extensibility or FlexGet integration. Great for automation workflows.
✨ Transmission
Choose if: You want simplicity and minimal configuration. Perfect for beginners or low-resource systems.
⚡ rTorrent + ruTorrent
Choose if: You're a power user who wants maximum performance and customization with a rich web interface.
Not Sure Which to Choose?
Start with qBittorrent if you’re new to seedboxes—it’s feature-rich, easy to use, and works great with all *arr applications. You can always install additional clients later.
Usenet Client Comparison
| Client | Language | Resource Usage | Best For |
|---|---|---|---|
| SABnzbd | Python | Medium | Feature-rich automation |
| NZBGet | C++ | Very Low | Maximum performance |
Usenet Requirements
Both Usenet clients require a Usenet provider subscription and an indexer to obtain NZB files. Provider credentials are configured after installation.
Common Workflows
📺 Automated Media Downloading
Let *arr applications handle everything automatically:
- Sonarr/Radarr monitors for new releases
- Sends download to your BitTorrent or Usenet client
- Client downloads and notifies *arr when complete
- Sonarr/Radarr imports to your media library
- Media server scans and adds to library
Symptoms
- QuickBox Pro v3 installed and configured
- At least one user account created
- Media management apps installed (Sonarr, Radarr)
Resolution
- Install QuickBox Pro using the official installer
- Create a user with qb adduser
- Install *arr apps before download clients for auto-detection
🔄 Multi-Client Setup
Run multiple clients for different purposes:
- qBittorrent for public trackers and general use
- rTorrent for private trackers (racing/buffer building)
- SABnzbd for Usenet automation
- Flood as unified dashboard for all torrent clients
Port Allocation
QuickBox automatically assigns unique ports to each client and user. No manual port configuration required.
Installation
Quick Installation
Install any download client with a single command:
# BitTorrent clients
qb install qbittorrent -u username
qb install deluge -u username
qb install transmission -u username
qb install rtorrent -u username
qb install rutorrent -u username
qb install flood -u username
# Usenet clients
qb install sabnzbd -u username
qb install nzbget -u username
# General download managers
qb install jdownloader -u username -e 'email@example.com' -p 'password'
qb install pyload -u usernameInstallation Order
For best results, install download clients before configuring *arr applications. The *arr apps will auto-detect installed clients during their setup.
Version Options
Some clients offer version selection:
# Transmission v4 (Qt6) instead of v3
qb install transmission -u username --v4
# rTorrent specific version
qb install rtorrent -u username -o '0.16.2'
# SABnzbd beta
qb install sabnzbd -u username --betaIntegration with *arr Applications
All download clients integrate seamlessly with media management apps:
Connection Settings
| Client | Host | Port/Path | Auth |
|---|---|---|---|
| qBittorrent | 127.0.0.1 | Port in ~/.config/qBittorrent/qBittorrent.conf | Username/Password |
| Deluge | 127.0.0.1 | Port in ~/.config/Deluge/core.conf | Username/Password |
| Transmission | 127.0.0.1 | Port in ~/.config/Transmission/settings.json | Username/Password |
| rTorrent | 127.0.0.1 | URL Path: /username | Username/Password |
| SABnzbd | 127.0.0.1 | Port in ~/.config/SABnzbd/sabnzbd.ini | API Key |
| NZBGet | 127.0.0.1 | Port in ~/.config/NZBGet/nzbget.conf | Username/Password |
rTorrent SCGI Connection
For *arr applications connecting to rTorrent, QuickBox exposes an SCGI endpoint via nginx at /username:
| Setting | Value |
|---|---|
| Host | 127.0.0.1 |
| Port | 443 (or your HTTPS port) |
| URL Path | /username |
| Use SSL | Yes |
| Username | Your QuickBox username |
| Password | Your QuickBox password |
rTorrent SCGI Routing
The nginx scgi.conf routes requests from /username directly to the Unix socket at /var/run/username/.rtorrent.sock. This allows *arr apps to connect via HTTP/HTTPS rather than requiring direct socket access.
Credentials
All clients use your QuickBox username and password by default. API keys (for SABnzbd/NZBGet) are found in the client’s web interface settings.
Best Practices
Do
- Install download clients before configuring *arr applications for auto-detection.
- Use
qb update [client]to keep clients updated safely. - Monitor disk space—downloads can fill storage quickly.
- Configure categories/labels for different *arr applications.
- Use watch folders for manual torrent/NZB additions.
Don't
- Do not install clients from system package managers—use QuickBox only.
- Do not expose client ports directly to the internet without nginx.
- Do not share API keys publicly—they grant full access.
- Do not manually edit systemd or nginx configs without backups.
Troubleshooting
systemctl status [client]@username and view logs with journalctl -u [client]@username -f. Common issues include port conflicts (check with netstat -tlnp) or permission problems on config directories.127.0.0.1 as the host (not localhost). Verify the port in the client's config file. For rTorrent, use the SCGI connection via nginx—set Host to your server, Port to 443, enable SSL, and set XMLRpc Path to /USERNAME. The nginx scgi.conf routes this to the Unix socket automatically.systemctl status nginx. Verify the client service is running. Clear browser cache and try accessing via the correct URL pattern: https://server/[client]/ or https://server/username/[client]/.speedtest-cli. Verify peer connections in the client. For torrents, ensure port forwarding is working (check in client settings). For Usenet, verify SSL connections and try different server addresses from your provider.chown -R username:username /home/username. Check that the download directory exists and has correct permissions. The service runs as your user, so files must be accessible to that user.ls /etc/nginx/software/username.scgi.conf. Check the socket exists: ls -la /var/run/username/.rtorrent.sock. Ensure rTorrent is running: systemctl status rtorrent@username. If the socket is missing, restart rTorrent to recreate it.Related Categories
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.