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 13 Packages Projects Releases 10 Wiki Activity

Openresty start failed in npm script #1937

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

Originally created by @pafade89 on GitHub (Nov 6, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Nginx Proxy Manager

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)"

⚙️ 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.

openresty could not start. update not possible

🔄 Steps to reproduce the issue.

start update script

❌ Paste the full error output (if available).

Job for openresty.service failed because the control process exited with error code.
See "systemctl status openresty.service" and "journalctl -xeu openresty.service" for details.
invoke-rc.d: initscript openresty, action "start" failed.
x openresty.service - The OpenResty Application Platform
Loaded: loaded (/lib/systemd/system/openresty.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 2025-11-06 09:21:01 CET; 7ms ago
Duration: 24.912s
Process: 13578 ExecStartPre=/usr/local/openresty/nginx/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
CPU: 7ms

Nov 06 09:21:01 nginx systemd[1]: Starting openresty.service - The OpenResty Application Platform...
Nov 06 09:21:01 nginx nginx[13578]: nginx: [emerg] getpwnam("npm") failed in /usr/local/openresty/nginx/conf/nginx.conf:4
Nov 06 09:21:01 nginx nginx[13578]: nginx: configuration file /usr/local/openresty/nginx/conf/nginx.conf test failed
Nov 06 09:21:01 nginx systemd[1]: openresty.service: Control process exited, code=exited, status=1/FAILURE
Nov 06 09:21:01 nginx systemd[1]: openresty.service: Failed with result 'exit-code'.
Nov 06 09:21:01 nginx systemd[1]: Failed to start openresty.service - The OpenResty Application Platform.
dpkg: error processing package openresty (--configure):
installed openresty package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of openresty-opm:
openresty-opm depends on openresty (>= 1.27.1.2); however:
Package openresty is not configured yet.

dpkg: error processing package openresty-opm (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openresty-resty:
openresty-resty depends on openresty (>= 1.27.1.2); however:
Package openresty is not configured yet.

dpkg: error processing package openresty-resty (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u13) ...
Errors were encountered while processing:
openresty
openresty-opm
openresty-resty
E: Sub-process /usr/bin/dpkg returned an error code (1)

[ERROR] in line 160: exit code 0: while executing command $STD apt -y install openresty

🖼️ Additional context (optional).

No response

Originally created by @pafade89 on GitHub (Nov 6, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Nginx Proxy Manager ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)" ### ⚙️ 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. openresty could not start. update not possible ### 🔄 Steps to reproduce the issue. start update script ### ❌ Paste the full error output (if available). Job for openresty.service failed because the control process exited with error code. See "systemctl status openresty.service" and "journalctl -xeu openresty.service" for details. invoke-rc.d: initscript openresty, action "start" failed. x openresty.service - The OpenResty Application Platform Loaded: loaded (/lib/systemd/system/openresty.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Thu 2025-11-06 09:21:01 CET; 7ms ago Duration: 24.912s Process: 13578 ExecStartPre=/usr/local/openresty/nginx/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE) CPU: 7ms Nov 06 09:21:01 nginx systemd[1]: Starting openresty.service - The OpenResty Application Platform... Nov 06 09:21:01 nginx nginx[13578]: nginx: [emerg] getpwnam("npm") failed in /usr/local/openresty/nginx/conf/nginx.conf:4 Nov 06 09:21:01 nginx nginx[13578]: nginx: configuration file /usr/local/openresty/nginx/conf/nginx.conf test failed Nov 06 09:21:01 nginx systemd[1]: openresty.service: Control process exited, code=exited, status=1/FAILURE Nov 06 09:21:01 nginx systemd[1]: openresty.service: Failed with result 'exit-code'. Nov 06 09:21:01 nginx systemd[1]: Failed to start openresty.service - The OpenResty Application Platform. dpkg: error processing package openresty (--configure): installed openresty package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of openresty-opm: openresty-opm depends on openresty (>= 1.27.1.2); however: Package openresty is not configured yet. dpkg: error processing package openresty-opm (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of openresty-resty: openresty-resty depends on openresty (>= 1.27.1.2); however: Package openresty is not configured yet. dpkg: error processing package openresty-resty (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.36-9+deb12u13) ... Errors were encountered while processing: openresty openresty-opm openresty-resty E: Sub-process /usr/bin/dpkg returned an error code (1) [ERROR] in line 160: exit code 0: while executing command $STD apt -y install openresty ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 02:59:30 +03:00
OVERLORD commented 2026-02-05 02:59:39 +03:00
Author
Owner
Copy Link

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

Update of old instance?
How old? What Version before?

You get dpkg Issues, not directly service issues, because there are missing rights and user npm.

@MickLesk commented on GitHub (Nov 6, 2025): Update of old instance? How old? What Version before? You get dpkg Issues, not directly service issues, because there are missing rights and user npm.
OVERLORD commented 2026-02-05 02:59:47 +03:00
Author
Owner
Copy Link

@pafade89 commented on GitHub (Nov 6, 2025):

I don't use an old version. My last one was 2.12.6

@pafade89 commented on GitHub (Nov 6, 2025): I don't use an old version. My last one was 2.12.6
OVERLORD commented 2026-02-05 02:59:58 +03:00
Author
Owner
Copy Link

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

Can you switch to your last snapshot and update your debian system to 13?
https://github.com/community-scripts/ProxmoxVE/discussions/7489

After this hit update again

@MickLesk commented on GitHub (Nov 6, 2025): Can you switch to your last snapshot and update your debian system to 13? https://github.com/community-scripts/ProxmoxVE/discussions/7489 After this hit update again
OVERLORD commented 2026-02-05 03:00:05 +03:00
Author
Owner
Copy Link

@pafade89 commented on GitHub (Nov 6, 2025):

works, thank you =)

@pafade89 commented on GitHub (Nov 6, 2025): works, thank you =)
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#1937
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?