starred/ProxmoxVE-Local
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE-Local.git synced 2026-04-24 20:25:50 +03:00
Code Issues 19 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #442] Update 0.5.3 to 0.5.4 fail #132

New issue
Open
opened 2026-02-26 12:40:16 +03:00 by kerem · 10 comments
kerem commented 2026-02-26 12:40:16 +03:00
Owner
Copy link

Originally created by @rbalaev on GitHub (Jan 13, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE-Local/issues/442

✅ Have you read and understood the above guidelines?

yes

📝 Provide a clear and concise description of the issue.

Image Image

🔄 Steps to reproduce the issue.

the problem persists

❌ Paste the full error output (if available).

[2026-01-13 19:53:14] Starting ProxmoxVE-Local update process...
[2026-01-13 19:53:14] Log file: /tmp/update.log
[2026-01-13 19:53:14] Detected running from application directory
[2026-01-13 19:53:14] Starting ProxmoxVE-Local update process...
[2026-01-13 19:53:14] Log file: /tmp/update.log
[2026-01-13 19:53:14] Running as detached process
[2026-01-13 19:53:17] Checking dependencies...
[SUCCESS] All dependencies are available
[WARNING] No GitHub token found. Using unauthenticated requests (lower rate limits)
[WARNING] To use a token, add GITHUB_TOKEN=your_token to .env file or set GITHUB_TOKEN environment variable
[2026-01-13 19:53:17] Fetching latest release information from GitHub...
[2026-01-13 19:53:17] Using unauthenticated GitHub API request (lower rate limits)
[SUCCESS] Latest release: v0.5.4 (published: 2026-01-13T16:05:35Z)
[2026-01-13 19:53:17] Creating backup directory at /tmp/pve-scripts-backup-20260113-195314...
[2026-01-13 19:53:17] Backing up data directory...
[SUCCESS] Data directory backed up successfully
[2026-01-13 19:53:17] Backing up .env file...
[SUCCESS] .env file backed up successfully
[2026-01-13 19:53:17] Backing up scripts/ct directory...
[SUCCESS] scripts/ct directory backed up successfully
[2026-01-13 19:53:17] Backing up scripts/install directory...
[SUCCESS] scripts/install directory backed up successfully
[WARNING] scripts/tools directory not found, skipping backup
[WARNING] scripts/vm directory not found, skipping backup
[2026-01-13 19:53:17] Working from application directory: /opt/ProxmoxVE-Local
[2026-01-13 19:53:17] Disabling systemd service temporarily to prevent auto-restart...
[SUCCESS] Service disabled successfully
[2026-01-13 19:53:17] Killing any remaining npm/node processes...
[2026-01-13 19:53:17] No running processes found
[2026-01-13 19:53:17] Detected Node.js version: 24.12.0
[SUCCESS] Node.js 24 already installed
[2026-01-13 19:53:17] Preparing Node.js 24 upgrade…
[2026-01-13 19:53:19] Installing Node.js 24…
[ERROR] Failed to install Node.js 24

🖼️ Additional context (optional).

No response

Originally created by @rbalaev on GitHub (Jan 13, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE-Local/issues/442 ### ✅ Have you read and understood the above guidelines? yes ### 📝 Provide a clear and concise description of the issue. <img width="1118" height="1102" alt="Image" src="https://github.com/user-attachments/assets/79904b4a-2e0a-4e39-b03a-30fd6eb043cf" /> <img width="852" height="642" alt="Image" src="https://github.com/user-attachments/assets/92a832e1-2acf-45c1-ba5c-1fcf74dd95e5" /> ### 🔄 Steps to reproduce the issue. the problem persists ### ❌ Paste the full error output (if available). [2026-01-13 19:53:14] Starting ProxmoxVE-Local update process... [2026-01-13 19:53:14] Log file: /tmp/update.log [2026-01-13 19:53:14] Detected running from application directory [2026-01-13 19:53:14] Starting ProxmoxVE-Local update process... [2026-01-13 19:53:14] Log file: /tmp/update.log [2026-01-13 19:53:14] Running as detached process [2026-01-13 19:53:17] Checking dependencies... [SUCCESS] All dependencies are available [WARNING] No GitHub token found. Using unauthenticated requests (lower rate limits) [WARNING] To use a token, add GITHUB_TOKEN=your_token to .env file or set GITHUB_TOKEN environment variable [2026-01-13 19:53:17] Fetching latest release information from GitHub... [2026-01-13 19:53:17] Using unauthenticated GitHub API request (lower rate limits) [SUCCESS] Latest release: v0.5.4 (published: 2026-01-13T16:05:35Z) [2026-01-13 19:53:17] Creating backup directory at /tmp/pve-scripts-backup-20260113-195314... [2026-01-13 19:53:17] Backing up data directory... [SUCCESS] Data directory backed up successfully [2026-01-13 19:53:17] Backing up .env file... [SUCCESS] .env file backed up successfully [2026-01-13 19:53:17] Backing up scripts/ct directory... [SUCCESS] scripts/ct directory backed up successfully [2026-01-13 19:53:17] Backing up scripts/install directory... [SUCCESS] scripts/install directory backed up successfully [WARNING] scripts/tools directory not found, skipping backup [WARNING] scripts/vm directory not found, skipping backup [2026-01-13 19:53:17] Working from application directory: /opt/ProxmoxVE-Local [2026-01-13 19:53:17] Disabling systemd service temporarily to prevent auto-restart... [SUCCESS] Service disabled successfully [2026-01-13 19:53:17] Killing any remaining npm/node processes... [2026-01-13 19:53:17] No running processes found [2026-01-13 19:53:17] Detected Node.js version: 24.12.0 [SUCCESS] Node.js 24 already installed [2026-01-13 19:53:17] Preparing Node.js 24 upgrade… [2026-01-13 19:53:19] Installing Node.js 24… [ERROR] Failed to install Node.js 24 ### 🖼️ Additional context (optional). _No response_
kerem commented 2026-02-26 12:40:16 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jan 13, 2026):

try to remove the update.sh and wget the new one and try again

  1. cd /opt/PVE*
  2. rm -rf update.sh
  3. wget https://raw.githubusercontent.com/community-scripts/ProxmoxVE-Local/refs/heads/main/update.sh
<!-- gh-comment-id:3745400302 --> @MickLesk commented on GitHub (Jan 13, 2026): try to remove the update.sh and wget the new one and try again 1. cd /opt/PVE* 2. rm -rf update.sh 3. wget https://raw.githubusercontent.com/community-scripts/ProxmoxVE-Local/refs/heads/main/update.sh
kerem commented 2026-02-26 12:40:16 +03:00
Author
Owner
Copy link

@rbalaev commented on GitHub (Jan 13, 2026):

it worked!

<!-- gh-comment-id:3745474555 --> @rbalaev commented on GitHub (Jan 13, 2026): it worked!
kerem commented 2026-02-26 12:40:16 +03:00
Author
Owner
Copy link

@ronkinoz commented on GitHub (Jan 13, 2026):

I was having same failure. Suggested remedy has also worked for me to upgrade from 0.5.3 to 0.5.5.

<!-- gh-comment-id:3746869355 --> @ronkinoz commented on GitHub (Jan 13, 2026): I was having same failure. Suggested remedy has also worked for me to upgrade from 0.5.3 to 0.5.5.
kerem commented 2026-02-26 12:40:16 +03:00
Author
Owner
Copy link

@Seqway commented on GitHub (Jan 14, 2026):

Had the same problem ! Worked also for me.
In the future i need to do it also or is it solved now with v0.5.5 ?

<!-- gh-comment-id:3748653564 --> @Seqway commented on GitHub (Jan 14, 2026): Had the same problem ! Worked also for me. In the future i need to do it also or is it solved now with v0.5.5 ?
kerem commented 2026-02-26 12:40:16 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jan 14, 2026):

