[GH-ISSUE #429] v0.5.3 update failed

kerem commented

2026-02-26 12:40:15 +03:00

Owner

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

✅ Have you read and understood the above guidelines?

yes

📝 Provide a clear and concise description of the issue.

Everything is on the screenshot, cannot upgrade from v0.5.2 to v0.5.3 due to install Node.js 24 failure:

🔄 Steps to reproduce the issue.

Update from v0.5.2 to v0.5.3

❌ Paste the full error output (if available).

Failed to install Node.js 24

🖼️ Additional context (optional).

No response

Originally created by @jmcruvellier on GitHub (Jan 7, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE-Local/issues/429 ### ✅ Have you read and understood the above guidelines? yes ### 📝 Provide a clear and concise description of the issue. Everything is on the screenshot, cannot upgrade from v0.5.2 to v0.5.3 due to install Node.js 24 failure: <img width="491" height="371" alt="Image" src="https://github.com/user-attachments/assets/72e29493-2842-4710-a084-9f2fc908970f" /> ### 🔄 Steps to reproduce the issue. Update from v0.5.2 to v0.5.3 ### ❌ Paste the full error output (if available). Failed to install Node.js 24 ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:40:15 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:40:16 +03:00

Author

Owner

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

The same!

@rbalaev commented on GitHub (Jan 7, 2026): The same!

kerem commented

2026-02-26 12:40:16 +03:00

Author

Owner

@eryxator commented on GitHub (Jan 7, 2026):

@jmcruvellier same bug, this is solve issue (nodesource removed node 24.x distro?):

rm /etc/apt/sources.list.d/nodesource.sources
rm /etc/apt/sources.list.d/nodesource.list

@eryxator commented on GitHub (Jan 7, 2026): @jmcruvellier same bug, this is solve issue (nodesource removed node 24.x distro?): ``` rm /etc/apt/sources.list.d/nodesource.sources rm /etc/apt/sources.list.d/nodesource.list ```

kerem commented

2026-02-26 12:40:16 +03:00

Author

Owner

@zx81uk commented on GitHub (Jan 8, 2026):

Same here, fails at NodeJS

@zx81uk commented on GitHub (Jan 8, 2026): Same here, fails at NodeJS

kerem commented

2026-02-26 12:40:16 +03:00

Author

Owner

@dszp commented on GitHub (Jan 8, 2026):

Same problem here.

@dszp commented on GitHub (Jan 8, 2026): Same problem here.

kerem commented

2026-02-26 12:40:16 +03:00

Author

Owner

@scottp2765 commented on GitHub (Jan 8, 2026):

mee too.

@scottp2765 commented on GitHub (Jan 8, 2026): mee too.

kerem commented

2026-02-26 12:40:16 +03:00

Author

Owner

@Semicolon1071 commented on GitHub (Jan 8, 2026):

@jmcruvellier same bug, this is solve issue (nodesource removed node 24.x distro?):
rm /etc/apt/sources.list.d/nodesource.sources
rm /etc/apt/sources.list.d/nodesource.list

This was not enough to solve it for me, although it did allow me to run apt update && apt upgrade -y which updated to latest nodejs (24.12). But it fixed it for you, correct?

To any developer interested, this is the output of the /opt/ProxmoxVE-Local/update.log:

root@pve-scripts-local:/opt/ProxmoxVE-Local# cat update.log 
[2026-01-08 12:21:12] Starting ProxmoxVE-Local update process...
[2026-01-08 12:21:12] Log file: /tmp/update.log
[2026-01-08 12:21:12] Detected running from application directory
[2026-01-08 12:21:12] Starting ProxmoxVE-Local update process...
[2026-01-08 12:21:12] Log file: /tmp/update.log
[2026-01-08 12:21:12] Running as detached process
[2026-01-08 12:21:15] 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-08 12:21:16] Fetching latest release information from GitHub...
[2026-01-08 12:21:16] Using unauthenticated GitHub API request (lower rate limits)
[SUCCESS] Latest release: v0.5.3 (published: 2026-01-07T19:52:09Z)
[2026-01-08 12:21:17] Creating backup directory at /tmp/pve-scripts-backup-20260108-122112...
[2026-01-08 12:21:17] Backing up data directory...
[SUCCESS] Data directory backed up successfully
[2026-01-08 12:21:17] Backing up .env file...
[SUCCESS] .env file backed up successfully
[2026-01-08 12:21:17] Backing up scripts/ct directory...
[SUCCESS] scripts/ct directory backed up successfully
[2026-01-08 12:21:18] Backing up scripts/install directory...
[SUCCESS] scripts/install directory backed up successfully
[2026-01-08 12:21:19] Backing up scripts/tools directory...
[SUCCESS] scripts/tools directory backed up successfully
[2026-01-08 12:21:19] Backing up scripts/vm directory...
[SUCCESS] scripts/vm directory backed up successfully
[2026-01-08 12:21:19] Working from application directory: /opt/ProxmoxVE-Local
[2026-01-08 12:21:19] Disabling systemd service temporarily to prevent auto-restart...
Removed '/etc/systemd/system/multi-user.target.wants/pvescriptslocal.service'.
[SUCCESS] Service disabled successfully
[2026-01-08 12:21:19] Killing any remaining npm/node processes...
[2026-01-08 12:21:20] No running processes found
[2026-01-08 12:21:20] Detected Node.js version: 24.11.1
[SUCCESS] Node.js 24 already installed
[2026-01-08 12:21:20] Preparing Node.js 24 upgrade…
[2026-01-08 12:21:25] Installing Node.js 24…
[ERROR] Failed to install Node.js 24

While not fixing the root cause of this error, which seems to be related to the failed Node.js upgrade, I think it would be helpful to have error-handling, that would ensure to activate the pvescriptslocal.service again, instead of simply quitting. More generally: ensure errors are caught and attempt to restore last working state, which seems to be backed up in the first few lines of the update.

EDIT: for anyone else, whose Web UI was unavailable due to the service being disabled, these commands fixed it for me:

root@pve-scripts-local:/etc/systemd/system# systemctl enable pvescriptslocal.service 
Created symlink '/etc/systemd/system/multi-user.target.wants/pvescriptslocal.service' → '/etc/systemd/system/pvescriptslocal.service'.
root@pve-scripts-local:/etc/systemd/system# systemctl start pvescriptslocal.service 
root@pve-scripts-local:/etc/systemd/system# systemctl status pvescriptslocal.service 
● pvescriptslocal.service - PVEScriptslocal Service
     Loaded: loaded (/etc/systemd/system/pvescriptslocal.service; enabled; preset: enabled)
     Active: active (running) since Thu 2026-01-08 13:05:49 CET; 7s ago

@Semicolon1071 commented on GitHub (Jan 8, 2026): > [@jmcruvellier](https://github.com/jmcruvellier) same bug, this is solve issue (nodesource removed node 24.x distro?): > > ``` > rm /etc/apt/sources.list.d/nodesource.sources > rm /etc/apt/sources.list.d/nodesource.list > ``` This was not enough to solve it for me, although it did allow me to run `apt update && apt upgrade -y` which updated to latest nodejs (24.12). But it fixed it for you, correct? To any developer interested, this is the output of the `/opt/ProxmoxVE-Local/update.log`: ``` root@pve-scripts-local:/opt/ProxmoxVE-Local# cat update.log [2026-01-08 12:21:12] Starting ProxmoxVE-Local update process... [2026-01-08 12:21:12] Log file: /tmp/update.log [2026-01-08 12:21:12] Detected running from application directory [2026-01-08 12:21:12] Starting ProxmoxVE-Local update process... [2026-01-08 12:21:12] Log file: /tmp/update.log [2026-01-08 12:21:12] Running as detached process [2026-01-08 12:21:15] 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-08 12:21:16] Fetching latest release information from GitHub... [2026-01-08 12:21:16] Using unauthenticated GitHub API request (lower rate limits) [SUCCESS] Latest release: v0.5.3 (published: 2026-01-07T19:52:09Z) [2026-01-08 12:21:17] Creating backup directory at /tmp/pve-scripts-backup-20260108-122112... [2026-01-08 12:21:17] Backing up data directory... [SUCCESS] Data directory backed up successfully [2026-01-08 12:21:17] Backing up .env file... [SUCCESS] .env file backed up successfully [2026-01-08 12:21:17] Backing up scripts/ct directory... [SUCCESS] scripts/ct directory backed up successfully [2026-01-08 12:21:18] Backing up scripts/install directory... [SUCCESS] scripts/install directory backed up successfully [2026-01-08 12:21:19] Backing up scripts/tools directory... [SUCCESS] scripts/tools directory backed up successfully [2026-01-08 12:21:19] Backing up scripts/vm directory... [SUCCESS] scripts/vm directory backed up successfully [2026-01-08 12:21:19] Working from application directory: /opt/ProxmoxVE-Local [2026-01-08 12:21:19] Disabling systemd service temporarily to prevent auto-restart... Removed '/etc/systemd/system/multi-user.target.wants/pvescriptslocal.service'. [SUCCESS] Service disabled successfully [2026-01-08 12:21:19] Killing any remaining npm/node processes... [2026-01-08 12:21:20] No running processes found [2026-01-08 12:21:20] Detected Node.js version: 24.11.1 [SUCCESS] Node.js 24 already installed [2026-01-08 12:21:20] Preparing Node.js 24 upgrade… [2026-01-08 12:21:25] Installing Node.js 24… [ERROR] Failed to install Node.js 24 ``` While not fixing the root cause of this error, which seems to be related to the failed Node.js upgrade, I think it would be helpful to have error-handling, that would ensure to activate the `pvescriptslocal.service` again, instead of simply quitting. More generally: ensure errors are caught and attempt to restore last working state, which seems to be backed up in the first few lines of the update. EDIT: for anyone else, whose Web UI was unavailable due to the service being disabled, these commands fixed it for me: ```shell root@pve-scripts-local:/etc/systemd/system# systemctl enable pvescriptslocal.service Created symlink '/etc/systemd/system/multi-user.target.wants/pvescriptslocal.service' → '/etc/systemd/system/pvescriptslocal.service'. root@pve-scripts-local:/etc/systemd/system# systemctl start pvescriptslocal.service root@pve-scripts-local:/etc/systemd/system# systemctl status pvescriptslocal.service ● pvescriptslocal.service - PVEScriptslocal Service Loaded: loaded (/etc/systemd/system/pvescriptslocal.service; enabled; preset: enabled) Active: active (running) since Thu 2026-01-08 13:05:49 CET; 7s ago ```

kerem commented

2026-02-26 12:40:16 +03:00

Author

Owner

@BryanCLieberman commented on GitHub (Jan 8, 2026):

This should fix the issue but needs approval. In the meantime you can run the following in your Proxmox VE Helper Scripts container to allow yourself to update.

sed -i '/#Update Node.js to 24/,/upgrade_node_to_24/d' /opt/ProxmoxVE-Local/update.sh

Please note these changes are not official and if you use this it's at your own risk. That being said, all it does is remove a redundant nodejs update check that causes the update to error out, and shouldn't cause any issues.

@BryanCLieberman commented on GitHub (Jan 8, 2026): This should fix the issue but needs approval. In the meantime you can run the following in your Proxmox VE Helper Scripts container to allow yourself to update. `sed -i '/#Update Node.js to 24/,/upgrade_node_to_24/d' /opt/ProxmoxVE-Local/update.sh` Please note these changes are not official and if you use this it's at your own risk. That being said, all it does is remove a redundant nodejs update check that causes the update to error out, and shouldn't cause any issues.

kerem commented

2026-02-26 12:40:16 +03:00

Author

Owner

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

FYI, when running the upgrade from 0.5.2 to 0.5.4 via the web update, which describes including this fix being included, it still hangs and then eventually times out and quits without success after sitting here for some time:

...
[SUCCESS] Node.js 24 already installed
[2026-01-13 11:12:00] Preparing Node.js 24 upgrade…
[2026-01-13 11:12:01] Installing Node.js 24…
[ERROR] Failed to install Node.js 24

So the fix that has been implemented does not appear to be properly creating success in going from 0.5.2 to 0.5.4, if that was the intention, at least for me.

I have not yet applied the manual fix that @BryanCLieberman mentioned above or attempted manual updating.

@dszp commented on GitHub (Jan 13, 2026): FYI, when running the upgrade from 0.5.2 to 0.5.4 via the web update, which describes including this fix being included, it still hangs and then eventually times out and quits without success after sitting here for some time: ``` ... [SUCCESS] Node.js 24 already installed [2026-01-13 11:12:00] Preparing Node.js 24 upgrade… [2026-01-13 11:12:01] Installing Node.js 24… [ERROR] Failed to install Node.js 24 ``` So the fix that has been implemented does not appear to be properly creating success in going from 0.5.2 to 0.5.4, if that was the intention, at least for me. I have not yet applied the manual fix that @BryanCLieberman mentioned above or attempted manual updating.

kerem commented

2026-02-26 12:40:16 +03:00

Author

Owner

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

rm -rf update.sh and wget the update.sh from github ?

@MickLesk commented on GitHub (Jan 13, 2026): rm -rf update.sh and wget the update.sh from github ?

Rows
Columns

[GH-ISSUE #429] v0.5.3 update failed #127

✅ Have you read and understood the above guidelines?

📝 Provide a clear and concise description of the issue.

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).