Bad Gateway on login attempt

[adman120]

On container launch via the recommended compose file, I am unable to get past the login screen as it tells me I have a bad gateway every time I try and log in.

[ghost]

Hello guys, any news regarding this topic?

[Xantios]

I know this isn't much of a solution, but I had this very same issue and just let the container run for a couple of hours (as I went to bed) and now I can log in.

Maybe there is a bug in the initial startup?

[ghost]

I still can't login. I'm afraid that i've configured it wrong, because i am new using docker.

[theniwo]

having the same issue here. running on a pi4 with buster. I read app_1 | [3/4/2020] [12:48:41 PM] [Global ] › ✖ error create tableauth(idint unsigned not null auto_increment primary key,created_ondatetime not null,modified_ondatetime not null,user_idint unsigned not null,typevarchar(30) not null,secretvarchar(255) not null,metajson not null,is_deletedint unsigned not null default '0') - ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'json not null,is_deletedint unsigned not null default '0')' at line 1 app_1 | [3/4/2020] [12:48:42 PM] [Migrate ] › ℹ info Current database version: none app_1 | [3/4/2020] [12:48:42 PM] [Migrate ] › ℹ info [initial-schema] Migrating Up... app_1 | migration file "20180618015850_initial.js" failed app_1 | migration failed with error: create tableauth(idint unsigned not null auto_increment primary key,created_ondatetime not null,modified_ondatetime not null,user_idint unsigned not null,typevarchar(30) not null,secretvarchar(255) not null,metajson not null,is_deletedint unsigned not null default '0') - ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'json not null,is_deletedint unsigned not null default '0')' at line 1 when starting docker-compose without -d

[jc21]

To debug everyone's problems I would need to see the docker-compose file you're using and output of both the NPM container and the DB container, if you're using it and not using a direct connection to a mysql/maria host.

The JSON field error suggests that the mariadb version is old? what version are you running?

[theniwo]

Config Errors Errors with arm64v8/mariadb Docker Version

[jc21]

@theniwo so from the first error logs, you're using jsurf/rpi-mariadb maria image which is v10.0. JSON field support was added in maria 10.2.

The second error log has standard_init_linux.go:211: exec user process caused "exec format error" which is a clear indicator that you're using the wrong architecture image for your system. When using raspbian, no matter if it's rpi3 or 4, you need armv7. I can see that the official mariadb account doesn't make v7 versions. I'll have a stab at making my version multiarch.

[jc21]

Try using jc21/mariadb-aria:10.4 here. Should work for Raspbian as well. Let me know how you go!

[mark-130]

I'm having the same issues and getting the following error in portainer (container showing as unhealthy). I'm using linux as a base

Last output | parse error: Invalid numeric literal at line 1, column 7 NOT OK

[jc21]

A very cryptic message. is that from the db container or npm container? If it was a sql error there would be an error message in the npm container. But if it was an error that happens in the db container on start, it might be an issue of incompatible database versions.

[theniwo]

Try using jc21/mariadb-aria:10.4 here. Should work for Raspbian as well. Let me know how you go!

Thanks, but I get the db_1 | standard_init_linux.go:211: exec user process caused "exec format error" error message on this too.

Here's my new config.

[jc21]

@theniwo ok it's time to debug your OS. Can you paste the output of this command:

cat /proc/cpuinfo

[theniwo]

@theniwo ok it's time to debug your OS. Can you paste the output of this command:

cat /proc/cpuinfo

/proc/cpuinfo

EDIT: Having the same result on a raspberry pi 3 /proc/cpuinfo

[Delvien]

Im having the same issue. same config as the OP. Same raspberry pi CPU

[theniwo]

Versions:

Raspbian 10 buster - 4.19.102-v7l+

docker-ce          5:19.03.7~3-0~raspbian-buster  armhf
docker-ce-cli      5:19.03.7~3-0~raspbian-buster  armhf
docker-compose     1.21.0-3                       all

