starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

qbitorrent lxc update is broken #1592

New Issue
Closed
opened 2026-02-05 01:42:23 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-05 01:42:23 +03:00
Owner
Copy Link

Originally created by @nautilus7 on GitHub (Sep 7, 2025).

Hi, I am using a qbitorrent lxc with qbittorent version 5.x.x and I have updated serveral times in the past. With the latest changes, this check fails...

54d4d58b15/ct/qbittorrent.sh (L30)

I belive the correct path should be ~/.config/qbitorrent instead.

Originally created by @nautilus7 on GitHub (Sep 7, 2025). Hi, I am using a qbitorrent lxc with qbittorent version 5.x.x and I have updated serveral times in the past. With the latest changes, this check fails... https://github.com/community-scripts/ProxmoxVE/blob/54d4d58b15d0a7b8d79e50d977080ad074ccb282/ct/qbittorrent.sh#L30 I belive the correct path should be `~/.config/qbitorrent` instead.
OVERLORD commented 2026-02-05 01:42:29 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 7, 2025):

The check you pasted has nothing to do with qBittorrent configuration directory. Its to detect if you're using the "new" container or you're having a old install...

@tremor021 commented on GitHub (Sep 7, 2025): The check you pasted has nothing to do with qBittorrent configuration directory. Its to detect if you're using the "new" container or you're having a old install...
OVERLORD commented 2026-02-05 01:42:38 +03:00
Author
Owner
Copy Link

@nautilus7 commented on GitHub (Sep 7, 2025):

Which line of code creates this directory in the "new" install?

@nautilus7 commented on GitHub (Sep 7, 2025): Which line of code creates this directory in the "new" install?
OVERLORD commented 2026-02-05 01:42:40 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 7, 2025):

54d4d58b15/misc/tools.func (L800)

54d4d58b15/misc/tools.func (L1080)

@tremor021 commented on GitHub (Sep 7, 2025): https://github.com/community-scripts/ProxmoxVE/blob/54d4d58b15d0a7b8d79e50d977080ad074ccb282/misc/tools.func#L800 https://github.com/community-scripts/ProxmoxVE/blob/54d4d58b15d0a7b8d79e50d977080ad074ccb282/misc/tools.func#L1080
OVERLORD commented 2026-02-05 01:42:45 +03:00
Author
Owner
Copy Link

@nautilus7 commented on GitHub (Sep 7, 2025):

So, you basically moved the version file to this path/file braking the updates to an absolutely working lxc... Nice.

@nautilus7 commented on GitHub (Sep 7, 2025): So, you basically moved the version file to this path/file braking the updates to an absolutely working lxc... Nice.
OVERLORD commented 2026-02-05 01:42:49 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 7, 2025):

No, we basically moved to a installation method that benefits us and benefits the users in the long run. And updates are not "breaking", they are disabled for old installs. Deploy a new LXC, move your configuration to it and you are set.

Also, cut the smugness. if you want to update it, you can do it all by yourself, manually. Its only couple of bash commands

@tremor021 commented on GitHub (Sep 7, 2025): No, we basically moved to a installation method that benefits us and benefits the users in the long run. And updates are not "breaking", they are disabled for old installs. Deploy a new LXC, move your configuration to it and you are set. Also, cut the smugness. if you want to update it, you can do it all by yourself, manually. Its only couple of bash commands
OVERLORD commented 2026-02-05 01:42:52 +03:00
Author
Owner
Copy Link

@nautilus7 commented on GitHub (Sep 7, 2025):

Broken or disabled... Same thing. Existing lxcs do not update.

I will fix my container like I fixed it when I migrated from the old tteck script. Thank you very much.

Creating a new container every time you decide to do some radical changes is not as easy as you describe. I also have wireguard vpn setup in this container and a systemd mount. It's not just the qbitorrent config you Mr. Smart.

Just wondering whether there is any benefit from using these script after all, apart from having colorful text and icons in the console...

@nautilus7 commented on GitHub (Sep 7, 2025): Broken or disabled... Same thing. Existing lxcs do not update. I will fix my container like I fixed it when I migrated from the old tteck script. Thank you very much. Creating a new container every time you decide to do some radical changes is not as easy as you describe. I also have wireguard vpn setup in this container and a systemd mount. It's not just the qbitorrent config you Mr. Smart. Just wondering whether there is any benefit from using these script after all, apart from having colorful text and icons in the console...
OVERLORD commented 2026-02-05 01:42:56 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 7, 2025):

Fix what? the update script didn't run for you so it didn't do anything...

Also broken and disabled is not the same thing. Broken is error in update script, disabled is intentional feature.
You added, wireguard and other features not set up by our script, so maintaining it is completely on you.

I'm closing this because its pointless to continue

@tremor021 commented on GitHub (Sep 7, 2025): Fix what? the update script didn't run for you so it didn't do anything... Also broken and disabled is not the same thing. Broken is error in update script, disabled is intentional feature. You added, wireguard and other features not set up by our script, so maintaining it is completely on you. I'm closing this because its pointless to continue
OVERLORD commented 2026-02-05 01:42:58 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 7, 2025):

really simple solution...

cat <<EOF >/root/.qbittorrent
0.0.0
EOF

and update

The Container is so old, there was an Bigger Change from v4 to v5, so we decided that we dont migrate manually with code lines
But if this an old 4.x.x Version, it breaks to 5.x.x
If its an 5.x.x the solution above work fine

@MickLesk commented on GitHub (Sep 7, 2025): really simple solution... ```bash cat <<EOF >/root/.qbittorrent 0.0.0 EOF ``` and update The Container is so old, there was an Bigger Change from v4 to v5, so we decided that we dont migrate manually with code lines But if this an old 4.x.x Version, it breaks to 5.x.x If its an 5.x.x the solution above work fine
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1592
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?