starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #255] Docker image unable to start #223

New issue

Closed

opened 2026-02-26 06:31:36 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 06:31:36 +03:00

Owner

Originally created by @s4b3rt0oth on GitHub (Dec 11, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/255

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, I'm sure.
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
Not Applicable.

Describe the bug

A clear and concise description of what the bug is.
When using the installation instructions (doc/example) the "nginxproxymanager_app_1" container fails to start.
What version of Nginx Proxy Manager is reported on the login page?
Not available.

To Reproduce
Steps to reproduce the behavior:

Pull the doc/example folder.
Navigate to folder and run docker-compose up -d
Notice the DB container starts but the app container fails to start with the error:

App container docker logs:

Uncaught Error: Cannot find module '/app/node_modules/nodemon/bin/nodemon.js'

FROM
Function.Module._resolveFilename (internal/modules/cjs/loader.js:584:5)
Function.Module._load (internal/modules/cjs/loader.js:508:25)
Function.Module.runMain (internal/modules/cjs/loader.js:754:12)
startup (internal/bootstrap/node.js:283:19)
bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
Uncaught Error: Cannot find module '/app/node_modules/nodemon/bin/nodemon.js'

FROM
Function.Module._resolveFilename (internal/modules/cjs/loader.js:584:5)
Function.Module._load (internal/modules/cjs/loader.js:508:25)
Function.Module.runMain (internal/modules/cjs/loader.js:754:12)
startup (internal/bootstrap/node.js:283:19)
bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)`

DB container docker logs:

MySQL init process done. Ready for start up.

2019-12-11 17:10:13 0 [Note] mysqld (mysqld 10.3.14-MariaDB-1:10.3.14+maria-bionic) starting >as process 1 ...
2019-12-11 17:10:13 0 [Note] Plugin 'InnoDB' is disabled.
2019-12-11 17:10:13 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-12-11 17:10:13 0 [Note] Server socket created on IP: '::'.
2019-12-11 17:10:13 0 [Warning] 'proxies_priv' entry '@% root@93c31025b30d' ignored in -->skip-name-resolve mode.
2019-12-11 17:10:13 0 [Note] Reading of all Master_info entries succeded
2019-12-11 17:10:13 0 [Note] Added new Master_info '' to hash table
2019-12-11 17:10:13 0 [Note] mysqld: ready for connections.
Version: '10.3.14-MariaDB-1:10.3.14+maria~bionic' socket: '/var/run/mysqld/mysqld.sock' port: >3306 mariadb.org binary distribution

Expected behavior
I expected the containers to start.

Operating System

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Additional context
Docker version 19.03.5, build 633a0ea838

Originally created by @s4b3rt0oth on GitHub (Dec 11, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/255 **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, I'm sure. - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? Not Applicable. **Describe the bug** - A clear and concise description of what the bug is. When using the installation instructions (doc/example) the "nginxproxymanager_app_1" container fails to start. - What version of Nginx Proxy Manager is reported on the login page? Not available. **To Reproduce** Steps to reproduce the behavior: 1. Pull the doc/example folder. 2. Navigate to folder and run `docker-compose up -d` 3. Notice the DB container starts but the app container fails to start with the error: App container docker logs: >Uncaught Error: Cannot find module '/app/node_modules/nodemon/bin/nodemon.js' > >FROM >Function.Module._resolveFilename (internal/modules/cjs/loader.js:584:5) >Function.Module._load (internal/modules/cjs/loader.js:508:25) >Function.Module.runMain (internal/modules/cjs/loader.js:754:12) >startup (internal/bootstrap/node.js:283:19) >bootstrapNodeJSCore (internal/bootstrap/node.js:622:3) >Uncaught Error: Cannot find module '/app/node_modules/nodemon/bin/nodemon.js' > >FROM >Function.Module._resolveFilename (internal/modules/cjs/loader.js:584:5) >Function.Module._load (internal/modules/cjs/loader.js:508:25) >Function.Module.runMain (internal/modules/cjs/loader.js:754:12) >startup (internal/bootstrap/node.js:283:19) >bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)` DB container docker logs: >MySQL init process done. Ready for start up. > >2019-12-11 17:10:13 0 [Note] mysqld (mysqld 10.3.14-MariaDB-1:10.3.14+maria-bionic) starting >as process 1 ... >2019-12-11 17:10:13 0 [Note] Plugin 'InnoDB' is disabled. >2019-12-11 17:10:13 0 [Note] Plugin 'FEEDBACK' is disabled. >2019-12-11 17:10:13 0 [Note] Server socket created on IP: '::'. >2019-12-11 17:10:13 0 [Warning] 'proxies_priv' entry '@% root@93c31025b30d' ignored in -->skip-name-resolve mode. >2019-12-11 17:10:13 0 [Note] Reading of all Master_info entries succeded >2019-12-11 17:10:13 0 [Note] Added new Master_info '' to hash table >2019-12-11 17:10:13 0 [Note] mysqld: ready for connections. >Version: '10.3.14-MariaDB-1:10.3.14+maria~bionic' socket: '/var/run/mysqld/mysqld.sock' port: >3306 mariadb.org binary distribution **Expected behavior** I expected the containers to start. **Operating System** >DISTRIB_ID=Ubuntu >DISTRIB_RELEASE=16.04 >DISTRIB_CODENAME=xenial >DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS" >NAME="Ubuntu" >VERSION="16.04.3 LTS (Xenial Xerus)" >ID=ubuntu >ID_LIKE=debian >PRETTY_NAME="Ubuntu 16.04.3 LTS" >VERSION_ID="16.04" >HOME_URL="http://www.ubuntu.com/" >SUPPORT_URL="http://help.ubuntu.com/" >BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" >VERSION_CODENAME=xenial >UBUNTU_CODENAME=xenial **Additional context** `Docker version 19.03.5, build 633a0ea838`

kerem

2026-02-26 06:31:36 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:31:37 +03:00

Author

Owner

@s4b3rt0oth commented on GitHub (Dec 11, 2019):

OK... my bad. In my sleep deprivation I forgot to navigate to (doc/example). This is not an issue, closing.

@s4b3rt0oth commented on GitHub (Dec 11, 2019): OK... my bad. In my sleep deprivation I forgot to navigate to (doc/example). This is not an issue, closing.

No milestone

No project

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#223

No description provided.

Rows
Columns