How to Install qBittorrent on Fedora 44

Fedora already packages both the qBittorrent BitTorrent desktop client and the headless qbittorrent-nox service, so you can install qBittorrent on Fedora without chasing third-party RPM downloads. The desktop build fits Workstation sessions when you want to handle torrents locally, while the Web UI service is better for always-on hosts that you manage from a browser.

Updates stay inside DNF, and cleanup stays simpler because neither build needs a separate repository. The desktop package still needs an active graphical session to launch, while qbittorrent-nox is built for remote management. If you only need a lighter BitTorrent client, install Transmission on Fedora instead.

Install qBittorrent on Fedora

Fedora’s default repositories include both qBittorrent packages, and the upstream qBittorrent download page points Fedora users back to Fedora-managed packages. The main decision is whether you want the desktop client or the headless Web UI service.

Update Fedora System Packages Before Installing qBittorrent

Start from a current package set before installing either build.

sudo dnf upgrade --refresh

These commands use sudo for system changes. If your account is not in the sudoers file yet, follow the guide to add a user to sudoers on Fedora before continuing.

Compare qBittorrent Desktop and qbittorrent-nox

Choose the build that matches where the torrents will run.

Build	Package	Best For	What You Get
qBittorrent Desktop	qbittorrent	Fedora Workstation or any desktop session where you want to manage torrents locally	Qt desktop client, Activities launcher, and the usual qbittorrent command
qbittorrent-nox	qbittorrent-nox	Fedora Server, seedboxes, or remote systems where you want browser-based control	Headless daemon, packaged qbittorrent-nox@.service, and a Web UI on port 8080

Use the desktop package when you sit at the Fedora machine. Use qbittorrent-nox when the box stays online in the background and you want to manage it from another device.

Install qBittorrent Desktop Client

The desktop package is the straightforward choice for local Fedora sessions.

sudo dnf install qbittorrent

Confirm that Fedora registered the package after the install finishes. On Fedora 44, the installed package release currently uses an fc44 suffix.

rpm -q qbittorrent

qbittorrent-5.1.4-2.fc44.x86_64

Install qBittorrent-nox Package

The headless package is the better fit when you plan to manage downloads through the Web UI instead of a local desktop window.

sudo dnf install qbittorrent-nox

Use Fedora’s package database to confirm the installed build before you configure the service. On Fedora 44, the installed package release currently uses an fc44 suffix.

rpm -q qbittorrent-nox

qbittorrent-nox-5.1.4-2.fc44.x86_64

Launch qBittorrent Desktop on Fedora

The desktop package installs the qbittorrent launcher and a Fedora Activities entry named qBittorrent.

qbittorrent

Search for qBittorrent in Activities if you prefer the graphical launcher. The package installs a desktop file named org.qbittorrent.qBittorrent.desktop, but Fedora shows the app simply as qBittorrent.

The first launch opens qBittorrent’s legal notice. Accept it once, then the main window is ready for normal torrent management, RSS feeds, and search plugins.

Configure qBittorrent-nox on Fedora

Fedora ships the packaged qbittorrent-nox@.service template, so the job here is preparing a dedicated service account and bootstrapping the first run cleanly.

Create the qBittorrent-nox Service Account

Create a dedicated system group and a non-interactive service user with /var/lib/qbittorrent as its home directory.

sudo groupadd --system qbittorrent-nox
sudo useradd --system --create-home --home-dir /var/lib/qbittorrent --shell /usr/sbin/nologin -g qbittorrent-nox qbittorrent-nox

Create qBittorrent Download Directory

Fedora writes the qBittorrent service config under /var/lib/qbittorrent/.config/qBittorrent/ after the first start. Create a dedicated download path now so the daemon has a clean service-owned location for completed files.

sudo mkdir -p /var/lib/qbittorrent/downloads
sudo chown -R qbittorrent-nox:qbittorrent-nox /var/lib/qbittorrent

Verify that the service home and download directory belong to the dedicated account before you start the daemon.

sudo ls -ld /var/lib/qbittorrent /var/lib/qbittorrent/downloads

drwx------. 1 qbittorrent-nox qbittorrent-nox 96 May 16 22:04 /var/lib/qbittorrent
drwxr-xr-x. 1 qbittorrent-nox qbittorrent-nox  0 May 16 22:04 /var/lib/qbittorrent/downloads

Accept the qBittorrent Legal Notice

Current Fedora builds support --confirm-legal-notice, so you do not need to sit at an interactive prompt and press y. The timeout 8s wrapper lets qBittorrent write its first-run files, print the temporary Web UI password, and then stop cleanly.

sudo -u qbittorrent-nox timeout 8s /usr/bin/qbittorrent-nox --confirm-legal-notice --webui-port=8080 || test $? -eq 124

