Use this guide to upgrade an existing Swizzin-managed qBittorrent install from the 4.6 branch to qBittorrent 5.1.4 on a server where the Swizzin upgrade menu supports that target.
Requirements
- A working Swizzin server with qBittorrent already installed.
- Root or sudo access to the server.
- A current server snapshot before changing the qBittorrent build.
- The Swizzin username that owns the qBittorrent service.
Backup First
If your server is a VPS or VM with snapshot support, take a snapshot before upgrading qBittorrent. If you are on bare metal, stop here and confirm you have a tested recovery path, rescue access, and a way to restore the qBittorrent configuration. After that, back up the qBittorrent configuration for the Swizzin user.
USER_NAME="<swizzin-user>"
sudo systemctl stop "qbittorrent@${USER_NAME}"
sudo cp -a
"/home/${USER_NAME}/.config/qBittorrent"
"/home/${USER_NAME}/.config/qBittorrent.backup.$(date +%Y%m%d-%H%M%S)"
sudo systemctl start "qbittorrent@${USER_NAME}"
Record The Current Version
Capture the current qBittorrent and libtorrent versions before upgrading. This makes rollback and comparison easier.
USER_NAME="<swizzin-user>"
date -u
cat /etc/os-release
qbittorrent-nox --version
dpkg-query --show qbittorrent-nox libtorrent-rasterbar 2>/dev/null || true
systemctl status "qbittorrent@${USER_NAME}" --no-pager
journalctl -u "qbittorrent@${USER_NAME}" -n 80 --no-pager
Upgrade Commands
For an interactive upgrade, update Swizzin and start the qBittorrent upgrade. Choose qBittorrent 5.1.4 if it is offered for your operating system.
sudo box update
sudo box upgrade qbittorrent
For an unattended rebuild, set the qBittorrent and libtorrent targets explicitly before running the Swizzin upgrade.
sudo -i
export QBITTORRENT_VERSION=5.1.4
export LIBTORRENT_VERSION=RC_1_2
box upgrade qbittorrent
When the Swizzin upgrade menu asks for the qBittorrent version, select 5.1.4. Confirm the selected branch before the build starts, because choosing the older branch will keep qBittorrent on 4.6.x.
exit
Verify The Service
After the build completes, verify the installed versions, service status, and recent logs. Then open the qBittorrent WebUI through Swizzin and confirm the torrent list loads.
USER_NAME="<swizzin-user>"
qbittorrent-nox --version
dpkg-query --show qbittorrent-nox libtorrent-rasterbar 2>/dev/null || true
systemctl status "qbittorrent@${USER_NAME}" --no-pager
journalctl -u "qbittorrent@${USER_NAME}" -n 120 --no-pager
Rollback
The clean rollback is the server snapshot. If the server is healthy but the new qBittorrent build is not suitable, rebuild the previous version with Swizzin and restore the saved qBittorrent configuration if needed.
sudo -i
export QBITTORRENT_VERSION=4.6.7
export LIBTORRENT_VERSION=RC_1_2
box upgrade qbittorrent
When the Swizzin upgrade menu asks for the qBittorrent version, select 5.1.4. Confirm the selected branch before the build starts, because choosing the older branch will keep qBittorrent on 4.6.x.
exit
Next Step
After qBittorrent 5.1.4 is stable, create a baseline benchmark before changing operating system settings, qBittorrent settings, or libtorrent patch values.