Error logged by version 2.13.7, preventing login to the NPM admin page

[forestial]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • No (cannot upgrade past v2.13.7 because of Raspberry PI limitation)
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug

I have upgraded to version 2.13.7, which is the most recent version that is supported on my architecture (armhf on Raspberry Pi 32-bit).
The "docker logs" command shows many occurrences of the following error message:

nginx: [alert] failed to load the 'resty.core' module (https://github.com/openresty/lua-resty-core); ensure you are using an OpenResty release from https://openresty.org/en/download.html (reason: /etc/nginx/lualib/resty/core/base.lua:24: ngx_http_lua_module 0.10.25 required) in /etc/nginx/nginx.conf:87

The NPM admin/login page does not load in my browser (local to the server, or remotely), showing ERR_SOCKET_NOT_CONNECTED.

My docker container has a mapping of the /etc/nginx directory to the host, but the contents of my nginx.conf file are identical with the original in the container. Similarly the file /etc/nginx/lualib/resty/core/base.lua is unmodified.

The error message indicates than an incorrect OpenResty version is installed. But I presume that OpenResty is included with the NPM container, so I don't know how to proceed to correct this.

Nginx Proxy Manager Version

I cannot open the login page, but I verified in docker that I am using v2.13.7.
Similarly if I enter bash on the container via "docker exec..." I see 2.13.7 reported.

To Reproduce
Steps to reproduce the behavior:

1. Attempt to open the admin/login page (get socket error in browser)
2. Review the output of "docker logs" command and observed the error above.

Expected behavior
Expect the login page to open without error. I was previously running an old v2.11.something and there was no error there.

Screenshots

Operating System

Raspberry PI 4. Raspberry PI OS "bullseye"

Additional context

[IMNotMax]

looks like the openresty default conf file erased the npm file
My AI Agent gave me this :

Here is the complete diagnosis:
Root cause: The main nginx.conf was replaced with the default OpenResty configuration. Two critical elements are missing:
1. The log_format main directive is not defined, but default.conf uses it on line 11 (access_log … main;)
2. The include log.conf is not loaded in the http {} block of nginx.conf — so the proxy and standard log formats are not available either
3. The include of the include/ directory is missing in nginx.conf
4. The default server block in the http {} block conflicts with the one in default.conf (both listen on port 80)
In summary, nginx.conf is the vanilla OpenResty version, not the customized NPM version. The NPM configuration should include the log format files, the NPM includes, and should not have a default server block.
Do you want me to restore the correct nginx.conf for NPM? I can rebuild it from the NPM files present in /etc/nginx/conf.d/include/.

[Zwytch]

@forestial @IMNotMax Were either of you able to resolve this as I'm having the same issue

[Zwytch]

Its strange as I was using one of the latest releases a week ago and it was working fine.
But now I've had to roll all the way back to 2.12.2 to get it to work on my Raspberry Pi.

[IMNotMax]

I use an ai agent (Hermes) to help me with technical issues in my homelab.
Hermes manage to recreate the conf file. Restarting openresty with the good conf file resolved the issue.

[forestial]

No; I haven't been able to resolve this. I used Zwytch's tip about the older version to roll back to that; so my npm site is running again, but on the old version. I'd still like to be able to get to something more recent.

@IMNotMax would you be able to post the recreated nginx.conf file that your agent produced?

I am also unable to understand how this broke. In my system I have a docker volume mapping /etc/nginx to a folder on the host (so that I could if needed edit any of those files). My npm site broke when I pulled v2.3.7 of the docker container. But my understanding is that my host folder should not have been touched by pulling the container, so I'm puzzled how this happened.

[IMNotMax]

Here !
From the / INSIDE the LXC container (or inside the docker container - beware of the future updates)

root@NginxProxyManager:~# cat /usr/local/openresty/nginx/conf/nginx.conf

# run nginx in foreground
#daemon off;
pid /run/nginx/nginx.pid;
user www-data;

# Set number of worker processes automatically based on number of CPU cores.
worker_processes auto;

# Enables the use of JIT for regular expressions to speed-up their processing.
pcre_jit on;

error_log /data/logs/fallback_error.log warn;

# Includes files with directives to load dynamic modules.
include /etc/nginx/modules/*.conf;

# Custom
include /data/nginx/custom/root_top[.]conf;

events {
        include /data/nginx/custom/events[.]conf;
}

http {
        include                       /etc/nginx/mime.types;
        default_type                  application/octet-stream;
        sendfile                      on;
        server_tokens                 off;
        tcp_nopush                    on;
        tcp_nodelay                   on;
        client_body_temp_path         /tmp/nginx/body 1 2;
        keepalive_timeout             90s;
        proxy_connect_timeout         90s;
        proxy_send_timeout            90s;
        proxy_read_timeout            90s;
        ssl_prefer_server_ciphers     on;
        gzip                          on;
        proxy_ignore_client_abort     off;
        client_max_body_size          2000m;
        server_names_hash_bucket_size 1024;
        proxy_http_version            1.1;
        proxy_set_header              X-Forwarded-Scheme $scheme;
        proxy_set_header              X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header              Accept-Encoding "";
        proxy_cache                   off;
        proxy_cache_path              /var/lib/nginx/cache/public  levels=1:2 keys_zone=public-cache:30m max_size=192m;
        proxy_cache_path              /var/lib/nginx/cache/private levels=1:2 keys_zone=private-cache:5m max_size=1024m;

        # Log format and fallback log file
        include /etc/nginx/conf.d/include/log-proxy.conf;

        # Dynamically generated resolvers file
        include /etc/nginx/conf.d/include/resolvers.conf;

        # Default upstream scheme
        map $host $forward_scheme {
                default http;
        }

        # Handle upstream X-Forwarded-Proto and X-Forwarded-Scheme header
        map $http_x_forwarded_proto $x_forwarded_proto {
                "http" "http";
                "https" "https";
                default $scheme;
        }
        map $http_x_forwarded_scheme $x_forwarded_scheme {
                "http" "http";
                "https" "https";
                default $scheme;
        }

        # Real IP Determination

        # Local subnets:
        set_real_ip_from 10.0.0.0/8;
        set_real_ip_from 172.16.0.0/12; # Includes Docker subnet
        set_real_ip_from 192.168.0.0/16;
        # NPM generated CDN ip ranges:
        include /etc/nginx/conf.d/include/ip_ranges.conf;
        # always put the following 2 lines after ip subnets:
        real_ip_header X-Real-IP;
        real_ip_recursive on;

        # Custom
        include /data/nginx/custom/http_top[.]conf;

        # Files generated by NPM
        include /etc/nginx/conf.d/*.conf;
        include /data/nginx/default_host/*.conf;
        include /data/nginx/proxy_host/*.conf;
        include /data/nginx/redirection_host/*.conf;
        include /data/nginx/dead_host/*.conf;
        include /data/nginx/temp/*.conf;

        # Custom
        include /data/nginx/custom/http[.]conf;
}

stream {
        # Log format and fallback log file
        include /etc/nginx/conf.d/include/log-stream.conf;

        # Files generated by NPM
        include /data/nginx/stream/*.conf;

        # Custom
        include /data/nginx/custom/stream[.]conf;
}

# Custom
include /data/nginx/custom/root[.]conf;