SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

qBittorrent update error #824

New Issue
Closed
opened 2025-11-20 04:54:40 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 04:54:40 -05:00
Owner
Copy Link

Originally created by @nunomcm on GitHub (Apr 1, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

qBittorrent

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/qbittorrent.sh)"

📝 Provide a clear and concise description of the issue.

Ran the script to update and got this error:

mv: cannot move '/.config/qBittorrent' to '/root/.config/qBittorrent': Directory not empty

[ERROR] in line 34: exit code 0: while executing command mv /.config/qBittorrent $HOME/.config/

The destination directory had the following files:

categories.json qBittorrent-data.conf qBittorrent.conf rss watched_folders.json

qBittorrent.conf only had the following content:

[BitTorrent]
Session\Port=22118
Session\QueueingSystemEnabled=false

[LegalNotice]
Accepted=true

[Meta]
MigrationVersion=4

[Network]
Cookies=@Invalid()

To be honest I am not sure if these files, which looks default files from a qBittorrent installation, were created by the legacy install script or if was something that I did ages ago for some reason and I don't recall.

Because the script was updated recently I am not sure if it was something that I caused I went ahead and opened this but if you think it was something only on my end, apologies and you can close.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Run update script in a legacy install

❌ Paste the full error output (if available).

mv: cannot move '/.config/qBittorrent' to '/root/.config/qBittorrent': Directory not empty

[ERROR] in line 34: exit code 0: while executing command mv /.config/qBittorrent $HOME/.config/

🖼️ Additional context (optional).

No response

Originally created by @nunomcm on GitHub (Apr 1, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? qBittorrent ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/qbittorrent.sh)" ### 📝 Provide a clear and concise description of the issue. Ran the script to update and got this error: ``` mv: cannot move '/.config/qBittorrent' to '/root/.config/qBittorrent': Directory not empty [ERROR] in line 34: exit code 0: while executing command mv /.config/qBittorrent $HOME/.config/ ``` The destination directory had the following files: `categories.json qBittorrent-data.conf qBittorrent.conf rss watched_folders.json` qBittorrent.conf only had the following content: ``` [BitTorrent] Session\Port=22118 Session\QueueingSystemEnabled=false [LegalNotice] Accepted=true [Meta] MigrationVersion=4 [Network] Cookies=@Invalid() ``` To be honest I am not sure if these files, which looks default files from a qBittorrent installation, were created by the legacy install script or if was something that I did ages ago for some reason and I don't recall. Because the script was updated recently I am not sure if it was something that I caused I went ahead and opened this but if you think it was something only on my end, apologies and you can close. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Run update script in a legacy install ### ❌ Paste the full error output (if available). ``` mv: cannot move '/.config/qBittorrent' to '/root/.config/qBittorrent': Directory not empty [ERROR] in line 34: exit code 0: while executing command mv /.config/qBittorrent $HOME/.config/ ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 04:54:40 -05:00
saavagebueno commented 2025-11-20 04:54:40 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Apr 1, 2025):

port 22118 is definitely not something our script created. actually that whole qBittorrent.conf doesn't look like something our script created.

the fact that you have 2 config directories means you messed with it somehow in the past. our old script installs qbittorrent-nox from debian stable repo, which creates config directory in the root directory, hence /.config directory. The updated qbittorrent version 5.x uses $HOME directory as location for .config folder, hence the $HOME/.config path you pasted above.

if you already have something in $HOME/.config/qBittorrent that means you were messing with something.

move your /root/.config directory somewhere safe and rerun the update script

@tremor021 commented on GitHub (Apr 1, 2025): port 22118 is definitely not something our script created. actually that whole qBittorrent.conf doesn't look like something our script created. the fact that you have 2 config directories means you messed with it somehow in the past. our old script installs qbittorrent-nox from debian stable repo, which creates config directory in the root directory, hence /.config directory. The updated qbittorrent version 5.x uses $HOME directory as location for .config folder, hence the $HOME/.config path you pasted above. if you already have something in $HOME/.config/qBittorrent that means you were messing with something. move your /root/.config directory somewhere safe and rerun the update script
saavagebueno commented 2025-11-20 04:54:41 -05:00
Author
Owner
Copy Link

@nunomcm commented on GitHub (Apr 1, 2025):

The issue was already fixed on my end. I had a inkling that it might have been my doing as I thought the two config directories were strange but this is a old container that I barely use so I wasn't sure.

Apologies.

@nunomcm commented on GitHub (Apr 1, 2025): The issue was already fixed on my end. I had a inkling that it might have been my doing as I thought the two config directories were strange but this is a old container that I barely use so I wasn't sure. Apologies.
saavagebueno commented 2025-11-20 04:54:41 -05:00
Author
Owner
Copy Link

@6RomN6 commented on GitHub (Jun 5, 2025):

@nunomcm how you solved it? Because i have the same problem, the funny thing is first i had the normal config file where everything look good as i closed it without saving and opened it again i was seeing exactly the same file like you. Interessting is that i only can reach the UI per Port 8080 not like in the script per 8090. The funny thing was that i have ssen the 8090 in the config.file i am not able to open anymore... as far i can say i have nothing done than update it... since i update the UI is only reachable per 8080 not 8090

@6RomN6 commented on GitHub (Jun 5, 2025): @nunomcm how you solved it? Because i have the same problem, the funny thing is first i had the normal config file where everything look good as i closed it without saving and opened it again i was seeing exactly the same file like you. Interessting is that i only can reach the UI per Port 8080 not like in the script per 8090. The funny thing was that i have ssen the 8090 in the config.file i am not able to open anymore... as far i can say i have nothing done than update it... since i update the UI is only reachable per 8080 not 8090
saavagebueno commented 2025-11-20 04:54:41 -05:00
Author
Owner
Copy Link

@nunomcm commented on GitHub (Jun 9, 2025):

@6RomN6 Not entirely sure but I think I did the following.

First you need to remove /opt/${APP}_version.txt because the script runs touch /opt/${APP}_version.txt before the move and if the move fails, next time you run the script it will think you already have the updated version. Then you need to check which config file is being used. I can't recall which was in my case but if it is the one in $HOME/.config/qBittorrent, you need to rename the directory so that the script doesn't fail when doing the move command and after the script finishes it, you move the files inside the renamed directory you to $HOME/.config/qBittorrent. If the config file being used is in /.config/qBittorrent, just remove the $HOME/.config/qBittorrent directory, as those files shouldn't be in use, and run the script.

@nunomcm commented on GitHub (Jun 9, 2025): @6RomN6 Not entirely sure but I think I did the following. First you need to remove `/opt/${APP}_version.txt` because the script runs `touch /opt/${APP}_version.txt` before the move and if the move fails, next time you run the script it will think you already have the updated version. Then you need to check which config file is being used. I can't recall which was in my case but if it is the one in `$HOME/.config/qBittorrent`, you need to rename the directory so that the script doesn't fail when doing the move command and after the script finishes it, you move the files inside the renamed directory you to `$HOME/.config/qBittorrent`. If the config file being used is in `/.config/qBittorrent`, just remove the `$HOME/.config/qBittorrent` directory, as those files shouldn't be in use, and run the script.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#824
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?