mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-27 02:15:51 +03:00
[GH-ISSUE #193] Container is unhealty and can't access admin interface #169
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#169
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Oujiii on GitHub (Aug 26, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/193
Checklist
jc21/nginx-proxy-manager:latestdocker image? YesYes
Describe the bug
Can't get to the login page
To Reproduce
Steps to reproduce the behavior:
I ran
docker-compose up -din the folder whereconfig.jsonanddocker-compose.ymlare locateddocker-compose.ymlconfig.jsondocker logs npmExpected behavior
Excepted the container to be healthy and the admin interface to be accessible
Operating System
Additional context
Docker version 18.09.8-ce, build 0dd43dd87fd530113bf44c9bba9ad8b20ce4637f
Running inside a VM (KVM) via Proxmox.
Thank you!
@thehawk970 commented on GitHub (Sep 1, 2019):
I have same output,
in addition i have this :
docker logs db 2019-09-01 17:02:31 0 [Note] mysqld (mysqld 10.4.7-MariaDB-1:10.4.7+maria~bionic) starting as process 1 ... 2019-09-01 17:02:31 0 [Note] InnoDB: Using Linux native AIO 2019-09-01 17:02:31 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-09-01 17:02:31 0 [Note] InnoDB: Uses event mutexes 2019-09-01 17:02:31 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2019-09-01 17:02:31 0 [Note] InnoDB: Number of pools: 1 2019-09-01 17:02:31 0 [Note] InnoDB: Using SSE2 crc32 instructions 2019-09-01 17:02:31 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) 2019-09-01 17:02:32 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2019-09-01 17:02:32 0 [Note] InnoDB: Completed initialization of buffer pool 2019-09-01 17:02:32 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2019-09-01 17:02:32 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2019-09-01 17:02:32 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2019-09-01 17:02:32 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2019-09-01 17:02:32 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2019-09-01 17:02:32 0 [Note] InnoDB: Waiting for purge to start 2019-09-01 17:02:32 0 [Note] InnoDB: 10.4.7 started; log sequence number 140060; transaction id 21 2019-09-01 17:02:32 0 [Note] Plugin 'FEEDBACK' is disabled. 2019-09-01 17:02:32 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2019-09-01 17:02:32 0 [Note] Server socket created on IP: '::'. 2019-09-01 17:02:33 0 [Warning] 'user' entry 'root@fe57c7c0ba15' ignored in --skip-name-resolve mode. 2019-09-01 17:02:33 0 [Warning] 'user' entry '@fe57c7c0ba15' ignored in --skip-name-resolve mode. 2019-09-01 17:02:33 0 [Warning] 'proxies_priv' entry '@% root@fe57c7c0ba15' ignored in --skip-name-resolve mode. 2019-09-01 17:02:33 0 [Note] Reading of all Master_info entries succeeded 2019-09-01 17:02:33 0 [Note] Added new Master_info '' to hash table 2019-09-01 17:02:33 0 [Note] mysqld: ready for connections. Version: '10.4.7-MariaDB-1:10.4.7+maria~bionic' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution 2019-09-01 17:02:33 0 [Note] InnoDB: Buffer pool(s) load completed at 190901 17:02:33 2019-09-01 17:02:46 8 [Warning] Aborted connection 8 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:47 9 [Warning] Aborted connection 9 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:48 10 [Warning] Aborted connection 10 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:49 11 [Warning] Aborted connection 11 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:50 12 [Warning] Aborted connection 12 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:52 13 [Warning] Aborted connection 13 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:53 14 [Warning] Aborted connection 14 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:54 15 [Warning] Aborted connection 15 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:55 16 [Warning] Aborted connection 16 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:56 17 [Warning] Aborted connection 17 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:57 18 [Warning] Aborted connection 18 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:58 19 [Warning] Aborted connection 19 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:02:59 20 [Warning] Aborted connection 20 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:00 21 [Warning] Aborted connection 21 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:01 22 [Warning] Aborted connection 22 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:02 23 [Warning] Aborted connection 23 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:03 24 [Warning] Aborted connection 24 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:04 25 [Warning] Aborted connection 25 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:05 26 [Warning] Aborted connection 26 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:06 27 [Warning] Aborted connection 27 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:07 28 [Warning] Aborted connection 28 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:08 29 [Warning] Aborted connection 29 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:09 30 [Warning] Aborted connection 30 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:10 31 [Warning] Aborted connection 31 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:11 32 [Warning] Aborted connection 32 to db: 'unconnected' user: 'unauthenticated' host: '172.21.0.9' (This connection closed normally without authentication) 2019-09-01 17:03:21 0 [Note] mysqld (initiated by: unknown): Normal shutdown 2019-09-01 17:03:21 0 [Note] Event Scheduler: Purging the queue. 0 events 2019-09-01 17:03:21 0 [Note] InnoDB: FTS optimize thread exiting. 2019-09-01 17:03:21 0 [Note] InnoDB: Starting shutdown... 2019-09-01 17:03:21 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool 2019-09-01 17:03:21 0 [Note] InnoDB: Buffer pool(s) dump completed at 190901 17:03:21 2019-09-01 17:03:22 0 [Note] InnoDB: Shutdown completed; log sequence number 140069; transaction id 22 2019-09-01 17:03:22 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2019-09-01 17:03:23 0 [Note] mysqld: Shutdown completemy docker compose :
version: "3" services: app: container_name: app image: jc21/nginx-proxy-manager:2.0.12 restart: always ports: - 80:80 - 81:81 - 443:443 volumes: - ./apps/nginx-proxy/config.json:/app/config/production.json - ./data:/data - ./letsencrypt:/etc/letsencrypt depends_on: - db environment: # if you want pretty colors in your docker logs: - FORCE_COLOR=1 db: image: mariadb:latest container_name: db environment: MYSQL_ROOT_PASSWORD: "npm" MYSQL_DATABASE: "npm" MYSQL_USER: "npm" MYSQL_PASSWORD: "npm" volumes: - ./data/mysql:/var/lib/mysqlBut the same docker-compose on my macos computer works fine :) but not on my remote server
@bpjobin commented on GitHub (Sep 1, 2019):
Same here. Can't get to admin webpage because npm can't connect to db.
2019-09-01 17:39:54 0 [Note] mysqld (mysqld 10.4.7-MariaDB-1:10.4.7+maria~bionic) starting as process 1 ... 2019-09-01 17:39:54 0 [Note] InnoDB: Using Linux native AIO 2019-09-01 17:39:54 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-09-01 17:39:54 0 [Note] InnoDB: Uses event mutexes 2019-09-01 17:39:54 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2019-09-01 17:39:54 0 [Note] InnoDB: Number of pools: 1 2019-09-01 17:39:54 0 [Note] InnoDB: Using SSE2 crc32 instructions 2019-09-01 17:39:54 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) 2019-09-01 17:39:54 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2019-09-01 17:39:54 0 [Note] InnoDB: Completed initialization of buffer pool 2019-09-01 17:39:54 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2019-09-01 17:39:54 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=139881 [s6-init] making user provided files available at /var/run/s6/etc...exited 0. 2019-09-01 17:39:54 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2019-09-01 17:39:54 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2019-09-01 17:39:54 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2019-09-01 17:39:54 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. 2019-09-01 17:39:56 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2019-09-01 17:39:56 0 [Note] InnoDB: Waiting for purge to start 2019-09-01 17:39:56 0 [Note] InnoDB: 10.4.7 started; log sequence number 139890; transaction id 21 2019-09-01 17:39:56 0 [Note] Plugin 'FEEDBACK' is disabled. 2019-09-01 17:39:56 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2019-09-01 17:39:56 0 [Note] Server socket created on IP: '::'. 2019-09-01 17:39:56 0 [Note] InnoDB: Buffer pool(s) load completed at 190901 17:39:56 2019-09-01 17:39:56 0 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2019-09-01 17:39:56 0 [Note] Reading of all Master_info entries succeeded 2019-09-01 17:39:56 0 [Note] Added new Master_info '' to hash table 2019-09-01 17:39:56 0 [Note] mysqld: ready for connections. Version: '10.4.7-MariaDB-1:10.4.7+maria~bionic' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution [9/1/2019] [5:39:57 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND mariadb mariadb:3306 [9/1/2019] [5:39:58 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND mariadb mariadb:3306@thehawk970 commented on GitHub (Sep 1, 2019):
your error came from mariadb is not found, what is the name of the container ? maybe db instead of mariadb (check your docker-compose and the config.json) :)
thehawk970
@Oujiii commented on GitHub (Sep 1, 2019):
@bpjobin
Well, to be honest it fails even with the example docs. For me I solved using another type of mariadb for this setup.
I used
jc21/mariadb-ariathat is a container maintained by the same maintainer of this project and works as intended.I'm gonna close this issue now because I've tried in a dozen VMs and all worked with the new container, so that's it.
@bpjobin commented on GitHub (Sep 4, 2019):
Actually, I'd like to keep this issue open if possible. I haven't been able to launch npm properly yet whether I'm using mysql, mariadb or jc21/mariadb-aria.
@thehawk970, here's my config.
config
docker-compose.yaml
logs
@Oujiii commented on GitHub (Sep 4, 2019):
Alright, I'm gonna leave this open to maybe get more traction to solve it for you.
@thehawk970 commented on GitHub (Sep 5, 2019):
my personal error comes from an existing /var/lib on the host, once all has been delete and reinstall
all works fine :)
@thehawk970 commented on GitHub (Sep 5, 2019):
Have you tried "db" instead of "mariadb" (i guess yes but maybe :D )
@thehawk970 commented on GitHub (Sep 5, 2019):
with docker run -it /bin/sh on your npm container, can you ping the "mariadb" or "db" container (ping db)
@bpjobin commented on GitHub (Sep 6, 2019):
YEEEESSSS!!
It was in fact db instead of mariadb.
ping mariadbreturned unknown host. I guess I didn't wait long enough last time because I already tried that too. At first it was giving me ECONNREFUSED.But I let it run for a few minutes and it finally went through!
Thanks very much I've been working on this for days!
This issue may now be closed.
@Oujiii commented on GitHub (Sep 6, 2019):
I guess both of our problems were different. Glad it was solved. Thank @thehawk970 for all the help!
@varunsridharan commented on GitHub (Oct 26, 2019):
This worked for me :-)
@brusezot commented on GitHub (Jan 17, 2020):
i'm the same probleme during one minute, can you explain to me why ?
db_1 | Version: '10.4.11-MariaDB-1:10.4.11+maria~bionic' socket: '/var/run/mysqld/mysqld.sock' port: 0 mariadb.org binary distribution
app_1 | [1/17/2020] [1:27:58 AM] [Global ] › ✖ error connect ECONNREFUSED 172.21.0.2:3306
db_1 | 2020-01-17 01:27:58+00:00 [Note] [Entrypoint]: Temporary server started.
app_1 | [1/17/2020] [1:27:59 AM] [Global ] › ✖ error connect ECONNREFUSED 172.21.0.2:3306
app_1 | [1/17/2020] [1:28:00 AM] [Global ] › ✖ error connect ECONNREFUSED 172.21.0.2:3306
app_1 | [1/17/2020] [1:28:01 AM] [Global ] › ✖ error connect ECONNREFUSED 172.21.0.2:3306
app_1 | [1/17/2020] [1:28:02 AM] [Global ] › ✖ error connect ECONNREFUSED 172.21.0.2:3306
app_1 | [1/17/2020] [1:28:03 AM] [Global ] › ✖ error connect ECONNREFUSED 172.21.0.2:3306
app_1 | [1/17/2020] [1:28:04 AM] [Global ] › ✖ error connect ECONNREFUSED 172.21.0.2:3306
@johnweland commented on GitHub (Sep 22, 2020):
What I am noticing by checking the logs is app is having the connection error above. However logs for the db container show
standard_init_linux.go:211: exec user process caused "exec format error"which seems to be the case when its trying to use an image build for the wrong architecture. I am using thejc21/mariadb-aria:latestimage from the docs.