0.5.1: Upgrade fails

[white-rabbit07]

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 24

Afterwards the server restarts automatically but it is still on 0.5.0.

[chadwellens]

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]

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.

🚀 The app offers a built-in updater. Please use it.
⏳ Cleaning up
Error: 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
Error: The list of sources could not be read.
Error: 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
Error: The list of sources could not be read.
npm warn using --force Recommended protections disabled.
Journal file /var/log/journal/18639833b5f84638b7803b83059dad5e/system.journal is truncated, ignoring file.
Vacuuming done, freed 0B of archived journals from /var/log/journal.
Vacuuming done, freed 0B of archived journals from /run/log/journal.
Vacuuming done, freed 0B of archived journals from /var/log/journal/18639833b5f84638b7803b83059dad5e.
✔️ Cleaned
/dev/fd/62: line 21: pveversion: command not found
[ERROR] in line 21: exit code 0: while executing command pve_version=$(pveversion | awk -F'[/ ]' '{print $2}')

[michelroegl-brunner]

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.

🚀 The app offers a built-in updater. Please use it.
⏳ Cleaning up
Error: 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
Error: The list of sources could not be read.
Error: 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
Error: The list of sources could not be read.
npm warn using --force Recommended protections disabled.
Journal file /var/log/journal/18639833b5f84638b7803b83059dad5e/system.journal is truncated, ignoring file.
Vacuuming done, freed 0B of archived journals from /var/log/journal.
Vacuuming done, freed 0B of archived journals from /run/log/journal.
Vacuuming done, freed 0B of archived journals from /var/log/journal/18639833b5f84638b7803b83059dad5e.
✔️ Cleaned
/dev/fd/62: line 21: pveversion: command not found
[ERROR] in line 21: exit code 0: while executing command pve_version=$(pveversion | awk -F'[/ ]' '{print $2}')

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]

To resolve the issue please do the following:
Enter the LXC Shell and edit the update.sh file with this command: nano /opt/ProxmoxVE-Local/update.sh and almost on the end of the file remove the lines:

973    #Update Node.js to 24
974  upgrade_node_to_24

After that change the Version number in the VERSION file (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]

Hi.
I tried it ... and it worked even with this error message while updating:

[2025-12-01 17:05:05] Starting ProxmoxVE-Local update process...
[2025-12-01 17:05:05] Log file: /tmp/update.log
[2025-12-01 17:05:05] Detected running from application directory
[2025-12-01 17:05:05] Starting ProxmoxVE-Local update process...
[2025-12-01 17:05:05] Log file: /tmp/update.log
[2025-12-01 17:05:05] Running as detached process
[2025-12-01 17:05:08] 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
[2025-12-01 17:05:08] Fetching latest release information from GitHub...
[2025-12-01 17:05:08] Using unauthenticated GitHub API request (lower rate limits)
[SUCCESS] Latest release: v0.5.1 (published: 2025-12-01T09:35:29Z)
[2025-12-01 17:05:08] Creating backup directory at /tmp/pve-scripts-backup-20251201-170505...
[2025-12-01 17:05:08] Backing up data directory...
[SUCCESS] Data directory backed up successfully
[2025-12-01 17:05:08] Backing up .env file...
[SUCCESS] .env file backed up successfully
[2025-12-01 17:05:08] Backing up scripts/ct directory...
[SUCCESS] scripts/ct directory backed up successfully
[2025-12-01 17:05:08] Backing up scripts/install directory...
[SUCCESS] scripts/install directory backed up successfully
[2025-12-01 17:05:08] Backing up scripts/tools directory...
[SUCCESS] scripts/tools directory backed up successfully
[2025-12-01 17:05:08] Backing up scripts/vm directory...
[SUCCESS] scripts/vm directory backed up successfully
[2025-12-01 17:05:08] Working from application directory: /opt/ProxmoxVE-Local
[2025-12-01 17:05:08] Disabling systemd service temporarily to prevent auto-restart...
[SUCCESS] Service disabled successfully
[2025-12-01 17:05:08] Killing any remaining npm/node processes...
[2025-12-01 17:05:08] No running processes found
[2025-12-01 17:05:08] Detected Node.js version: 24.11.1
[SUCCESS] Node.js 24 already installed
[2025-12-01 17:05:08] Downloading release v0.5.1...
[SUCCESS] Downloaded release
[SUCCESS] Release extracted successfully
[2025-12-01 17:05:09] Clearing original directory...
[SUCCESS] Original directory cleared
[2025-12-01 17:05:11] Updating application files...
[SUCCESS] Application files updated successfully (976 files)
[2025-12-01 17:05:14] Restoring .env, data directory, and scripts directories from backup...
[SUCCESS] .env file restored from backup
[SUCCESS] Data directory restored from backup
[2025-12-01 17:05:14] Restoring scripts/ct directory from backup...
[SUCCESS] scripts/ct directory restored from backup
[2025-12-01 17:05:14] Restoring scripts/install directory from backup...
[SUCCESS] scripts/install directory restored from backup
[2025-12-01 17:05:14] Restoring scripts/tools directory from backup...
[SUCCESS] scripts/tools directory restored from backup
[2025-12-01 17:05:14] Restoring scripts/vm directory from backup...
[SUCCESS] scripts/vm directory restored from backup
[2025-12-01 17:05:14] Verifying database was restored correctly...
[SUCCESS] Database verified (file: data/settings.db, size: 94208 bytes)
[2025-12-01 17:05:14] Ensuring DATABASE_URL is set in .env file...
[2025-12-01 17:05:14] DATABASE_URL already exists in .env file
[2025-12-01 17:05:14] Installing dependencies...
[SUCCESS] Dependencies installed successfully
[2025-12-01 17:05:40] Generating Prisma client...
[SUCCESS] Prisma client generated successfully
[2025-12-01 17:05:42] Existing migration history detected
[2025-12-01 17:05:42] Found 3 existing migrations
[2025-12-01 17:05:42] Running Prisma migrations...
[SUCCESS] Prisma migrations completed successfully
[2025-12-01 17:05:43] Building application...
[ERROR] Failed to build application
[ERROR] npm run build output:
[ERROR] BUILD: 
[ERROR] BUILD: > pve-scripts-local@0.1.0 build
[ERROR] BUILD: > prisma generate && next build --webpack
[ERROR] BUILD: 
[ERROR] BUILD: Loaded Prisma config from prisma.config.ts.
[ERROR] BUILD: 
[ERROR] BUILD: Prisma schema loaded from prisma/schema.prisma
[ERROR] BUILD: 
[ERROR] BUILD: ✔ Generated Prisma Client (7.0.1) to ./prisma/generated/prisma in 102ms
[ERROR] BUILD: 
[ERROR] BUILD: [baseline-browser-mapping] The data in this module is over two months old.  To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
[ERROR] BUILD: Multiple bundler flags set: TURBOPACK=auto, --webpack.
[ERROR] BUILD: 
[ERROR] BUILD: Edit your command or your package.json script to configure only one bundler.
[ERROR] Install and build failed, rolling back...
[WARNING] Rolling back to previous version...
[2025-12-01 17:05:45] Restoring from backup directory: /tmp/pve-scripts-backup-20251201-170505
[2025-12-01 17:05:45] Restoring data directory...
[SUCCESS] Data directory restored from backup
[2025-12-01 17:05:45] Restoring .env file...
[SUCCESS] .env file restored from backup
[2025-12-01 17:05:45] Restoring scripts/ct directory from backup...
[SUCCESS] scripts/ct directory restored from backup
[2025-12-01 17:05:45] Restoring scripts/install directory from backup...
[SUCCESS] scripts/install directory restored from backup
[2025-12-01 17:05:45] Restoring scripts/tools directory from backup...
[SUCCESS] scripts/tools directory restored from backup
[2025-12-01 17:05:45] Restoring scripts/vm directory from backup...
[SUCCESS] scripts/vm directory restored from backup
[2025-12-01 17:05:45] Cleaning up backup directory...
[ERROR] Update failed. Please check the logs and try again.

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]

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]

Enter the LXC Shell and edit the update.sh file with this command: nano /opt/ProxmoxVE-Local/update.sh and almost on the end of the file remove the lines:

973 #Update Node.js to 24
974 upgrade_node_to_24

Did this and ran update.sh manually. Worked just fine! Running 0.5.1 now.

[white-rabbit07]

I re-installed the whole ProxmoxVE-Local-LXC-Container ... was easier for me. Now it's on 0.5.1, too.

[michelroegl-brunner]

I re-installed the whole ProxmoxVE-Local-LXC-Container ... was easier for me. Now it's on 0.5.1, too.

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]

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.