Nginx Proxy Manager update fails #1926

Closed
opened 2026-02-05 02:50:27 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @superfunk2000 on GitHub (Nov 4, 2025).

Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Nginx Proxy Manager LXC

📂 What was the exact command used to execute the script?

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/8.3.5/dac3aa88bac3f300 (running kernel: 6.8.12-9-pve)

📝 Provide a clear and concise description of the issue.

The update script for v2.13.0 aborts with errors.

🔄 Steps to reproduce the issue.

I'm trying to update NPM LXC using "update".

Paste the full error output (if available).

    _   __      _               ____                           __  ___                                 
   / | / /___ _(_)___  _  __   / __ \_________  _  ____  __   /  |/  /___ _____  ____ _____ ____  _____
  /  |/ / __ `/ / __ \| |/_/  / /_/ / ___/ __ \| |/_/ / / /  / /|_/ / __ `/ __ \/ __ `/ __ `/ _ \/ ___/
 / /|  / /_/ / / / / />  <   / ____/ /  / /_/ />  </ /_/ /  / /  / / /_/ / / / / /_/ / /_/ /  __/ /    
/_/ |_/\__, /_/_/ /_/_/|_|  /_/   /_/   \____/_/|_|\__, /  /_/  /_/\__,_/_/ /_/\__,_/\__, /\___/_/     
      /____/                                      /____/                            /____/             

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'npm' is not installed, so not removed
The following packages will be REMOVED:
  nodejs*
0 upgraded, 0 newly installed, 1 to remove and 85 not upgraded.
After this operation, 237 MB disk space will be freed.
(Reading database ... 37244 files and directories currently installed.)
Removing nodejs (22.21.0-1nodesource1) ...
Processing triggers for man-db (2.11.2-2) ...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 85 not upgraded.
Reading package lists... Doneeplacing with 22
Building dependency tree... Done
Reading state information... Done
Package 'nodejs' is not installed, so not removed
Package 'npm' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 85 not upgraded.
Hit:1 http://security.debian.org bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease                      
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease              
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease              
Hit:5 http://openresty.org/package/debian bullseye InRelease
Reading package lists... Done   
Building dependency tree... Done
Reading state information... Done
85 packages can be upgraded. Run 'apt list --upgradable' to see them.
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: npm@11.6.2
npm ERR! notsup Not compatible with your version of node/npm: npm@11.6.2
npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"}
npm ERR! notsup Actual:   {"npm":"8.19.4","node":"v16.20.2"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2025-11-04T06_05_25_077Z-debug-0.log
   ✖️   Failed to update npm to latest version
  ✔️   Setup Node.js 22

changed 1 package, and audited 2 packages in 1s

found 0 vulnerabilities
  ✔️   Installed Node.js modules: yarn
  ✔️   Downloaded NPM v2.12.6
  ⏳   Building Frontendnode: --openssl-legacy-provider is not allowed in NODE_OPTIONS

[ERROR] in line 63: exit code 0: while executing command $STD yarn install --network-timeout 600000


[ERROR] in line 65: exit code 0: while executing command ( sed -i "s|\"version\": \"0.0.0\"|\"version\": \"$RELEASE\"|" backend/package.json; sed -i "s|\"version\": \"0.0.0\"|\"version\": \"$RELEASE\"|" frontend/package.json; cd ./frontend || exit; sed -i 's/"node-sass".*$/"sass": "^1.92.1",/g' package.json; $STD yarn install --network-timeout 600000; $STD yarn build )

🖼️ Additional context (optional).

No response

Originally created by @superfunk2000 on GitHub (Nov 4, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Nginx Proxy Manager LXC ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/8.3.5/dac3aa88bac3f300 (running kernel: 6.8.12-9-pve) ### 📝 Provide a clear and concise description of the issue. The update script for v2.13.0 aborts with errors. ### 🔄 Steps to reproduce the issue. I'm trying to update NPM LXC using "update". ### ❌ Paste the full error output (if available). ``` _ __ _ ____ __ ___ / | / /___ _(_)___ _ __ / __ \_________ _ ____ __ / |/ /___ _____ ____ _____ ____ _____ / |/ / __ `/ / __ \| |/_/ / /_/ / ___/ __ \| |/_/ / / / / /|_/ / __ `/ __ \/ __ `/ __ `/ _ \/ ___/ / /| / /_/ / / / / /> < / ____/ / / /_/ /> </ /_/ / / / / / /_/ / / / / /_/ / /_/ / __/ / /_/ |_/\__, /_/_/ /_/_/|_| /_/ /_/ \____/_/|_|\__, / /_/ /_/\__,_/_/ /_/\__,_/\__, /\___/_/ /____/ /____/ /____/ Reading package lists... Done Building dependency tree... Done Reading state information... Done Package 'npm' is not installed, so not removed The following packages will be REMOVED: nodejs* 0 upgraded, 0 newly installed, 1 to remove and 85 not upgraded. After this operation, 237 MB disk space will be freed. (Reading database ... 37244 files and directories currently installed.) Removing nodejs (22.21.0-1nodesource1) ... Processing triggers for man-db (2.11.2-2) ... Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 85 not upgraded. Reading package lists... Doneeplacing with 22 Building dependency tree... Done Reading state information... Done Package 'nodejs' is not installed, so not removed Package 'npm' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 85 not upgraded. Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:5 http://openresty.org/package/debian bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 85 packages can be upgraded. Run 'apt list --upgradable' to see them. npm ERR! code EBADENGINE npm ERR! engine Unsupported engine npm ERR! engine Not compatible with your version of node/npm: npm@11.6.2 npm ERR! notsup Not compatible with your version of node/npm: npm@11.6.2 npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"} npm ERR! notsup Actual: {"npm":"8.19.4","node":"v16.20.2"} npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2025-11-04T06_05_25_077Z-debug-0.log ✖️ Failed to update npm to latest version ✔️ Setup Node.js 22 changed 1 package, and audited 2 packages in 1s found 0 vulnerabilities ✔️ Installed Node.js modules: yarn ✔️ Downloaded NPM v2.12.6 ⏳ Building Frontendnode: --openssl-legacy-provider is not allowed in NODE_OPTIONS [ERROR] in line 63: exit code 0: while executing command $STD yarn install --network-timeout 600000 [ERROR] in line 65: exit code 0: while executing command ( sed -i "s|\"version\": \"0.0.0\"|\"version\": \"$RELEASE\"|" backend/package.json; sed -i "s|\"version\": \"0.0.0\"|\"version\": \"$RELEASE\"|" frontend/package.json; cd ./frontend || exit; sed -i 's/"node-sass".*$/"sass": "^1.92.1",/g' package.json; $STD yarn install --network-timeout 600000; $STD yarn build ) ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 02:50:27 +03:00
Author
Owner

@MickLesk commented on GitHub (Nov 4, 2025):

You have the very old Install with nvm. Check old closed Issues. You need to remove nvm and Install node22

Or its better to recreate an new LXC.

@MickLesk commented on GitHub (Nov 4, 2025): You have the very old Install with nvm. Check old closed Issues. You need to remove nvm and Install node22 Or its better to recreate an new LXC.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1926