starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Error on update nginxproxymanager #1833

New Issue
Closed
opened 2026-02-05 02:23:23 +03:00 by OVERLORD · 17 comments
OVERLORD commented 2026-02-05 02:23:23 +03:00
Owner
Copy Link

Originally created by @netbix on GitHub (Oct 19, 2025).

✅ Have you read and understood the above guidelines?

yes

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

nginxproxymanager

📂 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?

9.0.11

📝 Provide a clear and concise description of the issue.

Update error

🔄 Steps to reproduce the issue.

update

❌ Paste the full error output (if available).

_   __      _               ____                           __  ___

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

✔️ Downloaded NPM v2.12.6
⏳ Building Frontendnode: --openssl-legacy-provider is not allowed in NODE_OPTIONS

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

[ERROR] in line 57: 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 @netbix on GitHub (Oct 19, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? nginxproxymanager ### 📂 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? 9.0.11 ### 📝 Provide a clear and concise description of the issue. Update error ### 🔄 Steps to reproduce the issue. update ### ❌ Paste the full error output (if available). _ __ _ ____ __ ___ / | / /___ _(_)___ _ __ / __ \_________ _ ____ __ / |/ /___ _____ ____ _____ ____ _____ / |/ / __ `/ / __ \| |/_/ / /_/ / ___/ __ \| |/_/ / / / / /|_/ / __ `/ __ \/ __ `/ __ `/ _ \/ ___/ / /| / /_/ / / / / /> < / ____/ / / /_/ /> </ /_/ / / / / / /_/ / / / / /_/ / /_/ / __/ / /_/ |_/\__, /_/_/ /_/_/|_| /_/ /_/ \____/_/|_|\__, / /_/ /_/\__,_/_/ /_/\__,_/\__, /\___/_/ /____/ /____/ /____/ ✔️ Downloaded NPM v2.12.6 ⏳ Building Frontendnode: --openssl-legacy-provider is not allowed in NODE_OPTIONS [ERROR] in line 55: exit code 0: while executing command $STD yarn install --network-timeout 600000 [ERROR] in line 57: 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:23:23 +03:00
OVERLORD commented 2026-02-05 02:23:30 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 19, 2025):

recreate the script with new lxc

@MickLesk commented on GitHub (Oct 19, 2025): recreate the script with new lxc
OVERLORD commented 2026-02-05 02:23:32 +03:00
Author
Owner
Copy Link

@netbix commented on GitHub (Oct 19, 2025):

That is? I don't want to lose the data inside, I want to update and not redo a new LXC.

@netbix commented on GitHub (Oct 19, 2025): That is? I don't want to lose the data inside, I want to update and not redo a new LXC.
OVERLORD commented 2026-02-05 02:23:35 +03:00
Author
Owner
Copy Link

@netbix commented on GitHub (Oct 19, 2025):

ok, with a fresh installation it works, but what do I do with a previous installation with data inside?

@netbix commented on GitHub (Oct 19, 2025): ok, with a fresh installation it works, but what do I do with a previous installation with data inside?
OVERLORD commented 2026-02-05 02:23:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 19, 2025):

They Mixed yarn and npm packages. We cannot build this sh"t Tool correctly, because the tarball is not 100% working

@MickLesk commented on GitHub (Oct 19, 2025): They Mixed yarn and npm packages. We cannot build this sh"t Tool correctly, because the tarball is not 100% working
OVERLORD commented 2026-02-05 02:23:42 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 19, 2025):

You can try to build yarn Install Like the install-script with the sed before, but i think that doesnt Change anything

@MickLesk commented on GitHub (Oct 19, 2025): You can try to build yarn Install Like the install-script with the sed before, but i think that doesnt Change anything
OVERLORD commented 2026-02-05 02:23:47 +03:00
Author
Owner
Copy Link

@netbix commented on GitHub (Oct 19, 2025):

I tried upgrading Debian 12 to 13 with
sed -i 's/bookworm/trixie/g' /etc/apt/sources.list && apt update && apt full-upgrade
But nothing works.

@netbix commented on GitHub (Oct 19, 2025): I tried upgrading Debian 12 to 13 with sed -i 's/bookworm/trixie/g' /etc/apt/sources.list && apt update && apt full-upgrade But nothing works.
OVERLORD commented 2026-02-05 02:23:51 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 19, 2025):

No that doesnt affect anything

You need Node 22 and yarn latest

@MickLesk commented on GitHub (Oct 19, 2025): No that doesnt affect anything You need Node 22 and yarn latest
OVERLORD commented 2026-02-05 02:23:54 +03:00
Author
Owner
Copy Link

@netbix commented on GitHub (Oct 19, 2025):

