NginxProxyManager / NginxProxyManager/nginx-proxy-manager

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

Open
#5,517 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the v2.13.7 Docker image on Raspberry Pi OS Bullseye and review the reported docker logs error at nginx.conf:87. Inspect /etc/nginx/lualib/resty/core/base.lua:24 and the bundled OpenResty components, then verify that the admin/login page loads without ERR_SOCKET_NOT_CONNECTED and the module error no longer appears.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, lua, nginx
Domain
authentication, backend, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.