qBittorrent #106

Closed
opened 2025-09-09 19:43:21 -05:00 by giteasync · 18 comments

Originally created by @tremor021 on GitHub.

Originally assigned to: @tremor021 on GitHub.

Name of the Script

qBittorrent

📋 Scritpt Details

Please make a backup of existing LXC !!!

This is a test script to migrate from Debian stable qBittorrent-nox releases to staticaly built binaries from source. Debian people take way too long to include new releases into official repo, so we're decided to switch away from it.

Changes to original update script are:

  1. /opt/qBittorrent_version.txt is missing, we create it to make future updates possible and compatible
  2. We move /.config/qBittorrent directory to $HOME/.config/qBittorrent so your configuration is preserved
  3. We update Exec path in service file to point to the /opt/qbittorrent/qbittorrent-nox binary

This should be enough for painless migration to the static binary build updating mechanism,

Link to test script: bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVED/raw/main/ct/qbittorrent.sh)"

Originally created by @tremor021 on GitHub. Originally assigned to: @tremor021 on GitHub. ### Name of the Script qBittorrent ### 📋 Scritpt Details **Please make a backup of existing LXC !!!** This is a test script to migrate from Debian stable qBittorrent-nox releases to staticaly built binaries from source. Debian people take way too long to include new releases into official repo, so we're decided to switch away from it. Changes to original update script are: 1. `/opt/qBittorrent_version.txt` is missing, we create it to make future updates possible and compatible 2. We move `/.config/qBittorrent` directory to `$HOME/.config/qBittorrent` so your configuration is preserved 3. We update Exec path in service file to point to the `/opt/qbittorrent/qbittorrent-nox` binary This should be enough for painless migration to the static binary build updating mechanism, Link to test script: `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVED/raw/main/ct/qbittorrent.sh)"`
giteasync added the
Ready For Testing
label 2025-09-09 19:43:21 -05:00
Author

@oOStroudyOo commented on GitHub:

Is this not to be used as a new LXC?
Because I've just tried this a new LXC and a couple things I've noticed:

  • The installer doesn't show the IP address, only port number.
  • The LXC is asking for a username and password, even though automatic login is selected.
  • Using default settings (With output) doesn't actually show any Verbose logs.

Image

@oOStroudyOo commented on GitHub: Is this not to be used as a new LXC? Because I've just tried this a new LXC and a couple things I've noticed: - The installer doesn't show the IP address, only port number. - The LXC is asking for a username and password, even though automatic login is selected. - Using default settings (With output) doesn't actually show any Verbose logs. ![Image](https://github.com/user-attachments/assets/90238bbd-b2fd-4799-b0d2-ffe35d09d98d)
Author

@github-actions[bot] commented on GitHub:

The qbittorrent script is ready for testing:
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVED/raw/main/ct/qbittorrent.sh)"
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.

@github-actions[bot] commented on GitHub: The qbittorrent script is ready for testing: ```bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVED/raw/main/ct/qbittorrent.sh)"``` 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.
Author

@oOStroudyOo commented on GitHub:

I also tried a fresh install of qBittorent from the prod branch (v4.5.2) using default settings.

Then using this commend to run the update produces an error:

Image

