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 13 Packages Projects Releases 10 Wiki Activity

Update via command line from v2.17.1 to 2.18.4 fails #1652

New Issue
Closed
opened 2026-02-05 01:52:16 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-05 01:52:16 +03:00
Owner
Copy Link

Originally created by @dabepp on GitHub (Sep 22, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Paperless NGX

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

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.0.9/117b893e0e6a4fee (running kernel: 6.14.8-2-pve)

📝 Provide a clear and concise description of the issue.

I did apt-get update and upgrade before. Previous updates over last couple of weeks worked fine.

Server: Paperless-ngx v2.17.1
Update to: Paperless-ngx v2.18.4

Proxmox 9.0.9

SSH: update

🔄 Steps to reproduce the issue.

Go to paperless LVE, ssh, enter "update" and press enter.

❌ Paste the full error output (if available).

✓ Stopped all Paperless-ngx Services

  • Updating to v2.18.4
    [ERROR] in line 93: exit code 0: while executing command pip install -r requirements.txt &> /dev/null

🖼️ Additional context (optional).

No response

Originally created by @dabepp on GitHub (Sep 22, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Paperless NGX ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.0.9/117b893e0e6a4fee (running kernel: 6.14.8-2-pve) ### 📝 Provide a clear and concise description of the issue. I did apt-get update and upgrade before. Previous updates over last couple of weeks worked fine. Server: Paperless-ngx v2.17.1 Update to: Paperless-ngx v2.18.4 Proxmox 9.0.9 SSH: update ### 🔄 Steps to reproduce the issue. Go to paperless LVE, ssh, enter "update" and press enter. ### ❌ Paste the full error output (if available). ✓ Stopped all Paperless-ngx Services - Updating to v2.18.4 [ERROR] in line 93: exit code 0: while executing command pip install -r requirements.txt &> /dev/null ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issue🛑 Failure to comply with the guidelines labels 2026-02-05 01:52:16 +03:00
OVERLORD commented 2026-02-05 01:52:21 +03:00
Author
Owner
Copy Link

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

paperless hasnt pip inside. You call an wrong script with update

@MickLesk commented on GitHub (Sep 22, 2025): paperless hasnt pip inside. You call an wrong script with update
OVERLORD commented 2026-02-05 01:52:25 +03:00
Author
Owner
Copy Link

@dabepp commented on GitHub (Sep 22, 2025):

paperless hasnt pip inside. You call an wrong script with update

Ok. Strange... Can you tell me which command I should use to upgrade the paperless-ngx?

@dabepp commented on GitHub (Sep 22, 2025): > paperless hasnt pip inside. You call an wrong script with update Ok. Strange... Can you tell me which command I should use to upgrade the paperless-ngx?
OVERLORD commented 2026-02-05 01:52:30 +03:00
Author
Owner
Copy Link

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

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

=> check /usr/local/update, i think there is tteck inside

@MickLesk commented on GitHub (Sep 22, 2025): bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/paperless-ngx.sh)" => check /usr/local/update, i think there is tteck inside
OVERLORD commented 2026-02-05 01:52:34 +03:00
Author
Owner
Copy Link

@dabepp commented on GitHub (Sep 22, 2025):

Strange because it used to work the last couple of times. Even the script itself says use "update"...

Image

Running bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/paperless-ngx.sh)" in the container seems to work...

@dabepp commented on GitHub (Sep 22, 2025): Strange because it used to work the last couple of times. Even the script itself says use "update"... <img width="369" height="164" alt="Image" src="https://github.com/user-attachments/assets/13164a34-d2d0-4c7a-903f-127e0aa3815a" /> Running bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/paperless-ngx.sh)" in the container seems to work...
OVERLORD commented 2026-02-05 01:52:37 +03:00
Author
Owner
Copy Link

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

yeah but its an old install from tteck,

https://community-scripts.github.io/ProxmoxVE/scripts?id=update-repo

@MickLesk commented on GitHub (Sep 22, 2025): yeah but its an old install from tteck, https://community-scripts.github.io/ProxmoxVE/scripts?id=update-repo
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 not a script issue 🛑 Failure to comply with the guidelines
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#1652
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?