Nginx Proxy Manager not loading configs after update

[andreibuzatu]

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

NginxProxyManager

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

bash -x <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh) 2>&1 | tee npm-update.log

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.1.9

📝 Provide a clear and concise description of the issue.

After updating Nginx Proxy Manager using the updated community script from PR #14353, NPM stopped working correctly.

Port 81 was no longer listening, so the web interface became inaccessible. From what I saw, only port 80 was active after the update.

I checked the container and it looks like /usr/local/openresty/nginx/conf/nginx.conf got replaced with the default OpenResty example config during the update process.

The production.conf file was still present and still contained the listen 81 configuration, but nginx was no longer loading anything from /usr/local/openresty/nginx/conf.d/.

Running nginx -T only showed the stock OpenResty localhost configuration and no NPM configs were loaded anymore.

These lines from the verbose update log looked related:

cp conf/nginx.conf '/usr/local/openresty/nginx/conf/nginx.conf.default'
sed -i 's/user npm/user root/g; s/^pid/#pid/g' /usr/local/openresty/nginx/conf/nginx.conf

I managed to get it working again by manually rebuilding the nginx.conf and restoring the missing include/map/cache settings.

I also saved the full verbose update log if needed.

🔄 Steps to reproduce the issue.

Update with latest version of script.

❌ Paste the full error output (if available).

root@nginxproxymanager:# ss -ltnp | grep -E ':(80|81|443)'
LISTEN 0 511 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=9438,fd=6),("nginx",pid=9421,fd=6))
root@nginxproxymanager:# grep -R "listen 81" /usr/local/openresty/nginx/conf.d /etc/nginx/conf.d
/usr/local/openresty/nginx/conf.d/production.conf: listen 81 default;
/etc/nginx/conf.d/production.conf: listen 81 default;

🖼️ Additional context (optional).

No response

[typhoon2099]

Just hit this, no idea how to fix it so all of my services are down...

[MickLesk]

systemctl status openresty?

cat /lib/systemd/system/openresty.service ?

[andreibuzatu]

I managed to fix mine by rebuilding /usr/local/openresty/nginx/conf/nginx.conf.

The update replaced it with the default OpenResty config, so NPM configs from conf.d were no longer being loaded and only port 80 was listening.

Inside the http {} section I restored:

map $scheme $x_forwarded_scheme {
default $scheme;
}

map $scheme $x_forwarded_proto {
default $scheme;
}

log_format standard '$proxy_protocol_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent"';

proxy_cache_path /var/cache/nginx/public levels=1:2 keys_zone=public-cache:30m max_size=1024m;
proxy_cache_path /var/cache/nginx/private levels=1:2 keys_zone=private-cache:5m max_size=1024m;

include /usr/local/openresty/nginx/conf.d/*.conf;

Then I ran:

mkdir -p /var/cache/nginx/public /var/cache/nginx/private

nginx -t && systemctl restart openresty

After that ports 81/443 came back and everything started working again.

@typhoon2099

[andreibuzatu]

@MickLesk

Mine was still showing active (running) even while only port 80 was listening.

/lib/systemd/system/openresty.service also looked normal on my side.

The main issue seemed to be that /usr/local/openresty/nginx/conf/nginx.conf got replaced with the default OpenResty config, so it stopped loading the NPM conf.d configs entirely.

[MickLesk]

Because a purge Change? Sounds very strange

[andreibuzatu]

Confused me too. Initially I restored from a backup and updated again out of curiosity, after that I started to check.