Deluge

Lightweight BitTorrent client with daemon + web UI, optimized for QuickBox Pro

Deluge is a lightweight, cross-platform BitTorrent client with a powerful daemon (deluged) and web interface (deluge-web). QuickBox Pro installs Deluge from QuickBox compiled packages with a tuned libtorrent/Boost stack, secure nginx reverse proxy, and per-user configuration handled automatically.

Installation

Install from the Dashboard

Open App Dashboard → Package Management (/dashboard?mode=packages), find Deluge in the catalog (browse Download Clients or search), and click Install. The version and its tuned libtorrent/Boost stack are resolved automatically for your distribution — there is nothing to pick. The dashboard streams the install log live and Deluge appears in your Application Control panel when it finishes. Reinstall, Update, and Remove are available from the same panel.

What you see and can manage is gated by your account: admins manage any user’s apps; regular users manage their own. For the full package flow see App Management.

Install from the CLI (automation)

The CLI runs the same install and is suited to automation and scripting:

qb install deluge -u username

Accessing Deluge

After installation, access Deluge at:

https://your-server-ip/username/deluge/

Login credentials:

• Password: Your QuickBox password (authenticates to daemon via hostlist.conf)

Browser Download Index

In addition to the Deluge Web UI, QuickBox installs a per-user browser file index that lists the contents of your Deluge download directory in a dark-themed fancyindex view. Useful for quickly grabbing a single finished file without loading the torrent client.

https://your-server-ip/username.deluge.downloads

• The listing path matches the Deluge download root. Completed files (under download/complete/) and in-progress files (under download/incomplete/) are both visible.
• The index is stitched together per user: if you also have qBittorrent, rTorrent, Transmission, NZBGet, or SABnzbd installed, their completed-download locations are appended into the same username.dlindex.conf so each client gets its own URL. It is one shared browse-index config covering all of that user’s download clients.
• The feature has no service of its own — it is pure nginx. If the page fails to load — returns a 502 or 404, shows blank, or errors — while the rest of the dashboard works normally, the per-user config is broken or missing. Rebuild it with qb fix dlindex -u username (one user) or qb fix dlindex (all users). See the Download Clients overview and the qb fix reference.

Initial Configuration

1. Connect Web UI to Daemon

On first launch, the web UI will prompt you to connect to a daemon:

1. Click Add if no daemon is listed
2. Use these credentials (automatically configured):
   • Hostname: 127.0.0.1
   • Port: Your daemon port (see ~/.config/Deluge/hostlist.conf)
   • Username: Your QuickBox username
   • Password: Your QuickBox password
3. Click Add then Connect

2. Configure Paths and Preferences

Adjust via Preferences → Downloads if needed.

3. Connect to *arr Applications (Optional)

If using Sonarr, Radarr, or other *arr applications:

1. In your *arr app, go to Settings → Download Clients → Add (+)
2. Select Deluge from the list
3. Enter connection details (enable advanced settings to access URL Base):
   • Host: 127.0.0.1 or localhost
   • Port: 443
   • Use SSL: Enabled
   • URL Base: /username/deluge
   • Password: Your QuickBox password
   • Category: Create categories like sonarr, radarr as needed
4. Test and save

Service Management

Deluge uses templated systemd units (deluged@.service, deluge-web@.service) for isolation and security hardening.

# Check status
systemctl status deluged@username
systemctl status deluge-web@username
 
# Restart services
systemctl restart deluged@username
systemctl restart deluge-web@username
 
# View logs
journalctl -u deluged@username -f
journalctl -u deluge-web@username -f
 
# Enable/disable auto-start
systemctl enable deluged@username deluge-web@username
systemctl disable deluged@username deluge-web@username

Troubleshooting

Deluge Won’t Start

journalctl -u deluged@username -f
journalctl -u deluge-web@username -f

Check for port conflicts:

grep -E 'listen_ports|daemon_port' ~/.config/Deluge/core.conf
grep -E 'port' ~/.config/Deluge/web.conf

Web UI Cannot Connect to Daemon

Permission Issues

qb fix permissions -u username
systemctl restart deluged@username deluge-web@username

Configuration Reset

# Backup current configuration
cp -r ~/.config/Deluge ~/.config/Deluge.backup
 
# Stop services
systemctl stop deluge-web@username deluged@username
 
# Remove configuration (will be regenerated)
rm -rf ~/.config/Deluge/*
 
# Reinstall to regenerate configs
qb reinstall deluge -u username

Best Practices

Related Applications

Additional Resources