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.

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?

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 table auth (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_deleted int 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