You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
qBit Manage keeps a qBittorrent instance tidy: tracker-based tagging, cross-seed handling, orphaned file cleanup, share-limit enforcement, recheck of paused torrents, removal of unregistered ones. Requested in discussion #977.
Single binary:singlefile mode against qbit-manage-linux-$(arch_resolve amd64 arm64) from v4.11.0. No build.
Has a web UI since v4 — QBT_WEB_SERVER=true on port 8181 (QBT_HOST=0.0.0.0, the default binds all interfaces already but is set explicitly). Configuration and run inspection happen there.
The upstream config/config.yml.sample is placed in /opt/qbit-manage_data/config.yml on install; QBT_CONFIG_DIR points at that directory so it survives updates.
Scheduler defaults to QBT_SCHEDULE=1440 (once a day); accepts minutes or a cron expression.
Note: for the cleanup features the container must see the same download paths as qBittorrent, otherwise orphan detection misfires. Flagged as a warning.
Edit /opt/qbit-manage_data/config.yml (the upstream sample is placed there on install) and point the qbt section at your qBittorrent host, port and credentials, then run 'systemctl restart qbit-manage'. Until then the run fails on every schedule tick.
The schedule defaults to once a day (QBT_SCHEDULE=1440 minutes) in /opt/qbit-manage.env. Accepts minutes or a cron expression.
For the cleanup features to work, this container needs to see the same paths as qBittorrent - mount the download directories into it identically, otherwise orphan detection will misfire.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Just ran the script and created a new LXC with no issues. I used the default settings and resources were allocated correctly. I'm able to access the web UI.
Activity
github-actions commentedon Aug 4, 2026
The qBit-Manage script is ready for testing:
Edit /opt/qbit-manage_data/config.yml (the upstream sample is placed there on install) and point the qbt section at your qBittorrent host, port and credentials, then run 'systemctl restart qbit-manage'. Until then the run fails on every schedule tick.
The schedule defaults to once a day (QBT_SCHEDULE=1440 minutes) in /opt/qbit-manage.env. Accepts minutes or a cron expression.
For the cleanup features to work, this container needs to see the same paths as qBittorrent - mount the download directories into it identically, otherwise orphan detection will misfire.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1534079980122804285
tallrals commentedon Sep 8, 2026
Just ran the script and created a new LXC with no issues. I used the default settings and resources were allocated correctly. I'm able to access the web UI.
github-actions commentedon Sep 19, 2026
A PR has been created for qbit-manage: community-scripts/ProxmoxVE#17377
MickLesk commentedon Sep 19, 2026
Merged with #17377 in ProxmoxVE
github-actions commentedon Sep 19, 2026
Files deleted with PR #2303