Relevant output includes the Web UI address and the one-time temporary password for this session.

WebUI will be started shortly after internal preparations. Please wait...

******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8080
The WebUI administrator username is: admin
The WebUI administrator password was not set. A temporary password is provided for this session: IwBdrEbdY
You should set your own password in program preferences.
Catching signal: SIGTERM
Exiting cleanly

The test $? -eq 124 check accepts the expected timeout exit status after qBittorrent writes its first-run files and receives SIGTERM. A different exit status still surfaces as a failed command.

Start the qBittorrent-nox Systemd Service

Fedora’s packaged unit starts the daemon as the user named after the @ symbol, so the dedicated account you created earlier drops straight into the supported service template.

sudo systemctl enable --now qbittorrent-nox@qbittorrent-nox.service

Use systemd’s enabled and active states as the quick health check before you open the Web UI.

systemctl is-enabled qbittorrent-nox@qbittorrent-nox.service
systemctl is-active qbittorrent-nox@qbittorrent-nox.service

enabled
active

Sign In to the qBittorrent Web UI

Open http://server-ip-address:8080 in a browser only from a trusted network path. The Web UI is an administrative interface, so keep port 8080 private unless you deliberately restrict access with firewall rules or an SSH tunnel.

The journal keeps the current startup password, and this command uses the grep command in Linux with examples to isolate the credential lines before showing the newest username and password pair.

sudo journalctl -u qbittorrent-nox@qbittorrent-nox.service -n 30 --no-pager | grep -Ei "administrator username|temporary password" | tail -n 2

May 16 22:20:34 fedora-44 qbittorrent-nox[44338]: The WebUI administrator username is: admin
May 16 22:20:34 fedora-44 qbittorrent-nox[44338]: The WebUI administrator password was not set. A temporary password is provided for this session: 9ICCr5t3c

Sign in with the username admin and the temporary password from the journal, then store your own credentials under Tools > Options > Web UI > Authentication. The main configuration file for this service-account layout is /var/lib/qbittorrent/.config/qBittorrent/qBittorrent.conf, with runtime data under /var/lib/qbittorrent/.local/share/qBittorrent/. Restart the daemon once you save the new username and password so the hashed credentials reload cleanly.

sudo systemctl restart qbittorrent-nox@qbittorrent-nox.service

Manage qBittorrent on Fedora

Once qBittorrent is in place, regular maintenance is mostly standard DNF work plus a little extra cleanup for the headless service account.

Update qBittorrent on Fedora

DNF updates both qBittorrent packages through the normal Fedora refresh cycle.

sudo dnf upgrade --refresh

When you move to the next Fedora release, use the guide to run the DNF5 system upgrade command on Fedora so qBittorrent and its dependencies move forward together.

Remove qBittorrent Desktop on Fedora

Removing the desktop package is just a normal DNF erase operation.

sudo dnf remove qbittorrent

Check Fedora’s package database afterward instead of relying on the launcher disappearing from Activities.

rpm -q qbittorrent

package qbittorrent is not installed

If you launched the GUI before removing it, search for per-user leftovers first. No output means the desktop profile directories are already gone.

find "$HOME" -maxdepth 3 \( -path "$HOME/.config/qBittorrent" -o -path "$HOME/.local/share/qBittorrent" -o -path "$HOME/.cache/qBittorrent" \)

If the command prints any of those directories and you no longer need the saved desktop profile, remove them with:

This deletes qBittorrent’s per-user settings, cache, saved UI state, and local application data for the current account. Back up anything you want to keep before running the removal command.

rm -rf "$HOME/.config/qBittorrent" "$HOME/.local/share/qBittorrent" "$HOME/.cache/qBittorrent"

Remove qBittorrent-nox on Fedora

Remove the service in stages so systemd stops cleanly before you erase the package and service account.

sudo systemctl disable --now qbittorrent-nox@qbittorrent-nox.service
sudo dnf remove qbittorrent-nox
sudo userdel qbittorrent-nox

Fedora usually removes the matching private group when you delete the user. If the group still exists afterward, remove the leftover group explicitly.

if getent group qbittorrent-nox >/dev/null; then
    sudo groupdel qbittorrent-nox
fi

Deleting /var/lib/qbittorrent removes the service configuration in .config/qBittorrent, runtime data in .local/share/qBittorrent, cache files, GeoIP data, and anything left in downloads. Back up anything you want to keep before you erase that directory.

sudo rm -rf /var/lib/qbittorrent

Verify both the package removal and the service home cleanup before you call the job done.

rpm -q qbittorrent-nox
sudo test ! -e /var/lib/qbittorrent && echo removed

package qbittorrent-nox is not installed
removed