its solved with 0.5.4/0.5.5

<!-- gh-comment-id:3748725594 --> @MickLesk commented on GitHub (Jan 14, 2026): its solved with 0.5.4/0.5.5
kerem commented 2026-02-26 12:40:16 +03:00
Author
Owner
Copy link

@sesardelaisla commented on GitHub (Jan 14, 2026):

its solved with 0.5.4/0.5.5

This issue has been also happening to me a few versions ago. I managed to update with a custom script to override nodejs installation. Great that it is going to be fixed from now on. Thanks!

<!-- gh-comment-id:3751708155 --> @sesardelaisla commented on GitHub (Jan 14, 2026): > its solved with 0.5.4/0.5.5 This issue has been also happening to me a few versions ago. I managed to update with a custom script to override nodejs installation. Great that it is going to be fixed from now on. Thanks!
kerem commented 2026-02-26 12:40:16 +03:00
Author
Owner
Copy link

@Aareon commented on GitHub (Jan 14, 2026):

Happened to me when attempting to update from v0.5.2

<!-- gh-comment-id:3751742714 --> @Aareon commented on GitHub (Jan 14, 2026): Happened to me when attempting to update from `v0.5.2`
kerem commented 2026-02-26 12:40:16 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jan 14, 2026):

Happened to me when attempting to update from v0.5.2

