mirror of
https://github.com/community-scripts/ProxmoxVE-Local.git
synced 2026-04-25 12:45:50 +03:00
[GH-ISSUE #363] 0.5.1: Upgrade fails #111
Labels
No labels
bug
enhancement
enhancement
feature
in progress
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ProxmoxVE-Local#111
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @white-rabbit07 on GitHub (Nov 29, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE-Local/issues/363
Hi.
I tried to upgrade via WebUI from 0.5.0 to 0.5.1 and all I got was:
[2025-11-29 20:38:26] Backing up data directory... [SUCCESS] Data directory backed up successfully [2025-11-29 20:38:26] Backing up .env file... [SUCCESS] .env file backed up successfully [2025-11-29 20:38:26] Backing up scripts/ct directory... [SUCCESS] scripts/ct directory backed up successfully [2025-11-29 20:38:26] Backing up scripts/install directory... [SUCCESS] scripts/install directory backed up successfully [2025-11-29 20:38:26] Backing up scripts/tools directory... [SUCCESS] scripts/tools directory backed up successfully [2025-11-29 20:38:26] Backing up scripts/vm directory... [SUCCESS] scripts/vm directory backed up successfully [2025-11-29 20:38:26] Working from application directory: /opt/ProxmoxVE-Local [2025-11-29 20:38:26] Disabling systemd service temporarily to prevent auto-restart... [SUCCESS] Service disabled successfully [2025-11-29 20:38:27] Killing any remaining npm/node processes... [2025-11-29 20:38:27] No running processes found [2025-11-29 20:38:27] Detected Node.js version: 24.11.1 [SUCCESS] Node.js 24 already installed [2025-11-29 20:38:27] Preparing Node.js 24 upgrade… [2025-11-29 20:38:28] Installing Node.js 24… [ERROR] Failed to install Node.js 24Afterwards the server restarts automatically but it is still on 0.5.0.
@chadwellens commented on GitHub (Nov 29, 2025):
Same here, but no reason given i.e. Failed to install Node.js.
I deleted the LXC, rebooted everything, reinstalled with the helper script - but no joy.
@xb00tt commented on GitHub (Nov 30, 2025):
Same issue as above mentioned. I am running a fresh 0.5.0 install since the "breaking changes" in that update.
This is error when running "update" inside the LXC.
@michelroegl-brunner commented on GitHub (Dec 1, 2025):
As it says up top you should use the in App updater, not the update command. The update command in the lxc will not update the App. The other Errors are unrelated.
@michelroegl-brunner commented on GitHub (Dec 1, 2025):
To resolve the issue please do the following:
Enter the LXC Shell and edit the
update.shfile with this command:nano /opt/ProxmoxVE-Local/update.shand almost on the end of the file remove the lines:After that change the Version number in the
VERSIONfile (nano /opt/ProxmoxVE-Local/VERSION) to something different.Then you can run the update in the Web App again.
There was a bug in the Update.sh file introduced in 0.5.0. It is allready corrected, but it only is correct after you have updated.
@white-rabbit07 commented on GitHub (Dec 1, 2025):
Hi.
I tried it ... and it worked even with this error message while updating:
Afterwards I see v0.5.1 in the WebUI ... but the Stop/Destroy Commands for other LXC containers still don't work.
Is it correct like this?
@michelroegl-brunner commented on GitHub (Dec 1, 2025):
Can you please try and run the update.sh file manually in the lxc console please? That fixed the issue for me. I look again what broke there.
@xb00tt commented on GitHub (Dec 1, 2025):
Did this and ran update.sh manually. Worked just fine! Running 0.5.1 now.
@white-rabbit07 commented on GitHub (Dec 2, 2025):
I re-installed the whole ProxmoxVE-Local-LXC-Container ... was easier for me. Now it's on 0.5.1, too.
@michelroegl-brunner commented on GitHub (Dec 2, 2025):
Good to hear!
And yes i know it is anoying sometimes when it breaks again, but that helps so much in speeding up the development of new features
@scarecr0w12 commented on GitHub (Dec 6, 2025):
Check your Apt source files. For some reason i had a older .sources file and .list for node, removed the sources, and it worked. I think because it was an install of the pve lxc from early v4, and i was upgrading to v5, It must place a node apt source file that is different the original? just a thought.