Flood

Modern web UI for monitoring and managing your torrent clients

Flood is a sleek, modern web interface for monitoring and managing various torrent clients. Built as a Node.js service, Flood communicates with your favorite torrent client and serves a beautiful, responsive web UI for administration—perfect for users who want a unified dashboard across multiple download clients.

Installation

Install at least one supported torrent client (Deluge, qBittorrent, rTorrent, or Transmission) before Flood — Flood is a monitoring interface and needs a client to connect to.

Install from the Dashboard

Open App Dashboard → Package Management (/dashboard?mode=packages), find Flood in the catalog (browse Download Clients or search), and click Install. The dashboard streams the install log live and Flood appears in your Application Control panel when it finishes. Reinstall and Remove are in the same Package Management panel. To update, use the amber Update badge on the Flood row in the App Dashboard.

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 flood -u username

Directory Layout

Per-User Binary Isolation

QuickBox Pro uses a per-user binary architecture for Flood, providing true isolation between users:

Each user gets their own independent Flood binary in /usr/local/bin/username/. This means:

• Independent Updates: Updating one user’s Flood doesn’t affect other users
• Version Flexibility: Different users can run different Flood versions if needed
• Enhanced Security: Binaries are owned by the respective user, preventing unauthorized modifications
• Service Isolation: systemd services are configured to run user-specific binaries with security sandboxing

Network & Access

Flood runs on an auto-assigned port (default starting at 3001) and is accessible through the nginx reverse proxy:

The first time you access Flood, you’ll be prompted to configure your torrent client connection.

Services

Flood uses a templated systemd unit (flood@.service) for per-user isolation with enhanced security:

# Check status
systemctl status flood@username
 
# View logs
journalctl -u flood@username -f
 
# Restart service
systemctl restart flood@username

Security Hardening

Each Flood service runs with systemd security features enabled:

• NoNewPrivileges: Prevents privilege escalation
• PrivateTmp: Isolated /tmp directory per service
• LimitNOFILE=65536: Increased file descriptor limit for torrent operations
• User-specific binary: Each service runs its own binary from /usr/local/bin/username/flood

Integrations

Configuration

On first access, Flood will prompt you to configure your torrent client connection. Use the QuickBox-specific connection details below for each client.

rTorrent

rTorrent SCGI shim (Flood + ruTorrent)

Shim essentials

• rTorrent real socket: /var/run/username/.rtorrent-real.sock (this is what is set on the .rtorrent.rc file and ruTorrent/nginx)
• Shim socket (use this in Flood): /var/run/username/.rtorrent.sock
• Service: rtorrent-scgi-shim@username
• Also adds the following entries to /home/username/.rtorrent.rc (Removed during uninstall):

## Load & start methods (used by watch directories)
method.insert = "load.start_throw", "simple", "load.raw_start="
method.insert = "load.throw", "simple", "load.raw="
## End load & start methods

Validate & recover

systemctl status rtorrent-scgi-shim@username
ls -l /var/run/username/.rtorrent.sock /var/run/username/.rtorrent-real.sock

• If the shim socket is missing: systemctl restart rtorrent-scgi-shim@username
• If the real socket is missing: systemctl restart rtorrent@username
• Always point Flood and ruTorrent at /var/run/username/.rtorrent.sock

qBittorrent

Deluge

Transmission

Best Practices

Additional Resources