@oOStroudyOo commented on GitHub: I also tried a fresh install of qBittorent from the prod branch (v4.5.2) using default settings. Then using this commend to run the update produces an error: ![Image](https://github.com/user-attachments/assets/85c4be61-3f1b-4819-b8cb-fb8174aa2a40)
Author

@tremor021 commented on GitHub:

Oops, typo there. Try again in couple of minutes @oOStroudyOo

@tremor021 commented on GitHub: Oops, typo there. Try again in couple of minutes @oOStroudyOo
Author

@tremor021 commented on GitHub:

Is this not to be used as a new LXC? Because I've just tried this a new LXC and a couple things I've noticed:

  • The installer doesn't show the IP address, only port number.
  • The LXC is asking for a username and password, even though automatic login is selected.
  • Using default settings (With output) doesn't actually show any Verbose logs.

Image

No, this is a update script. Its not a install script.

@tremor021 commented on GitHub: > Is this not to be used as a new LXC? Because I've just tried this a new LXC and a couple things I've noticed: > > * The installer doesn't show the IP address, only port number. > * The LXC is asking for a username and password, even though automatic login is selected. > * Using default settings (With output) doesn't actually show any Verbose logs. > > ![Image](https://github.com/user-attachments/assets/90238bbd-b2fd-4799-b0d2-ffe35d09d98d) No, this is a update script. Its not a install script.
Author

@oOStroudyOo commented on GitHub:

Ahh maybe not. Same error on a fresh install:

Image

@oOStroudyOo commented on GitHub: Ahh maybe not. Same error on a fresh install: ![Image](https://github.com/user-attachments/assets/1c5bb277-f2f2-45e6-8b1d-0ae46b6a4bf3)
Author

@oOStroudyOo commented on GitHub:

Oops, typo there. Try again in couple of minutes @oOStroudyOo

Image

Will try this with a fresh install again in case the previous update script broke anything.

@oOStroudyOo commented on GitHub: > Oops, typo there. Try again in couple of minutes [@oOStroudyOo](https://github.com/oOStroudyOo) ![Image](https://github.com/user-attachments/assets/0c3bd162-a2e5-4f63-ad21-22d2f0bf92e3) Will try this with a fresh install again in case the previous update script broke anything.
Author

@oOStroudyOo commented on GitHub:

I'm no programmer but isn't the " in the wrong place?

wget -q "https://github.com/userdocs/qbittorrent-nox-static/releases/download/${FULLRELEASE}/x86_64-qbittorrent-nox -O /opt/qbittorrent/qbittorrent-nox"

Should be?
wget -q "https://github.com/userdocs/qbittorrent-nox-static/releases/download/${FULLRELEASE}/x86_64-qbittorrent-nox" -O /opt/qbittorrent/qbittorrent-nox

@oOStroudyOo commented on GitHub: I'm no programmer but isn't the " in the wrong place? `wget -q "https://github.com/userdocs/qbittorrent-nox-static/releases/download/${FULLRELEASE}/x86_64-qbittorrent-nox -O /opt/qbittorrent/qbittorrent-nox"` Should be? `wget -q "https://github.com/userdocs/qbittorrent-nox-static/releases/download/${FULLRELEASE}/x86_64-qbittorrent-nox" -O /opt/qbittorrent/qbittorrent-nox`
Author

@tremor021 commented on GitHub:

Yea, mighty Copilot at it again. Try now

@tremor021 commented on GitHub: Yea, mighty Copilot at it again. Try now
Author

@oOStroudyOo commented on GitHub:

Still same with a fresh install.

Image

@oOStroudyOo commented on GitHub: Still same with a fresh install. ![Image](https://github.com/user-attachments/assets/3c022b66-24bd-463f-8166-42d69d0c46cd)
Author

@wii747 commented on GitHub:

I have installed the prod qbt then run this update script and its failed

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libdouble-conversion3 libpcre2-16-0 libqt5core5a libqt5dbus5 libqt5network5 libqt5sql5 libqt5sql5-sqlite libqt5xml5
libtorrent-rasterbar2.0 qttranslations5-l10n
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
qbittorrent-nox*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 9,699 kB disk space will be freed.
(Reading database ... 20483 files and directories currently installed.)
Removing qbittorrent-nox (4.5.2-3+deb12u1) ...
Processing triggers for man-db (2.11.2-2) ...
✔️ Stopped Service
⠙ Updating qBittorrent to v5.0.4curl: (3) URL using bad/illegal format or missing URL
curl: option -: is unknown
curl: try 'curl --help' or 'curl --manual' for more information

[ERROR] in line 48: exit code 0 ( ): while executing command curl -fsSL "https://github.com/userdocs/qbittorrent-nox-static/releases/download/${FULLRELEASE}/x86_64-qbittorrent-nox" -O /opt/qbittorrent/qbittorrent-nox

@wii747 commented on GitHub: I have installed the prod qbt then run this update script and its failed Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libdouble-conversion3 libpcre2-16-0 libqt5core5a libqt5dbus5 libqt5network5 libqt5sql5 libqt5sql5-sqlite libqt5xml5 libtorrent-rasterbar2.0 qttranslations5-l10n Use 'apt autoremove' to remove them. The following packages will be REMOVED: qbittorrent-nox* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 9,699 kB disk space will be freed. (Reading database ... 20483 files and directories currently installed.) Removing qbittorrent-nox (4.5.2-3+deb12u1) ... Processing triggers for man-db (2.11.2-2) ... ✔️ Stopped Service ⠙ Updating qBittorrent to v5.0.4curl: (3) URL using bad/illegal format or missing URL curl: option -: is unknown curl: try 'curl --help' or 'curl --manual' for more information [ERROR] in line 48: exit code 0 ( ): while executing command curl -fsSL "https://github.com/userdocs/qbittorrent-nox-static/releases/download/${FULLRELEASE}/x86_64-qbittorrent-nox" -O /opt/qbittorrent/qbittorrent-nox
Author

@tremor021 commented on GitHub:

Sorry, i was really half-assing these updates. My kids are constantly getting me to get up from my laptop.

Should be fixed now, try please

@tremor021 commented on GitHub: Sorry, i was really half-assing these updates. My kids are constantly getting me to get up from my laptop. Should be fixed now, try please
Author

@oOStroudyOo commented on GitHub:

Tried with another fresh install, seems to work.

I've not thoroughly tested it though, my current qBittorrent runs via Docker because it was easier to keep up to date, worked better with the VPN port forwarding, and I use add-on applications such as qBit_Manage.

This will need somebody to do a live bare metal test with real data I guess to see if there's any issues.

Image

@oOStroudyOo commented on GitHub: Tried with another fresh install, seems to work. I've not thoroughly tested it though, my current qBittorrent runs via Docker because it was easier to keep up to date, worked better with the VPN port forwarding, and I use add-on applications such as qBit_Manage. This will need somebody to do a live bare metal test with real data I guess to see if there's any issues. ![Image](https://github.com/user-attachments/assets/75e49672-bf65-4ba6-8150-f37a8e0cb754)
Author

@oOStroudyOo commented on GitHub:

Attempted new install and got following error:

✔️ Installed Dependencies
⠹bash: line 25: RELEASE: unbound variable

[ERROR] in line 25: exit code 0: while executing command RELEASE=$(echo $RELEASE | cut -c 9-13)

The script currently is to migrate existing qbittorrent LXCs to a new repository.

@oOStroudyOo commented on GitHub: > Attempted new install and got following error: > > ✔️ Installed Dependencies > ⠹bash: line 25: RELEASE: unbound variable > ⠸ > [ERROR] in line 25: exit code 0: while executing command RELEASE=$(echo $RELEASE | cut -c 9-13) The script currently is to migrate existing qbittorrent LXCs to a new repository.
Author

@VladTheImpaller commented on GitHub:

Attempted new install and got following error:

✔️ Installed Dependencies
⠹bash: line 25: RELEASE: unbound variable

[ERROR] in line 25: exit code 0: while executing command RELEASE=$(echo $RELEASE | cut -c 9-13)

@VladTheImpaller commented on GitHub: Attempted new install and got following error: ✔️ Installed Dependencies ⠹bash: line 25: RELEASE: unbound variable ⠸ [ERROR] in line 25: exit code 0: while executing command RELEASE=$(echo $RELEASE | cut -c 9-13)
Author

@wii747 commented on GitHub:

@tremor021 the upgrade script now worked

@wii747 commented on GitHub: @tremor021 the upgrade script now worked
Author

@tremor021 commented on GitHub:

Yea, we transitioned from using wget to using curl to fetch files. Can you try again please? @wii747

@tremor021 commented on GitHub: Yea, we transitioned from using wget to using curl to fetch files. Can you try again please? @wii747
Author

@tremor021 commented on GitHub:

Awesome, gonna make it on main repo a bit later today

@tremor021 commented on GitHub: Awesome, gonna make it on main repo a bit later today
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: community-scripts/ProxmoxVED#106
No description provided.