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 finished-download folder of your Deluge 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 is the folder Deluge puts finished files in: the move-completed folder when Move completed to is enabled in Deluge, otherwise the download folder. In-progress files are not part of the default listing. Change the setting in Deluge and QuickBox re-renders the index on its own, with an hourly check as a safety net (Deluge itself can take a few seconds to write the change to disk). If the folder can’t be served (it is a symlink, it is outside your home folder, /mnt and /media, it doesn’t exist, or the web server can’t read it), the index keeps serving the default folder and the dashboard shows a note beginning “Showing the default folder.” See Open download folder for each note.
• Removing Deluge keeps your finished downloads. qb remove deluge deletes the client’s configuration and data but never the finished-download folder or what is inside it, and the remove output names the folder it kept. Reinstalling writes your download location, move-completed setting and move-completed folder back into the fresh configuration.
• 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

VPN routing

Deluge can route all of its torrent traffic through a VPN tunnel using QuickBox Pro’s app-scoped routing, with either a WireGuard or an OpenVPN backend. When routing is enabled, Deluge downloads, seeds, and announces to trackers from the VPN peer’s exit IP instead of your server’s real IP.

Deluge downloads, seeds, and announces its ratio from the VPN exit IP, and all of that keeps working whatever your provider. Whether other peers can start a connection to you depends on the provider, and the routing card shows a Port forwarding section for it: with ProtonVPN (NAT-PMP) or AirVPN (a port from your account) the dashboard keeps Deluge’s peer port on the provider’s forwarded port; with a provider that forwards none (like NordVPN) your tracker may show you as not connectable, which only means other peers can’t start a connection to you. You may seed to slightly fewer peers, because two peers that are both not connectable can’t reach each other. A provider that forwards a port (ProtonVPN, AirVPN) removes that limit. The section works the same for every torrent client; see qBittorrent routing for the full walkthrough. Port forwarding works with the WireGuard backend. A client routed over OpenVPN works the same way as the NordVPN case above: downloading, seeding and ratio are unaffected.

Deluge is a per-user template service, so several users can each route their own instance independently. Both of its units - the deluged daemon and the deluge-web WebUI - move into one shared VPN namespace together. It appears in the App-Scoped Routing card once Deluge is installed and its service is running.

Your interfaces keep working while routed:

• The WebUI stays reachable at its usual https://yourserver.com/username/deluge/ address through the dashboard proxy.
• Thin clients (the GTK or console UI connecting from off-box) keep reaching Deluge on its daemon port - QuickBox forwards that port into the VPN namespace so remote thin-client connections continue to work.

How to enable VPN routing for Deluge:

1. Go to System > VPN Control (/system/vpn) in the dashboard
2. Upload at least one WireGuard .conf or OpenVPN .ovpn file if you have not done so already
3. Scroll to the App-Scoped Routing card on the VPN Control page
4. Select Deluge from the app list
5. Choose the tunnel backend and a peer configuration from the dropdown
6. Click Enable Routing

Deluge restarts inside its VPN network namespace and its torrent traffic exits through the VPN peer from that point forward.

The default kill-switch stale threshold for Deluge is 30 minutes, matching qBittorrent and the other downloaders. You can adjust it between 60 seconds and 24 hours on the app row inside the App-Scoped Routing card.

For full details on routing configuration, kill switch settings, and live metrics, see the VPN Control dashboard page.

Best Practices

Related Applications

Additional Resources