Then read my Solution above.

<!-- gh-comment-id:3751753629 --> @MickLesk commented on GitHub (Jan 14, 2026): > Happened to me when attempting to update from `v0.5.2` Then read my Solution above.
kerem commented 2026-02-26 12:40:16 +03:00
Author
Owner
Copy link

@Deulfi commented on GitHub (Jan 15, 2026):

Happened to me when attempting to update from v0.5.2

Then read my Solution above.

Version v0.5.2 still fails with the fix.

[SUCCESS] Node.js 24 already installed
[2026-01-15 21:37:12] Preparing Node.js 24 upgrade…
[2026-01-15 21:37:16] Installing Node.js 24…
E: Conflicting values set for option Signed-By regarding source https://deb.nodesource.com/node_24.x/ nodistro: /usr/share/keyrings/nodesource.gpg != /etc/apt/keyrings/nodesource.gpg
E: The list of sources could not be read.
[ERROR] Failed to install Node.js 24

Update worked after nuking it. (rm -f /etc/apt/sources.list.d/nodesource.sources)

<!-- gh-comment-id:3756812685 --> @Deulfi commented on GitHub (Jan 15, 2026): > > Happened to me when attempting to update from `v0.5.2` > > Then read my Solution above. Version v0.5.2 still fails with the fix. > [SUCCESS] Node.js 24 already installed [2026-01-15 21:37:12] Preparing Node.js 24 upgrade… [2026-01-15 21:37:16] Installing Node.js 24… E: Conflicting values set for option Signed-By regarding source https://deb.nodesource.com/node_24.x/ nodistro: /usr/share/keyrings/nodesource.gpg != /etc/apt/keyrings/nodesource.gpg E: The list of sources could not be read. [ERROR] Failed to install Node.js 24 Update worked after nuking it. (rm -f /etc/apt/sources.list.d/nodesource.sources)
kerem commented 2026-02-26 12:40:16 +03:00
Author
Owner
Copy link

@MickLesk commented on GitHub (Jan 15, 2026):

This isnt a Part of the Update anymore? 🤔

<!-- gh-comment-id:3756914596 --> @MickLesk commented on GitHub (Jan 15, 2026): This isnt a Part of the Update anymore? 🤔
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v1.0.0
dependabot/npm_and_yarn/lucide-react-1.8.0
dependabot/npm_and_yarn/vite-8.0.9
dependabot/npm_and_yarn/eslint-10.2.1
dependabot/npm_and_yarn/react-dom-19.2.5
dependabot/npm_and_yarn/tailwindcss-4.2.3
update-version-v0.5.1
feat/lxc_backups
localization
v1.0.0-pre5
v1.0.0-pre4
v1.0.0-pre3
v1.0.0-pre2
v1.0.0-pre1
v0.5.8
v0.5.7
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
v0.4.13
v0.4.12
v0.4.11
v0.4.10.3
v0.4.10.2
v0.4.10.1
v0.4.10
v0.4.9
v0.4.8
v0.4.7
v0.4.6
v0.4.5
v0.4.4
v0.4.3
v0.4.2
v0.4.1
v0.4.0
v0.3.0
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.1
v0.1.0
Labels
Clear labels   
bug

   
enhancement

   
enhancement

   
feature

   
in progress

   
pull-request

Mirrored from GitHub Pull Request

No labels
bug
enhancement
enhancement
feature
in progress
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE-Local#132
No description provided.