Thanks for your help.
I also tried this:

  1. Install new LXC
  2. Systemctl stop openresty.service
  3. Restore backup /data and /etc/letsencrypt folders
  4. Systemctl start openresty.service

But nothing, error message doesn't start

@netbix commented on GitHub (Oct 19, 2025): Thanks for your help. I also tried this: 1) Install new LXC 2) Systemctl stop openresty.service 3) Restore backup /data and /etc/letsencrypt folders 4) Systemctl start openresty.service But nothing, error message doesn't start
OVERLORD commented 2026-02-05 02:23:57 +03:00
Author
Owner
Copy Link

@netbix commented on GitHub (Oct 19, 2025):

In the base project,

https://github.com/NginxProxyManager/nginx-proxy-manager

The data folders should be:

/data
/etc/letsencrypt

@netbix commented on GitHub (Oct 19, 2025): In the base project, https://github.com/NginxProxyManager/nginx-proxy-manager The data folders should be: /data /etc/letsencrypt
OVERLORD commented 2026-02-05 02:24:00 +03:00
Author
Owner
Copy Link

@netbix commented on GitHub (Oct 19, 2025):

root@nginxproxymanager:~# systemctl status openresty.service
× openresty.service - The OpenResty Application Platform
Loaded: loaded (/usr/lib/systemd/system/openresty.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sun 2025-10-19 15:33:15 CEST; 3min 3s ago
Duration: 6min 24.899s
Invocation: 26ae932e428e4ff8822694b07adabe2b
Process: 1072 ExecStartPre=/usr/local/openresty/nginx/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
Mem peak: 3.7M
CPU: 9ms

Oct 19 15:33:15 nginxproxymanager systemd[1]: Starting openresty.service - The OpenResty Application Platform...
Oct 19 15:33:15 nginxproxymanager nginx[1072]: nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-1/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or >
Oct 19 15:33:15 nginxproxymanager nginx[1072]: nginx: configuration file /usr/local/openresty/nginx/conf/nginx.conf test failed
Oct 19 15:33:15 nginxproxymanager systemd[1]: openresty.service: Control process exited, code=exited, status=1/FAILURE
Oct 19 15:33:15 nginxproxymanager systemd[1]: openresty.service: Failed with result 'exit-code'.
Oct 19 15:33:15 nginxproxymanager systemd[1]: Failed to start openresty.service - The OpenResty Application Platform.

@netbix commented on GitHub (Oct 19, 2025): root@nginxproxymanager:~# systemctl status openresty.service × openresty.service - The OpenResty Application Platform Loaded: loaded (/usr/lib/systemd/system/openresty.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sun 2025-10-19 15:33:15 CEST; 3min 3s ago Duration: 6min 24.899s Invocation: 26ae932e428e4ff8822694b07adabe2b Process: 1072 ExecStartPre=/usr/local/openresty/nginx/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE) Mem peak: 3.7M CPU: 9ms Oct 19 15:33:15 nginxproxymanager systemd[1]: Starting openresty.service - The OpenResty Application Platform... Oct 19 15:33:15 nginxproxymanager nginx[1072]: nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-1/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or > Oct 19 15:33:15 nginxproxymanager nginx[1072]: nginx: configuration file /usr/local/openresty/nginx/conf/nginx.conf test failed Oct 19 15:33:15 nginxproxymanager systemd[1]: openresty.service: Control process exited, code=exited, status=1/FAILURE Oct 19 15:33:15 nginxproxymanager systemd[1]: openresty.service: Failed with result 'exit-code'. Oct 19 15:33:15 nginxproxymanager systemd[1]: Failed to start openresty.service - The OpenResty Application Platform.
OVERLORD commented 2026-02-05 02:24:05 +03:00
Author
Owner
Copy Link

@netbix commented on GitHub (Oct 19, 2025):

Sorry!
I solved it!
It worked.
I restored the backup files incorrectly; I used .zip and not tar.gz, so I'm losing the links.

Update work in new LXC con my restore data

.....................................................
Requirement already satisfied: urllib3<3,>=1.21.1 in /opt/certbot/lib/python3.13/site-packages (from requests->cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (2.5.0)
Requirement already satisfied: certifi>=2017.4.17 in /opt/certbot/lib/python3.13/site-packages (from requests->cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (2025.10.5)
Requirement already satisfied: attrs>=19.2.0 in /opt/certbot/lib/python3.13/site-packages (from jsonlines->cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (25.4.0)
✔️ Setup Environment
yarn install v1.22.22
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning " > @apidevtools/swagger-parser@10.1.0" has unmet peer dependency "openapi-types@>=7".
[4/4] Building fresh packages...
Done in 31.21s.
✔️ Initialized Backend
✔️ Started Services
✔️ Cleaned
✔️ Updated Successfully

Thank's

@netbix commented on GitHub (Oct 19, 2025): Sorry! I solved it! It worked. I restored the backup files incorrectly; I used .zip and not tar.gz, so I'm losing the links. Update work in new LXC con my restore data ..................................................... Requirement already satisfied: urllib3<3,>=1.21.1 in /opt/certbot/lib/python3.13/site-packages (from requests->cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (2.5.0) Requirement already satisfied: certifi>=2017.4.17 in /opt/certbot/lib/python3.13/site-packages (from requests->cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (2025.10.5) Requirement already satisfied: attrs>=19.2.0 in /opt/certbot/lib/python3.13/site-packages (from jsonlines->cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (25.4.0) ✔️ Setup Environment yarn install v1.22.22 [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... warning " > @apidevtools/swagger-parser@10.1.0" has unmet peer dependency "openapi-types@>=7". [4/4] Building fresh packages... Done in 31.21s. ✔️ Initialized Backend ✔️ Started Services ✔️ Cleaned ✔️ Updated Successfully Thank's
OVERLORD commented 2026-02-05 02:24:09 +03:00
Author
Owner
Copy Link

@Nickfost commented on GitHub (Oct 20, 2025):

Could you make the update script handle this?

@Nickfost commented on GitHub (Oct 20, 2025): Could you make the update script handle this?
OVERLORD commented 2026-02-05 02:24:11 +03:00
Author
Owner
Copy Link

@netbix commented on GitHub (Oct 20, 2025):

I don't think it's as feasible as they told me, the compilation fails.
I solved it this way:

  1. From the old LXC Debian 12, systemctl stop openresty.service
  2. Tar.gz backup of /data and /etc/letsencrypt folders
  3. Install new LXC on Debian 13
  4. systemctl stop openresty.service
  5. Import and restore /data and /etc/letsencrypt folders
  6. systemctl start openresty.service

It works!

@netbix commented on GitHub (Oct 20, 2025): I don't think it's as feasible as they told me, the compilation fails. I solved it this way: 1) From the old LXC Debian 12, systemctl stop openresty.service 2) Tar.gz backup of /data and /etc/letsencrypt folders 3) Install new LXC on Debian 13 4) systemctl stop openresty.service 5) Import and restore /data and /etc/letsencrypt folders 6) systemctl start openresty.service It works!
OVERLORD commented 2026-02-05 02:24:16 +03:00
Author
Owner
Copy Link

