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

Paperless NGX update fails #367

New Issue
Closed
opened 2025-11-20 04:47:29 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 04:47:29 -05:00
Owner
Copy Link

Originally created by @apachelance on GitHub (Jan 16, 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

📝 Provide a clear and concise description of the issue.

The update of Paperless NGX 2.11.2 to 2.14.3 fails. Paperless NGX was installed using the former TTECK helper script (LXC container). After using the update command in the console of the LXC container, the update process starts but ends with an error message, see below. Paperless NGX is not starting anymore.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Use the "update" command of the helper script.

❌ Paste the full error output (if available).

Updating Ghostscript
✔️ Ghostscript updated to 10.04.0
✔️ Stopped all Paperless-ngx Services
Updating to v2.14.3
[ERROR] in line 66: exit code 0: while executing command pip install -r requirements.txt &> /dev/null

🖼️ Additional context (optional).

No response

Originally created by @apachelance on GitHub (Jan 16, 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 ### 📝 Provide a clear and concise description of the issue. The update of Paperless NGX 2.11.2 to 2.14.3 fails. Paperless NGX was installed using the former TTECK helper script (LXC container). After using the update command in the console of the LXC container, the update process starts but ends with an error message, see below. Paperless NGX is not starting anymore. ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Use the "update" command of the helper script. ### ❌ Paste the full error output (if available). Updating Ghostscript ✔️ Ghostscript updated to 10.04.0 ✔️ Stopped all Paperless-ngx Services Updating to v2.14.3 [ERROR] in line 66: exit code 0: while executing command pip install -r requirements.txt &> /dev/null ### 🖼️ Additional context (optional). _No response_
saavagebueno added the not a script issue label 2025-11-20 04:47:29 -05:00
saavagebueno commented 2025-11-20 04:47:30 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 16, 2025):

python issue.

https://github.com/community-scripts/ProxmoxVE/discussions/555

@MickLesk commented on GitHub (Jan 16, 2025): python issue. https://github.com/community-scripts/ProxmoxVE/discussions/555
saavagebueno commented 2025-11-20 04:47:30 -05:00
Author
Owner
Copy Link

@apachelance commented on GitHub (Jan 16, 2025):

Thanks!

@apachelance commented on GitHub (Jan 16, 2025): Thanks!
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 not a script issue
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#367
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?