qBittorrent is a free, open-source BitTorrent client with integrated search, RSS feed subscriptions, sequential downloading, and IP filtering. This guide covers how to install qBittorrent on Ubuntu 26.04, 24.04, and 22.04 using the default repository, the qBittorrent Team PPA, or Flatpak. It also walks through qBittorrent-nox setup for headless servers, including systemd service configuration, Web UI password retrieval, and firewall rules for remote access.
Choose Your qBittorrent Installation Method on Ubuntu
Each method targets a different use case. Review the table below, choose one path, and skip the sections that do not apply.
| Method | Channel | Version | Updates | Best For |
|---|---|---|---|---|
| Ubuntu 26.04 default repository | Ubuntu Universe | 5.1.x | Standard APT updates | Ubuntu 26.04 LTS (no PPA needed, latest version) |
| Flatpak | Flathub | 5.1.x | flatpak update | Sandboxed desktop on any Ubuntu LTS |
| Desktop client via stable PPA | Stable PPA | 4.6.x (24.04), 4.5.x (22.04) | PPA-tracked APT updates | Desktop use on 24.04 or 22.04 |
| Desktop client via unstable PPA | Unstable PPA | Development builds | PPA-tracked APT updates | Testing new features before stable release |
| qBittorrent-nox via stable PPA | Stable PPA | 4.6.x (24.04), 4.5.x (22.04) | PPA-tracked APT updates | Headless servers on 24.04 or 22.04 |
| Ubuntu default repository | Ubuntu Universe | 5.1.x (26.04), 4.6.x (24.04), 4.4.x (22.04) | Standard APT updates | Official packages without third-party PPAs |
Ubuntu 26.04 users should install from the default repository, which already ships version 5.1.x and requires no PPA. The qBittorrent Team PPA builds target 24.04 and 22.04 only; attempting to add the PPA on 26.04 will fail. On 24.04 and 22.04, the stable PPA provides well-tested releases newer than the default repository packages. Choose the unstable PPA only when troubleshooting a specific bug or testing a feature before stable release.
Add the qBittorrent PPA on Ubuntu
Update Your System
Refresh your Ubuntu package lists to ensure all packages are current and avoid conflicts during installation:
sudo apt update
All commands in this guide use
sudo. If your account is not in the sudoers file, follow the guide on adding a user to sudoers on Ubuntu before continuing.
Upgrade any outdated packages:
sudo apt upgrade
For a complete reference on refreshing and upgrading packages, review the Ubuntu package update guide.
Install PPA Prerequisites
The add-apt-repository command requires the software-properties-common package. Most Ubuntu desktop installations include this by default, but minimal server setups may need it:
sudo apt install software-properties-common
Import qBittorrent PPA
Import the qBittorrent Team PPA containing the latest software version. Choose between the stable PPA with well-tested versions or the unstable PPA with the latest features that may not be thoroughly tested.
Unstable builds can introduce bugs or breaking changes since they skip the extended testing cycle of stable releases.
Option 1: Import qBittorrent stable PPA:
sudo add-apt-repository ppa:qbittorrent-team/qbittorrent-stable -y
Option 2: Import qBittorrent unstable PPA:
sudo add-apt-repository ppa:qbittorrent-team/qbittorrent-unstable -y
The -y flag automatically confirms the PPA addition and refreshes the package index, so you can proceed directly to installation.
Install qBittorrent Desktop Client on Ubuntu
Install the qBittorrent desktop client and prepare to launch it for the first time. Ubuntu 26.04 users install directly from the default repository without a PPA. If you plan to run only the Web Interface version on a server, skip ahead to the qBittorrent-nox section.
Install the Desktop Client
Install the qBittorrent desktop client. On Ubuntu 24.04 and 22.04 this pulls from the PPA you added earlier; on Ubuntu 26.04 it uses the default repository:
sudo apt install qbittorrent
Verify the installation by checking the version number:
qbittorrent --version
Output varies by Ubuntu release and installation source:
- Ubuntu 26.04 (default repository):
qBittorrent v5.1.4 - Ubuntu 24.04 (PPA):
qBittorrent v4.6.7 - Ubuntu 22.04 (PPA):
qBittorrent v4.5.5
Launch qBittorrent
Launch the qBittorrent desktop client from the terminal:
qbittorrent
You can also launch qBittorrent from the applications menu:
Activities > Show Applications > qBittorrent