Client: Docker Engine - Community
 Version:           19.03.7
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        7141c19
 Built:             Wed Mar  4 01:55:10 2020
 OS/Arch:           linux/arm
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.7
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       7141c19
  Built:            Wed Mar  4 01:49:01 2020
  OS/Arch:          linux/arm
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

[drewbeer]

this is because you are all missing the config. the instructions don't include it.

rm -rf config.json (its a dir it shouldn't be)

create a new config.json with

{
  "database": {
    "engine": "mysql",
    "host": "db",
    "name": "npm",
    "user": "npm",
    "password": "npm",
    "port": 3306
  }
}

and that will fix it.

[theniwo]

I have that config.json as a file in the same directory as the docker-compose.yml. I did not clone from the git, I created the files manually

[zerpex]

Hi, Got the same issue: docker logs tool-nginx_db standard_init_linux.go:211: exec user process caused "exec format error" standard_init_linux.go:211: exec user process caused "exec format error" standard_init_linux.go:211: exec user process caused "exec format error"

cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 10 (v7l) BogoMIPS : 3.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc09 CPU revision : 10

I don't know if it can help, but it is working with the following image: https://hub.docker.com/r/yobasystems/alpine-mariadb/tags

Regards

[theniwo]

I get an ER_ACCESS_DENIED_NO_PASSWORD_ERROR error on this image

[jc21]

Funny, because I am using that same image as a base for mine: https://github.com/jc21/docker-mariadb-aria/blob/master/Dockerfile

[jdkruzr]

This issue still exists for anyone who starts from the instructions. I tried @drewbeer 's suggestion, but that didn't fix it either. The issue appears to be that it expects something on the host to be running on port 3000 (node, I guess?) but it isn't.

[miguelwill]

This issue still exists for anyone who starts from the instructions. I tried @drewbeer 's suggestion, but that didn't fix it either. The issue appears to be that it expects something on the host to be running on port 3000 (node, I guess?) but it isn't.

check the log of the nginx-proxy-manager container to see if the npm process loads the configuration or shows an error

[adman120]

Tfw you start the thread but contribute 0 to it.

On Mon, Mar 23, 2020 at 9:37 PM Miguelwill notifications@github.com wrote:

This issue still exists for anyone who starts from the instructions. I tried @drewbeer https://github.com/drewbeer 's suggestion, but that didn't fix it either. The issue appears to be that it expects something on the host to be running on port 3000 (node, I guess?) but it isn't.

check the log of the nginx-proxy-manager container to see if the npm process loads the configuration or shows an error

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jc21/nginx-proxy-manager/issues/310#issuecomment-602956406, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4EKQQWKRFGY2EFSRS4G2LRJAFEDANCNFSM4K5W4CGA .

[theniwo]

I managed to get it running with yobasystems/alpine-mariadb

[drewbeer]

ok so i tested this again and yes its doesn't create the config properly.

fresh install, on startup...

app_1 | [3/24/2020] [11:10:02 PM] [Global ] › ✖ error Config file /app/config/production.json cannot be read. Error code is: EISDIR. Error message is: EISDIR: illegal operation on a directory, read Error: Config file /app/config/production.json cannot be read. Error code is: EISDIR. Error message is: EISDIR: illegal operation on a directory, read

stop the containers and list the files

drwxr-xr-x 2 root root 4096 Mar 25 00:09 config.json drwxr-xr-x 8 root root 4096 Mar 25 00:10 data -rw-r--r-- 1 root root 480 Mar 25 00:08 docker-compose.yaml drwxr-xr-x 2 root root 4096 Mar 25 00:09 letsencrypt

all dirs are created correctly however the config.json is now a dir also... which is wrong...

so rm -rf config.json, edit it and then put in

{
  "database": {
    "engine": "mysql",
    "host": "db",
    "name": "npm",
    "user": "npm",
    "password": "npm",
    "port": 3306
  }
}

save docker-compose down docker-compose up -d

fixed.

here is my compose pulled straight from the site

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./config.json:/app/config/production.json
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
  db:
    image: 'jc21/mariadb-aria:10.4'
    environment:
      MYSQL_ROOT_PASSWORD: 'npm'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: 'npm'
    volumes:
      - ./data/mysql:/var/lib/mysql

[jdkruzr]

I’d like to add: if you, like me, thought this would be fine to run in an lxc container with nesting turned on and the appropriate AppArmor flags set:

lxc.apparmor.profile: unconfined lxc.cgroup.devices.allow: a lxc.cap.drop:

then I regret to inform you that we were both wrong, because nginx-proxy-manager exhibited the same symptoms in this configuration when I correctly set up the config.json file. I had to run it in a VM instead. Can’t speak to why; I don’t grok Docker networking.

On Mar 24, 2020, at 7:14 PM, Drew notifications@github.com wrote:

ok so i tested this again and yes its doesn't create the config properly.

fresh install, on startup...

app_1 | [3/24/2020] [11:10:02 PM] [Global ] › ✖ error Config file /app/config/production.json cannot be read. Error code is: EISDIR. Error message is: EISDIR: illegal operation on a directory, read Error: Config file /app/config/production.json cannot be read. Error code is: EISDIR. Error message is: EISDIR: illegal operation on a directory, read

stop the containers and list the files

drwxr-xr-x 2 root root 4096 Mar 25 00:09 config.json drwxr-xr-x 8 root root 4096 Mar 25 00:10 data -rw-r--r-- 1 root root 480 Mar 25 00:08 docker-compose.yaml drwxr-xr-x 2 root root 4096 Mar 25 00:09 letsencrypt

all dirs are created correctly however the config.json is now a dir also... which is wrong...

so rm -rf config.json, edit it and then put in

{ "database": { "engine": "mysql", "host": "db", "name": "npm", "user": "npm", "password": "npm", "port": 3306 } } save docker-compose down docker-compose up -d

fixed.

here is my compose pulled straight from the site

version: '3' services: app: image: 'jc21/nginx-proxy-manager:latest' ports:

• '80:80'
• '81:81'
• '443:443' volumes:
• ./config.json:/app/config/production.json
• ./data:/data
• ./letsencrypt:/etc/letsencrypt db: image: 'jc21/mariadb-aria:10.4' environment: MYSQL_ROOT_PASSWORD: 'npm' MYSQL_DATABASE: 'npm' MYSQL_USER: 'npm' MYSQL_PASSWORD: 'npm' volumes:
• ./data/mysql:/var/lib/mysql — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jc21/nginx-proxy-manager/issues/310#issuecomment-603552819, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEW5VT2TAWWNHJ7DJCXCS3RJE5GTANCNFSM4K5W4CGA.

[lopugit]

I get this in my logs of the app container

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[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.
[3/25/2020] [5:29:15 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:16 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:17 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:18 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:19 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:20 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:21 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:22 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:23 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:24 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:25 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:26 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:27 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:28 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:29 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:30 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:31 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:32 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:33 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:34 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:35 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:36 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:37 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:38 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:39 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:40 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:41 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:42 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:43 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:44 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:45 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:46 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:47 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:48 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:49 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:50 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:51 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:52 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:53 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:54 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:55 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:56 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:57 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:58 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:29:59 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:00 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:01 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:02 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:03 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:04 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:05 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:06 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:07 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:08 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:09 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:10 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:11 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:12 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:13 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:14 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:15 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:16 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:17 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:18 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:19 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:20 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:21 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:22 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:23 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:24 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:25 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:26 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:27 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:28 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:29 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:30 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:31 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:32 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:33 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:34 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:35 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:36 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:37 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:38 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:39 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:40 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:41 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:42 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:43 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:44 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:45 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:46 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:47 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:48 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:49 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:50 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:51 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:52 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:53 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:54 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:55 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:56 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:57 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:58 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:30:59 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:31:00 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:31:01 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:31:02 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:31:03 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:31:04 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:31:05 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:31:06 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:31:07 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0
[3/25/2020] [5:31:08 AM] [Global   ] › ✖  error     Packets out of order. Got: 1 Expected: 0

And this from my sql container

[i] mysqld not found, creating....
[i] MySQL directory already present, skipping creation
2020-03-25  5:28:43 0 [Note] /usr/bin/mysqld (mysqld 10.4.10-MariaDB) starting as process 1 ...
2020-03-25  5:28:43 0 [Note] InnoDB: Using Linux native AIO
2020-03-25  5:28:43 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-25  5:28:43 0 [Note] InnoDB: Uses event mutexes
2020-03-25  5:28:43 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-03-25  5:28:43 0 [Note] InnoDB: Number of pools: 1
2020-03-25  5:28:43 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-25  5:28:43 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2020-03-25  5:28:43 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-03-25  5:28:43 0 [Note] InnoDB: Completed initialization of buffer pool
2020-03-25  5:28:43 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-03-25  5:28:45 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-03-25  5:28:45 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-03-25  5:28:45 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-03-25  5:28:45 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2020-03-25  5:28:45 0 [Note] InnoDB: Waiting for purge to start
2020-03-25  5:28:45 0 [Note] InnoDB: 10.4.10 started; log sequence number 126551; transaction id 15
2020-03-25  5:28:45 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2020-03-25  5:28:45 0 [Note] InnoDB: Buffer pool(s) load completed at 200325  5:28:45
2020-03-25  5:28:45 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-03-25  5:28:45 0 [Note] Server socket created on IP: '::'.
2020-03-25  5:28:45 0 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
2020-03-25  5:28:45 6 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
2020-03-25  5:28:45 0 [Note] Reading of all Master_info entries succeeded
2020-03-25  5:28:45 0 [Note] Added new Master_info '' to hash table
2020-03-25  5:28:45 0 [Note] /usr/bin/mysqld: ready for connections.
Version: '10.4.10-MariaDB'  socket: '/run/mysqld/mysqld.sock'  port: 3306  MariaDB Server
2020-03-25  5:29:15 8 [Warning] Aborted connection 8 to db: 'unconnected' user: 'unauthenticated' host: '172.18.0.3' (This connection closed normally without authentication)
2020-03-25  5:29:16 9 [Warning] Aborted connection 9 to db: 'unconnected' user: 'unauthenticated' host: '172.18.0.3' (This connection closed normally without authentication)
2020-03-25  5:29:17 10 [Warning] Aborted connection 10 to db: 'unconnected' user: 'unauthenticated' host: '172.18.0.3' (This connection closed normally without authentication)
2020-03-25  5:29:18 11 [Warning] Aborted connection 11 to db: 'unconnected' user: 'unauthenticated' host: '172.18.0.3' (This connection closed normally without authentication)
etc.. connection 11, 12, 13 ..... up to 400

[lopugit]

Ok so I can confirm as I've read elsewhere, letting it sit for some time (I went to a friends for a few hours) and coming back, it'll be working, magically... I still wonder what the problem is though.

My docker has been a little slow to react because I moved it onto an HDD on AWS. So maybe it's just the slow HDD messing with something.

But yeah, if you leave it for a few hours it'll work.

Actually when I built it on my local machine, SSD, it had the same problem and I'm guessing it would have fixed itself too. I really wonder what causes this delay

[lopugit]

Ok so now I only had to wait about 10 minutes, interesting!

[satanahell]

Hello everyone,

I got a similar issue i guess on Centos 8 but with a different origin

• Issue : Bad gateway for every logon try on http://localhost:81/login or http://172.2.0.3:81/login
• Possible origin: app_1 logs show cannot connect 'EHOSTUNREACH 172.23.0.2:3306) and mariadb seems running fine on port 3306 on db_1 !

After running the setup tutorial this is where i am :

• Got my two files config.json and docker-compose.yml.
• This is an ls -la and a pwd.
• docker-compose up result
• the config.json file remain not alterred (not encrypted) after starting the application.
• This is the logs output of the both docker containers app db.
• Docker version info.

I'm available if you need further information. Thanks for your help,

[wwboynton]

I could be mistaken, but it seems like the first run of the container is creating a directory called config.json instead of a file. It's possible that it's supposed to create a file and then input the default config contents, or perhaps the user is supposed to do it themselves, but either way it seems like completing a successful setup right now means:

docker-compose up -d
# Wait for it to come up and scaffold the directory/file structure in the mount...
docker-compose stop
rmdir config.json
vi config.json
# input the default config from [the setup](https://nginxproxymanager.com/setup/), modifying if necessary
docker-compose up -d

(pardon any typos in that sample, I hope you get the idea)

EDIT: For what it's worth, on my Raspi4 running Ubuntu 18.04.4LTS, I had issues with the suggested DB image. I switched to the official MariaDB image of the same version, changing my root user name to root to avoid duplication. I changed that value in the docker-compose.yml and again in the config.json to use root as the user, and ran docker-compose down before bringing it back up to purge the old containers. I'm all up and running now. The previous MariaDB container was dying immediately with:

db_1   | standard_init_linux.go:211: exec user process caused "exec format error"

and I'd prefer to just use the official DB images anyway wherever I can.

[satanahell]

@wwboynton thanks for the reply.

I also saw the config.json directory been created on the first run but only because i made a mistake in the docker-compose file. I have repeated many times the same operation without this mistake and all was going like a charm, except this database connection issue. But to be sure, i exactly tried what you've suggested, and i got the same error.

As you mentioned, i will try to switch to the official database container but i'm not quite familiar with docker.

Thanks for the advice !

[lopugit]

Wait 10 minutes or 3 hours it should Magically start working

On Fri., 27 Mar. 2020, 9:49 pm SaTaNaeL, notifications@github.com wrote:

@wwboynton https://github.com/wwboynton thanks for the reply.

I also saw the config.json directory been created on the first run but only because i made a mistake in the docker-compose file. I have repeated many times the same operation without this mistake and all was going like a charm, except this database connection issue. But to be sure, i exactly tried what you've suggested, and i got the same error.

As you mentioned, i will try to switch to the official database container but i'm not quite familiar with docker.

Thanks for the advice !

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jc21/nginx-proxy-manager/issues/310#issuecomment-604934950, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADH7OBTBKLT6NNCQH7OLY7DRJSADZANCNFSM4K5W4CGA .

[satanahell]

@lopugit i already tried this one all night long! ^_^ But with no success at the moment.

[satanahell]

Hello everyone,

I got a similar issue i guess on Centos 8 but with a different origin

• Issue : Bad gateway for every logon try on http://localhost:81/login or http://172.2.0.3:81/login
• Possible origin: app_1 logs show cannot connect 'EHOSTUNREACH 172.23.0.2:3306) and mariadb seems running fine on port 3306 on db_1 !

After running the setup tutorial this is where i am :

• Got my two files config.json and docker-compose.yml.
• This is an ls -la and a pwd.
• docker-compose up result
• the config.json file remain not alterred (not encrypted) after starting the application.
• This is the logs output of the both docker containers app db.
• Docker version info.

Since my last post, i figured out how to log on on each container to make some ping, all is fine obviously but in docker-compose events i got container exec-die about the rproxy_app_1.

I also tried to change db container to official image but i'm not use to docker and i would to check if i'm doing this the good way. @wwboynton can you please post your docker compose file with the official mariadb image ?

I still looking for a solution because my homelab really need a reverse proxy with a GUI to expose and secure many HTTP/HTTPS web servers (same ports/ diff internal IP) !!

[joeyaben]

I managed to get it running with yobasystems/alpine-mariadb

Thanks, this also fixed the issue for me

[Wonderbox2000]

Hi, I am still having the same issue. I just tried with yobasystems/alpine-mariadb .=> same result in data/logs/error.log:

2020/04/05 06:51:04 [error] 226#226: *2159 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "127.0.0.1:81"

Can someone please guide me ?

So far I have also tried the quick-setup and the full-setup

But I have probably missed something.

Running on Ubuntu 18.04

[miguelwill]

Are you sure you have created the configuration file and added it to the NPM image mount ? Compare what you did with the instructions https://nginxproxymanager.com/setup/

[unixbird]

Having the same issues here and tried using a different mysql image. still bad gateway. I'll wait a little bit and see what happens

[unixbird]

Alright so it works. What I've found is

1. Create the config.json before you make the servers and run docker-compose
2. in the docker compose use the yobasystems/alpine-mariadb image instead of the default (I'm not sure if this actually affects anything but I used it and it works so I'll stick to it).
3. You definitely need to wait a moment. I noticed after when it works it actually put in RSA keys into the config.json so that may be the reason you need to wait as it is using entropy to generate them.

That's seemingly how mine works now

[Xantios]

So it basically comes down to making a PR to the docs so they explain how to create the json file, point to it in the docker-compose file and have to wait for it to populate?

[jpmurray]

EDIT: Nevermind me, @unixbird mentionned it does! I'll just wait!

Full instructions page states that

After the first run of the application, the config file will be altered to include generated encryption keys unique to your installation.

Can anyone confirm to me that checking the config.json we created has additionnal entries when they can log in? I'm hitting the same trouble as everyone (having created my config.json file before as I am following full guide), but the file stays exactly the same.

[jpmurray]

Adding my voice to this, but using the proposed jc21/mariadb-aria:10.4 image, checking docker ps the database container status was always Restarting (1) 1 second ago after ~10 seconds. Switching to the alpine-mariadb database solved it instantly.

[jc21]

Why was the jc21/mariadb-aria:10.4 container restarting though? What errors were you able to see? I'm using this exact image in production (amd64) and don't have problems.

[jpmurray]

What errors were you able to see?

None that I could see, although I might be missing places where to look for said errors, I'm still not entirely versed into Docker's inner workings. What would be the usual place to catch thoses? I'll go and try to reproduce the problem.

[delacosta456]

hi all i was also having this issue and reading some issues (this too didn't help) but bellow is what definitely worked:

• it looks like the port 81 (may be after several tries) stay in locked or occupied by a process which make the app container sometimes stay in healthy state while database container boot correctly. This mean the port 81 needed to be "free-ed". So WORKAROUND on my ubuntu, step by step :

1. (from the npm folder where config and yaml file are ) in terminal i run : sudo docker-compose down

2. then sudo kill -9 sudo lsof -t -i:81 or sudo kill -9 $(sudo lsof -t -i:9001)

3. now sudo docker-compose up -d

4. IMPORTANT STEP wait for at least 10 to 15 seconds before refreshing you browser on http://127.0.0.1:81

hope this will help (sorry for my English i'am french)

[wimmme]

For me on a RPI 3 running Hypriot

db:
image: mariadb:latest

does not work, but this does:

db:
image: yobasystems/alpine-mariadb:armhf

[leaderit]

1. run docker exec -ti nginx-proxy-manager /bin/bash where 'nginx-proxy-manager' is the name of your container
2. run node index SEE ERROR. Usualy : Error: Cannot parse config file: '/app/config/production.json': SyntaxError: Unexpected token } in JSON or something like this 3.FIX FILE OR ERROR
3. exit shell and restart the docker container
4. PROFIT!

[sbl05]

I had the same issues on my Raspberry 4 (armv7l) and solved it switching to SQLite using the following configuration:

version: "3"
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: always
    ports:
      - '80:80'
      - '443:443'
      - '81:81'
    environment:
      DB_SQLITE_FILE: "/data/npm.sqlite"
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

[Subline-75]

What I needed to work this it out (bad gateway on the login page): https://www.youtube.com/watch?v=ZrS3IT7HG2Y&

Create my first SQL user & database : 👍