Troubleshoot qBittorrent-nox on Fedora

Most qbittorrent-nox problems on Fedora come down to first-run setup, firewall access, ownership drift, or SELinux labels.

Fix qBittorrent-nox Service Startup Failures

Start with the unit status so you can tell whether qBittorrent failed on its first run or during a later restart.

sudo systemctl status qbittorrent-nox@qbittorrent-nox.service --no-pager -n 20

qbittorrent-nox@qbittorrent-nox.service: Main process exited, code=exited, status=1/FAILURE
qbittorrent-nox@qbittorrent-nox.service: Failed with result 'exit-code'.

If the service never completed the legal notice step, bootstrap it again and then restart the unit.

sudo -u qbittorrent-nox timeout 8s /usr/bin/qbittorrent-nox --confirm-legal-notice --webui-port=8080 || test $? -eq 124
sudo systemctl restart qbittorrent-nox@qbittorrent-nox.service
systemctl is-active qbittorrent-nox@qbittorrent-nox.service

active

Fix Remote qBittorrent Web UI Access on Fedora

Confirm the daemon is listening locally before you change firewall rules.

sudo ss -ltnp | grep ':8080'

LISTEN 0      50                                                   *:8080            *:*    users:(("qbittorrent-nox",pid=44338,fd=38))

If that listener exists, check firewalld before changing access rules. Fedora Workstation normally runs firewalld already and may allow broad high TCP port ranges in its default zone, while minimal installs may need the separate guide to install Firewalld on Fedora first.

Check the zone layout before adding a rule. The examples use Fedora’s default zone; if the interface serving remote browsers belongs to a different active zone, add that --zone=zone-name option to the query, add, verify, and removal commands.

sudo firewall-cmd --get-default-zone
sudo firewall-cmd --get-active-zones

sudo firewall-cmd --query-port=8080/tcp

A response of yes means port 8080 is already covered by a broad zone allowance, such as a Workstation high-port range. A source-restricted rich rule is additive and will not narrow that existing access. Use an SSH tunnel, VPN, stricter zone, or separate firewalld policy if you need firewall-enforced source restriction.

A response of no means there is no broad zone rule for port 8080. If you intentionally want direct LAN access for one trusted subnet, add a source-restricted rich rule. Replace 192.168.1.0/24 with the trusted LAN or VPN subnet that should reach qBittorrent.

sudo firewall-cmd --add-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="8080" protocol="tcp" accept'
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="8080" protocol="tcp" accept'

Verify the runtime and permanent rich rules, then inspect the full zone state so a broader port allowance does not hide beside the source-restricted rule.

sudo firewall-cmd --query-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="8080" protocol="tcp" accept'
sudo firewall-cmd --permanent --query-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="8080" protocol="tcp" accept'

yes
yes

sudo firewall-cmd --list-all
sudo firewall-cmd --permanent --list-all

Remove the same rich rule when the Web UI no longer needs direct LAN access.

sudo firewall-cmd --remove-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="8080" protocol="tcp" accept'
sudo firewall-cmd --permanent --remove-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="8080" protocol="tcp" accept'
sudo firewall-cmd --reload

Re-run the two --query-rich-rule commands afterward when you need cleanup proof. Both should print no after the runtime and permanent rules are gone.

Fix qBittorrent File-Permission Errors

The service account must own both its home directory and the download path.

sudo ls -ld /var/lib/qbittorrent /var/lib/qbittorrent/downloads

drwx------. 1 qbittorrent-nox qbittorrent-nox 96 May 16 22:04 /var/lib/qbittorrent
drwxr-xr-x. 1 qbittorrent-nox qbittorrent-nox  0 May 16 22:04 /var/lib/qbittorrent/downloads

If ownership drifted after a manual copy or restore, reset it and restart the daemon.

sudo chown -R qbittorrent-nox:qbittorrent-nox /var/lib/qbittorrent
sudo systemctl restart qbittorrent-nox@qbittorrent-nox.service

Check SELinux Denials for qBittorrent

Fedora Workstation ships ausearch through the audit package by default, but stripped-down installs may need that package first. Search recent AVC messages before you start changing labels.

sudo ausearch -m avc -ts recent | grep qbittorrent

No output means there were no recent qBittorrent-specific AVC denials. If denials appear after moving or restoring the data tree, reset Fedora’s default labels on that path.

sudo restorecon -Rv /var/lib/qbittorrent

Conclusion

qBittorrent is running on Fedora as either a desktop client or a Web UI service, so you can keep downloads local or move them onto a dedicated host without leaving Fedora’s repositories. If you want a lighter client, install Transmission on Fedora, and if the Web UI needs direct network access, keep the firewall rule limited to trusted source addresses.