@Nickfost commented on GitHub (Oct 20, 2025):

couldn't a script backup, wipe, import?

@Nickfost commented on GitHub (Oct 20, 2025): couldn't a script backup, wipe, import?
OVERLORD commented 2026-02-05 02:24:20 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 20, 2025):

No

@MickLesk commented on GitHub (Oct 20, 2025): No
OVERLORD commented 2026-02-05 02:24:24 +03:00
Author
Owner
Copy Link

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

I don't think it's as feasible as they told me, the compilation fails. I solved it this way:

1. From the old LXC Debian 12, systemctl stop openresty.service

2. Tar.gz backup of /data and /etc/letsencrypt folders

3. Install new LXC on Debian 13

4. systemctl stop openresty.service

5. Import and restore /data and /etc/letsencrypt folders

6. systemctl start openresty.service

It works!

Thanks so much for this, These steps worked perfectly for me.

@ianfriend commented on GitHub (Nov 4, 2025): > I don't think it's as feasible as they told me, the compilation fails. I solved it this way: > > 1. From the old LXC Debian 12, systemctl stop openresty.service > > 2. Tar.gz backup of /data and /etc/letsencrypt folders > > 3. Install new LXC on Debian 13 > > 4. systemctl stop openresty.service > > 5. Import and restore /data and /etc/letsencrypt folders > > 6. systemctl start openresty.service > > > It works! Thanks so much for this, These steps worked perfectly for me.
OVERLORD commented 2026-02-05 02:24:30 +03:00
Author
Owner
Copy Link

@eikaramba commented on GitHub (Nov 5, 2025):

can confirm, i did create an admin user first and logged in, thus i was first confused when i refreshed the page and nothing worked. of course, because the logged in user in the browser was just overwritten. so do not attempt to create a user, directly restore the data. or logout and login again, no harm.

@eikaramba commented on GitHub (Nov 5, 2025): can confirm, i did create an admin user first and logged in, thus i was first confused when i refreshed the page and nothing worked. of course, because the logged in user in the browser was just overwritten. so do not attempt to create a user, directly restore the data. or logout and login again, no harm.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1833
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?