starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #2697] Nginx proxy manager not working after update to 2.9.20 #1859

New issue
Closed
opened 2026-02-26 07:32:45 +03:00 by kerem · 3 comments
kerem commented 2026-02-26 07:32:45 +03:00
Owner
Copy link

Originally created by @pluim003 on GitHub (Mar 17, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2697

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • 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

Pulled the latest image and started my Docker-container to find out that none of the sites I have can't be reached anymore. When checking portainer the log shows the following

2023-03-17T06:30:06.655509626Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84

2023-03-17T06:30:07.338235078Z ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d

2023-03-17T06:30:07.338328670Z   ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf

2023-03-17T06:30:07.342167541Z   ❯ /etc/nginx/conf.d/include/resolvers.conf

2023-03-17T06:30:07.345959875Z   ❯ /etc/nginx/conf.d/include/block-exploits.conf

2023-03-17T06:30:07.349856431Z   ❯ /etc/nginx/conf.d/include/assets.conf

2023-03-17T06:30:07.353748838Z   ❯ /etc/nginx/conf.d/include/proxy.conf

2023-03-17T06:30:07.358799667Z   ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf

2023-03-17T06:30:07.362839629Z   ❯ /etc/nginx/conf.d/include/ip_ranges.conf

2023-03-17T06:30:07.366820666Z   ❯ /etc/nginx/conf.d/include/force-ssl.conf

2023-03-17T06:30:07.370862629Z   ❯ /etc/nginx/conf.d/production.conf

2023-03-17T06:30:07.374856054Z   ❯ /etc/nginx/conf.d/default.conf

2023-03-17T06:30:07.390621944Z ❯ Enabling IPV6 in hosts: /data/nginx

2023-03-17T06:30:07.390733573Z   ❯ /data/nginx/proxy_host/16.conf

2023-03-17T06:30:07.395038923Z   ❯ /data/nginx/proxy_host/10.conf

2023-03-17T06:30:07.399352866Z   ❯ /data/nginx/proxy_host/12.conf

2023-03-17T06:30:07.403587235Z   ❯ /data/nginx/proxy_host/11.conf

2023-03-17T06:30:07.407840159Z   ❯ /data/nginx/proxy_host/8.conf

2023-03-17T06:30:07.411881844Z   ❯ /data/nginx/proxy_host/14.conf

2023-03-17T06:30:07.416131009Z   ❯ /data/nginx/proxy_host/9.conf

2023-03-17T06:30:07.420186175Z   ❯ /data/nginx/proxy_host/15.conf

2023-03-17T06:30:07.424374878Z   ❯ /data/nginx/proxy_host/13.conf

Also I can't reach Nginx locally through :81

Nginx Proxy Manager Version

2.9.20

To Reproduce
Steps to reproduce the behavior:

  1. pull latest image
  2. run docker-compose up -d
  3. check log in Portainer
  4. See error

Expected behavior

A 'normal' working Nginx-proxy-manager

Screenshots

Operating System

Linux 5.15.84 on Raspberry Pi4 (arm64)

Additional context

2.9.19 is working fine, so when using that image everything is working as expected.

Originally created by @pluim003 on GitHub (Mar 17, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2697 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - 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** <!-- A clear and concise description of what the bug is. --> Pulled the latest image and started my Docker-container to find out that none of the sites I have can't be reached anymore. When checking portainer the log shows the following ```` 2023-03-17T06:30:06.655509626Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84 2023-03-17T06:30:07.338235078Z ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d 2023-03-17T06:30:07.338328670Z ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf 2023-03-17T06:30:07.342167541Z ❯ /etc/nginx/conf.d/include/resolvers.conf 2023-03-17T06:30:07.345959875Z ❯ /etc/nginx/conf.d/include/block-exploits.conf 2023-03-17T06:30:07.349856431Z ❯ /etc/nginx/conf.d/include/assets.conf 2023-03-17T06:30:07.353748838Z ❯ /etc/nginx/conf.d/include/proxy.conf 2023-03-17T06:30:07.358799667Z ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf 2023-03-17T06:30:07.362839629Z ❯ /etc/nginx/conf.d/include/ip_ranges.conf 2023-03-17T06:30:07.366820666Z ❯ /etc/nginx/conf.d/include/force-ssl.conf 2023-03-17T06:30:07.370862629Z ❯ /etc/nginx/conf.d/production.conf 2023-03-17T06:30:07.374856054Z ❯ /etc/nginx/conf.d/default.conf 2023-03-17T06:30:07.390621944Z ❯ Enabling IPV6 in hosts: /data/nginx 2023-03-17T06:30:07.390733573Z ❯ /data/nginx/proxy_host/16.conf 2023-03-17T06:30:07.395038923Z ❯ /data/nginx/proxy_host/10.conf 2023-03-17T06:30:07.399352866Z ❯ /data/nginx/proxy_host/12.conf 2023-03-17T06:30:07.403587235Z ❯ /data/nginx/proxy_host/11.conf 2023-03-17T06:30:07.407840159Z ❯ /data/nginx/proxy_host/8.conf 2023-03-17T06:30:07.411881844Z ❯ /data/nginx/proxy_host/14.conf 2023-03-17T06:30:07.416131009Z ❯ /data/nginx/proxy_host/9.conf 2023-03-17T06:30:07.420186175Z ❯ /data/nginx/proxy_host/15.conf 2023-03-17T06:30:07.424374878Z ❯ /data/nginx/proxy_host/13.conf ```` Also I can't reach Nginx locally through <ip-address>:81 **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> 2.9.20 **To Reproduce** Steps to reproduce the behavior: 1. pull latest image 2. run docker-compose up -d 3. check log in Portainer 4. See error **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> A 'normal' working Nginx-proxy-manager **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> Linux 5.15.84 on Raspberry Pi4 (arm64) **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. --> 2.9.19 is working fine, so when using that image everything is working as expected.
kerem 2026-02-26 07:32:45 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 07:32:45 +03:00
Author
Owner
Copy link

@pluim003 commented on GitHub (Mar 24, 2023):

Tried also release 2.9.21 with no success. Thought I commented but don't see the comment. Just tried 2.9.22 and that gives me:

2023-03-24T05:21:51.209949387Z [3/24/2023] [5:21:51 AM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
2023-03-24T05:21:51.212162452Z [3/24/2023] [5:21:51 AM] [Global   ] › ℹ  info      Generating SQLite knex configuration
2023-03-24T05:21:51.217380596Z [3/24/2023] [5:21:51 AM] [Global   ] › ⬤  debug     Wrote db configuration to config file: ./config/production.json
2023-03-24T05:21:52.076553073Z ❯ Starting nginx ...
2023-03-24T05:21:52.165406187Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84
2023-03-24T05:21:53.181088634Z ❯ Starting nginx ...
2023-03-24T05:21:53.270381672Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84
2023-03-24T05:21:54.264271509Z [3/24/2023] [5:21:54 AM] [Migrate  ] › ℹ  info      Current database version: none
2023-03-24T05:21:54.285149086Z ❯ Starting nginx ...
2023-03-24T05:21:54.368614835Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84
2023-03-24T05:21:54.494722806Z [3/24/2023] [5:21:54 AM] [Setup    ] › ℹ  info      Creating a new JWT key pair...
2023-03-24T05:21:55.414050578Z ❯ Starting nginx ...
2023-03-24T05:21:55.492552348Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84
2023-03-24T05:21:56.506553043Z ❯ Starting nginx ...
2023-03-24T05:21:56.607830066Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84
2023-03-24T05:21:57.620425211Z ❯ Starting nginx ...
2023-03-24T05:21:57.696218771Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84
2023-03-24T05:21:58.709063156Z ❯ Starting nginx ...

Afaik I don't use this anywhere, at least not that I have configured. Will be reverting back to 2.9.19 (again).

<!-- gh-comment-id:1482271340 --> @pluim003 commented on GitHub (Mar 24, 2023): Tried also release 2.9.21 with no success. Thought I commented but don't see the comment. Just tried 2.9.22 and that gives me: ``` 2023-03-24T05:21:51.209949387Z [3/24/2023] [5:21:51 AM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' 2023-03-24T05:21:51.212162452Z [3/24/2023] [5:21:51 AM] [Global ] › ℹ info Generating SQLite knex configuration 2023-03-24T05:21:51.217380596Z [3/24/2023] [5:21:51 AM] [Global ] › ⬤ debug Wrote db configuration to config file: ./config/production.json 2023-03-24T05:21:52.076553073Z ❯ Starting nginx ... 2023-03-24T05:21:52.165406187Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84 2023-03-24T05:21:53.181088634Z ❯ Starting nginx ... 2023-03-24T05:21:53.270381672Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84 2023-03-24T05:21:54.264271509Z [3/24/2023] [5:21:54 AM] [Migrate ] › ℹ info Current database version: none 2023-03-24T05:21:54.285149086Z ❯ Starting nginx ... 2023-03-24T05:21:54.368614835Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84 2023-03-24T05:21:54.494722806Z [3/24/2023] [5:21:54 AM] [Setup ] › ℹ info Creating a new JWT key pair... 2023-03-24T05:21:55.414050578Z ❯ Starting nginx ... 2023-03-24T05:21:55.492552348Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84 2023-03-24T05:21:56.506553043Z ❯ Starting nginx ... 2023-03-24T05:21:56.607830066Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84 2023-03-24T05:21:57.620425211Z ❯ Starting nginx ... 2023-03-24T05:21:57.696218771Z 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.19 or 0.10.20 required) in /etc/nginx/nginx.conf:84 2023-03-24T05:21:58.709063156Z ❯ Starting nginx ... ```` Afaik I don't use this anywhere, at least not that I have configured. Will be reverting back to 2.9.19 (again).
kerem commented 2026-02-26 07:32:45 +03:00
Author
Owner
Copy link

@pluim003 commented on GitHub (Mar 24, 2023):

O, found the problem (and solved it).
I had a volume in my container to /etc/nginx, so when using this it won't get updated. Removed it from the docker-compose-file and now it's working again. A volume for the data should be sufficient.

Sorry for inconvenience.

<!-- gh-comment-id:1482281537 --> @pluim003 commented on GitHub (Mar 24, 2023): O, found the problem (and solved it). I had a volume in my container to /etc/nginx, so when using this it won't get updated. Removed it from the docker-compose-file and now it's working again. A volume for the data should be sufficient. Sorry for inconvenience.
kerem commented 2026-02-26 07:32:45 +03:00
Author
Owner
Copy link

@dazrave commented on GitHub (Aug 6, 2023):

Wanted to comment that commenting out '/etc/nginx' from my stack and redeploying also worked! Thanks.

<!-- gh-comment-id:1667002631 --> @dazrave commented on GitHub (Aug 6, 2023): Wanted to comment that commenting out '/etc/nginx' from my stack and redeploying also worked! Thanks.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1859
No description provided.