Upon first launch, qBittorrent displays a legal notice. Accept it to reach the main interface.

Install qBittorrent via Flatpak on Ubuntu
Flatpak provides qBittorrent in a sandboxed environment with the latest upstream version. This method works identically on Ubuntu 26.04, 24.04, and 22.04, making it a reliable cross-version option when the PPA is unavailable or you prefer application sandboxing.
Flatpak is not pre-installed on Ubuntu. If you have not set it up yet, install it with
sudo apt install flatpakand restart your session before continuing. For detailed setup including the Flathub repository, follow the Flatpak installation guide for Ubuntu.
Install qBittorrent from Flathub:
flatpak install flathub org.qbittorrent.qBittorrent -y
Verify the installation:
flatpak run org.qbittorrent.qBittorrent --version
Expected output:
qBittorrent v5.1.4
Launch qBittorrent from the applications menu or run flatpak run org.qbittorrent.qBittorrent from the terminal. The Flatpak version receives updates through flatpak update independently of APT.
Install qBittorrent-nox on Ubuntu for Headless Server Use
For server environments, qBittorrent-nox provides a headless alternative that runs on Ubuntu servers without a graphical desktop. The web interface lets you manage torrents remotely through any browser.
Install qBittorrent-nox
Install qBittorrent-nox with the standard APT command:
sudo apt install qbittorrent-nox
Verify the version:
qbittorrent-nox --version
Output varies by Ubuntu release and installation source:
- Ubuntu 26.04 (default repository):
qBittorrent v5.1.4 - Ubuntu 24.04 (default repository):
qBittorrent v4.6.3 - Ubuntu 24.04 (PPA):
qBittorrent v4.6.7 - Ubuntu 22.04 (PPA):
qBittorrent v4.5.5
The install does not start the daemon automatically. Systemd service availability depends on your package source and Ubuntu version:
- Ubuntu 26.04 default repository (version 5.1.4): The templated systemd unit (
qbittorrent-nox@.service) is included. - Ubuntu 24.04 default repository (version 4.6.3): The templated systemd unit is included.
- PPA installations (24.04 or 22.04): The templated systemd unit is included.
- Ubuntu 22.04 default repository (version 4.4.1): No systemd unit is included. You must create one manually (see below).
The Web UI listens on port 8080 by default. The username is admin, and the daemon generates a temporary password on each launch until you save your own credentials.
Choose the Account that Runs qBittorrent-nox
The PPA and Ubuntu 24.04/26.04 default repository packages ship a templated systemd unit (qbittorrent-nox@.service) under /usr/lib/systemd/system/ that runs under whatever username you supply after the @ symbol. Decide whether to run the daemon as your regular login or a dedicated service account so downloaded files stay isolated.
If you prefer a dedicated account, create one with a system user that owns its own home directory:
sudo adduser --system --group --home /var/lib/qbittorrent qbittorrent
The --system flag creates a locked-down user that cannot log in interactively, which keeps the torrent service separate from your daily desktop profile. The explicit --home /var/lib/qbittorrent argument is important: without it, adduser defaults to /nonexistent for system accounts, and the qbittorrent-nox service will fail because it has nowhere to store its configuration. Skip this step entirely if you plan to run the service as your regular username.
Enable the qBittorrent-nox Systemd Service
Enable and start the built-in systemd service with your chosen username. Replace USERNAME with your actual username (run whoami to check), or use the shell substitution shown:
sudo systemctl enable --now qbittorrent-nox@$(whoami)
The
$(whoami)substitution automatically inserts your current username. If you created the dedicatedqbittorrentservice user earlier, replace$(whoami)withqbittorrentinstead.
Verify the service started successfully:
systemctl status qbittorrent-nox@$(whoami)
Expected output for a running service:
● qbittorrent-nox@username.service - qBittorrent-nox service for user username
Loaded: loaded (/usr/lib/systemd/system/qbittorrent-nox@.service; enabled; preset: enabled)
Active: active (running) since Sun 2026-01-19 12:00:00 UTC; 5s ago
Main PID: 1234 (qbittorrent-nox)
Tasks: 10 (limit: 4915)
Memory: 45.2M
CPU: 234ms
CGroup: /system.slice/system-qbittorrent\x2dnox.slice/qbittorrent-nox@username.service
└─1234 /usr/bin/qbittorrent-nox
The qBittorrent package maintains the templated unit, so you only need a custom override file if you plan to change advanced options such as ExecStart flags or custom environment variables.
Create a Systemd Service (Ubuntu 22.04 Only)
Ubuntu 22.04’s default repository ships qBittorrent-nox version 4.4.1, which does not include a systemd service file. The templated unit was added in version 4.5.2-3. If you installed from the default repository on Ubuntu 22.04 without the PPA, create the service file manually.
Create the systemd service file:
sudo tee /etc/systemd/system/qbittorrent-nox@.service <<'EOF'
[Unit]
Description=qBittorrent-nox service for user %i
Documentation=man:qbittorrent-nox(1)
After=network-online.target
[Service]
Type=simple
User=%i
ExecStart=/usr/bin/qbittorrent-nox
Restart=on-failure
RestartSec=5
[Install]
WantedBy=multi-user.target
EOF
Reload the systemd daemon to recognize the new service:
sudo systemctl daemon-reload
Enable and start the service using the same commands as the PPA installation:
sudo systemctl enable --now qbittorrent-nox@$(whoami)
Ubuntu 22.04’s version 4.4.1 predates the temporary password feature introduced in 4.6.1, so the default credentials are
admin/adminadmin. Change these immediately after first login through the Web UI settings.
Access the qBittorrent Web UI and Default Password
With the service running, open the qBittorrent Web UI in your browser. Type the server’s internal IP address followed by the port number (8080), for example, 192.168.55.156:8080. If hosted locally, use the localhost address 127.0.0.1:8080.
For remote access, ensure your firewall allows traffic on port 8080. Ubuntu users running UFW can open the port:
sudo ufw allow 8080/tcp
The Web UI username defaults to admin. Password behavior depends on your qBittorrent version:
- Version 4.6.1 and newer (Ubuntu 26.04, 24.04 default repository, or PPA): A temporary password is generated on each launch.
- Version 4.4.1 (Ubuntu 22.04 default repository): Default credentials are
admin/adminadmin.
Upstream developers removed the legacy admin/adminadmin WebUI credentials starting with qBittorrent 4.6.1. The daemon now generates a random temporary password each time it starts without saved credentials and prints it to stdout once. See the upstream issue #19984, which also documents why you must read this message from the systemd journal in headless deployments.
Check the service logs to retrieve the temporary password. The command pipes the journal output through grep to isolate the password line, and the $(whoami) substitution automatically inserts your current username:
sudo journalctl -u qbittorrent-nox@$(whoami) -n 50 | grep -i "temporary password"
If you created a dedicated
qbittorrentservice user, replace$(whoami)withqbittorrentin all systemd and journalctl commands.
If the password line does not appear, restart the service and follow the log stream in real time:
sudo systemctl restart qbittorrent-nox@$(whoami) && sudo journalctl -fu qbittorrent-nox@$(whoami)
Expect output similar to the following:
******** Information ******** The WebUI administrator username is: admin The WebUI administrator password was not set. A temporary password is provided for this session: VBGK9pUeT You should set your own password in program preferences.
Sign in with username admin and the temporary password that appears in your log. Each restart generates a new temporary password until you store permanent credentials.
Immediately set your own username and password from the Web UI by opening the gear icon (Options) and navigating to Web UI > Authentication.
After saving your credentials, restart the daemon to apply the change:
sudo systemctl restart qbittorrent-nox@$(whoami)
Reopen the Web UI and confirm your new credentials work. The temporary password message will no longer appear after you save permanent credentials.
Manage qBittorrent on Ubuntu: Updates and Removal
Update qBittorrent or qBittorrent-nox
APT provides updates through the PPA or default repository. Refresh the package lists and upgrade all packages:
sudo apt update && sudo apt upgrade
To upgrade only qBittorrent without touching other packages, use the --only-upgrade flag:
sudo apt install --only-upgrade qbittorrent
For qBittorrent-nox installations, substitute qbittorrent-nox in the command above. After updating qBittorrent-nox, restart the service to apply changes:
sudo systemctl restart qbittorrent-nox@$(whoami)
For Flatpak installations, update through the Flatpak toolchain independently of APT:
flatpak update org.qbittorrent.qBittorrent
Remove qBittorrent or qBittorrent-nox
To uninstall qBittorrent completely, first remove the PPA you imported earlier. The remove a PPA on Ubuntu guide covers every cleanup method.
Remove the PPA with the appropriate command:
Remove qBittorrent stable PPA:
sudo add-apt-repository --remove ppa:qbittorrent-team/qbittorrent-stable -y
Remove qBittorrent unstable PPA:
sudo add-apt-repository --remove ppa:qbittorrent-team/qbittorrent-unstable -y
Uninstall qBittorrent and clean up orphaned dependencies:
For desktop installations:
sudo apt remove qbittorrent && sudo apt autoremove
For qBittorrent-nox server installations:
sudo systemctl disable --now qbittorrent-nox@$(whoami)
sudo apt remove qbittorrent-nox && sudo apt autoremove
For Flatpak installations:
flatpak uninstall org.qbittorrent.qBittorrent -y
The Flatpak uninstall does not remove user data. Delete the Flatpak application data directory separately if you want a complete removal:
rm -rf ~/.var/app/org.qbittorrent.qBittorrent
Remove qBittorrent User Data (Optional)
The following commands permanently delete your qBittorrent configuration, download history, and torrent queue. Back up any data you want to keep before proceeding.
To remove all user configuration and data files:
rm -rf ~/.config/qBittorrent
rm -rf ~/.local/share/qBittorrent
Verify the removal completed successfully with the which command:
which qbittorrent qbittorrent-nox
If no output appears, qBittorrent has been fully removed from your system.
Troubleshooting Common qBittorrent Issues on Ubuntu
Service Fails to Start
If the qBittorrent-nox service fails to start, check the logs for specific error messages:
sudo journalctl -xeu qbittorrent-nox@$(whoami) --no-pager | tail -30
A common error message looks like:
qbittorrent-nox: /nonexistent: No such file or directory
This means the user’s home directory doesn’t exist. If you created a system user with the --home flag, verify the directory was created and has correct ownership:
ls -la /var/lib/qbittorrent
PPA Addition Fails on Ubuntu 26.04
If you attempt to add the qBittorrent PPA on Ubuntu 26.04, the command will fail because the PPA does not include packages for this release. The error looks like:
E: The repository 'https://ppa.launchpadcontent.net/qbittorrent-team/qbittorrent-stable/ubuntu resolute Release' does not have a Release file.
Ubuntu 26.04 ships qBittorrent 5.1.x in the default repository, which is newer than the PPA versions available for 22.04 and 24.04. Remove any partially added PPA entries and install from the default repository instead:
sudo add-apt-repository --remove ppa:qbittorrent-team/qbittorrent-stable -y
sudo apt update
sudo apt install qbittorrent
Temporary Password Not Appearing in Logs
If the temporary password line doesn’t appear in the journal output, the service may not have restarted since you last logged in. Restart the service and watch the logs in real time:
sudo systemctl restart qbittorrent-nox@$(whoami) && sudo journalctl -fu qbittorrent-nox@$(whoami)
The temporary password appears only once per restart. After you save permanent credentials through the Web UI, the password message stops appearing.
Web UI Not Accessible
If you cannot reach the Web UI from a remote machine, verify the firewall rule is active and the service is listening:
sudo ufw status | grep 8080
ss -tlnp | grep 8080
Expected output for the firewall check:
8080/tcp ALLOW Anywhere
Expected output showing the service listening:
LISTEN 0 50 *:8080 *:* users:(("qbittorrent-nox",pid=1234,fd=8))
If the port isn’t listening, ensure the service is running with systemctl status qbittorrent-nox@$(whoami).
Useful qBittorrent Links
- qBittorrent Official Website: Features, downloads, and project news.
- qBittorrent GitHub Repository: Source code, issue tracker, and development discussions.
- qBittorrent Wiki: Detailed documentation, configuration guides, and Web UI API reference.
- qBittorrent Forum: Community discussions, support, and announcement archive.
- qBittorrent on Flathub: Flatpak package with the latest upstream release.
- qBittorrent Team on Launchpad: Ubuntu PPA management and package archives.
Frequently Asked Questions about qBittorrent on Ubuntu
Stop the service, delete the qBittorrent.conf file from the configuration directory (typically ~/.config/qBittorrent/ or /var/lib/qbittorrent/.config/qBittorrent/ for dedicated service accounts), then restart the service. On qBittorrent 4.6.1 and newer, the daemon generates a new temporary password printed to the systemd journal. On older versions (4.4.1 on Ubuntu 22.04), the credentials reset to admin/adminadmin.
The desktop client does not start on boot by default. You can add it to your session startup applications through the desktop environment settings. For qBittorrent-nox, running sudo systemctl enable qbittorrent-nox@USERNAME configures the service to start automatically at boot.
The desktop client stores configuration in ~/.config/qBittorrent/ and data in ~/.local/share/qBittorrent/. For qBittorrent-nox running under a dedicated service account, configuration is stored in that account’s home directory, typically /var/lib/qbittorrent/.config/qBittorrent/.
No. The qBittorrent Team PPA does not include packages for Ubuntu 26.04 (resolute). However, Ubuntu 26.04’s default repository ships qBittorrent 5.1.4, which is newer than the PPA versions available for 24.04 and 22.04, so no PPA is needed.
On qBittorrent 4.6.1 and newer (Ubuntu 26.04, 24.04 default repository, or PPA), there is no fixed default password. The daemon generates a random temporary password on each start and prints it once to the systemd journal. Retrieve it with sudo journalctl -u qbittorrent-nox@USERNAME | grep 'temporary password'. On older versions (4.4.1 on Ubuntu 22.04 default repository), the default credentials are admin/adminadmin. Change the password immediately through the Web UI settings.
Conclusion
qBittorrent runs on every supported Ubuntu LTS release through the default repository, the qBittorrent Team PPA, or Flatpak. Ubuntu 26.04 ships version 5.1.x directly, so no PPA is needed. The systemd service and Web UI provide headless server management with firewall-ready remote access on port 8080. For alternative torrent clients on Ubuntu, see the guides on Deluge or KTorrent.
From what I can tell adduser won’t create a home home directory for a system user, which seems logical. Not sure if a bug or intended, but needless to say the service couldn’t start without it.
This was the output I got from “sudo adduser –system –group qbittorrent-nox”:
sudo adduser –system –group qbittorrent-nox
info: Selecting UID from range 100 to 999 …
info: Selecting GID from range 100 to 999 …
info: Adding system user `qbittorrent-nox’ (UID 111) …
info: Adding new group `qbittorrent-nox’ (GID 111) …
info: Adding new user `qbittorrent-nox’ (UID 111) with group `qbittorrent-nox’ …
info: Not creating `/nonexistent’.
After adding the environment for HOME and the path the service started without issues.
Thanks for sharing this, Necro. You’re right that a pure system user created with a non-existent home directory will break the default
qbittorrent-noxsetup, because the service expects to write its config under that user’s home.In the guide I use
sudo adduser --system --group --home /var/lib/qbittorrent qbittorrent, which forces a real home directory at/var/lib/qbittorrentso systemd can start the service cleanly without extra environment tweaks. Your example with/nonexistentmatches what happens if--homeis omitted, so your workaround by settingHOMEfor the unit makes sense in that case.I’ll add a short note to the article to clarify why the explicit
--home /var/lib/qbittorrentpath is important and to avoid commands that create a system user with no usable home directory. Appreciate you flagging the behavior so others don’t run into the same startup issue.The PPA is outdated: qbittorrent-nox v4.5.5 is not supported.
Apparently, AppImage is the new way:
https://www.fosshub.com/qBittorrent.html
Seems the PPA now only supports the qBittorrent desktop app not qBittorrent-nox. Basically, you are installing the version directly from Ubuntu has in its repository.
Thanks for the comment, I will make a note of it in the guide, however qBittorrent desktop latest builds are still supported and would work for anyone else that is curious with this PPA.
The admin/adminadmin credentials do not work.
Thanks for reporting this, Mark. The old
admin/adminadminlogin was removed starting with qBittorrent 4.6.1. The service now generates a random temporary password on each start and prints it to the system logs instead.To find your temporary password, run:
Replace
your-userwith the account running the service (or use$(whoami)if it’s your current user).If nothing shows up, restart the service and follow the log stream:
Look for the line that shows the WebUI administrator username and a one-time password. Sign in with username
adminand that temporary password, then immediately set your own credentials under Tools > Options > Web UI > Authentication. After saving, restart the service again so the new login takes effect.great guide, was able to set up an remote web-ui qBittorrent server with this. Thanks! 🙂