Unable to login - /api/tokens returns Bad Gateway

[thjendk]

Describe the bug
After setting up the docker container, I am able to access the login page on port 81. However, when trying to login, the /api/token throws a bad request, and makes me unable to login.
I have tried to recreate the container, but with no effect.

To Reproduce
Steps to reproduce the behavior:

1. Copy the contents of /doc/example
2. Run docker-compose -d
3. Access localhost:81
4. Try to login using the default credentials
5. Login throws bad request

Screenshots

Operating System
Ubuntu 18.04

[thjendk]

It looks like the issue might be down to an authentication error on the database.
The docker container for the nginx proxy manager throws the following error:
[2/21/2020] [12:24:21 PM] [Global ] › ✖ error connect ECONNREFUSED 172.20.0.2:3306
How is this fixable?

[jc21]

Depends on how you’ve set up your deployment. Paste your docker compose file if you can.

[thjendk]

The docker-compose file is identical to the example:

version: "3"
services:
  app:
    image: jc21/nginx-proxy-manager:latest
    restart: always
    ports:
      - 80:80
      - 81:81
      - 443:443
    volumes:
      - ./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
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: "npm"
      MYSQL_DATABASE: "npm"
      MYSQL_USER: "npm"
      MYSQL_PASSWORD: "npm"
    volumes:
      - ./data/mysql:/var/lib/mysql

I have placed the files under /home/user/apps/nginx. Is it possible that the relative path mapping of the docker-compose file somehow prevents it from finding the correct configuration?

[jc21]

Ok cool so the config file should have the host set to “db”. If so and still not working, maybe the logs of the db container have a clue

[thjendk]

Contents of config.json, located in the same folder as docker-compose:

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

Docker logs from db container:

2020-02-21 11:52:09+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.4.12+maria~bionic started.
2020-02-21 11:52:09+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2020-02-21 11:52:09+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.4.12+maria~bionic started.
2020-02-21 11:52:09+00:00 [Note] [Entrypoint]: Initializing database files


PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following commands:

'/usr/bin/mysqladmin' -u root password 'new-password'
'/usr/bin/mysqladmin' -u root -h  password 'new-password'

Alternatively you can run:
'/usr/bin/mysql_secure_installation'

which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.

See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.

Please report any problems at http://mariadb.org/jira

The latest information about MariaDB is available at http://mariadb.org/.
You can find additional information about the MySQL part at:
http://dev.mysql.com
Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/

2020-02-21 11:55:05+00:00 [Note] [Entrypoint]: Database files initialized
2020-02-21 11:55:05+00:00 [Note] [Entrypoint]: Starting temporary server
2020-02-21 11:55:05+00:00 [Note] [Entrypoint]: Waiting for server startup
2020-02-21 11:55:05 0 [Note] mysqld (mysqld 10.4.12-MariaDB-1:10.4.12+maria~bionic) starting as process 122 ...
2020-02-21 11:55:05 0 [Note] InnoDB: Using Linux native AIO
2020-02-21 11:55:05 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-02-21 11:55:05 0 [Note] InnoDB: Uses event mutexes
2020-02-21 11:55:05 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-02-21 11:55:05 0 [Note] InnoDB: Number of pools: 1
2020-02-21 11:55:05 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-02-21 11:55:05 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2020-02-21 11:55:05 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2020-02-21 11:55:05 0 [Note] InnoDB: Completed initialization of buffer pool
2020-02-21 11:55:05 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-02-21 11:55:05 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-02-21 11:55:05 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-02-21 11:55:05 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-02-21 11:55:05 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2020-02-21 11:55:05 0 [Note] InnoDB: 10.4.12 started; log sequence number 61560; transaction id 21
2020-02-21 11:55:05 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2020-02-21 11:55:05 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-02-21 11:55:05 0 [Warning] 'user' entry 'root@ab2be2af0e9b' ignored in --skip-name-resolve mode.
2020-02-21 11:55:05 0 [Warning] 'user' entry '@ab2be2af0e9b' ignored in --skip-name-resolve mode.
2020-02-21 11:55:05 0 [Warning] 'proxies_priv' entry '@% root@ab2be2af0e9b' ignored in --skip-name-resolve mode.
2020-02-21 11:55:05 0 [Note] InnoDB: Buffer pool(s) load completed at 200221 11:55:05
2020-02-21 11:55:06 0 [Note] Reading of all Master_info entries succeeded
2020-02-21 11:55:06 0 [Note] Added new Master_info '' to hash table
2020-02-21 11:55:06 0 [Note] mysqld: ready for connections.
Version: '10.4.12-MariaDB-1:10.4.12+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
2020-02-21 11:55:06+00:00 [Note] [Entrypoint]: Temporary server started.

[thjendk]

I have fixed it by deploying the database on its own like this (from a clean install, remember to delete both the letsencrypt and the data folder):
docker-compose up -d db

When that is done, the package works, and can be deployed using the full docker-compose file again. I'm not sure what's causing it, but it might only be replicateable on a new system. I have been able to replicate it on Mac and two seperate linux VMs.

[toomastamm]

How long did you wait after using the first docker-compose -d and then trying to login? The app takes a few minutes to get ready.

[thjendk]

Like 15 minutes I think. The issue might have resolved itself if I had waited longer. Closing for now.

[jc21]

That's very strange. The NPM nodejs backend will check for db access every 15 seconds and it loops forever. Having the database container take up to 15 mins to be ready is way too long as well.

In my CI, it spins up a fresh stack every time and it has no problems spinning up a mariadb docker container within 1 minute.

[thjendk]

I agree it’s way too long. Based on this comment: #300 (comment) the mariaDb is ready, but is refusing connections: #300 (comment)

[Kinark]

I'm having the same issue here.
Checked the data/logs/error.log and this error gets repeated over and over again:
2020/03/09 07:05:51 [error] 222#222: *42 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"

[Kinark]

And the docker for nginx container throws the following error:
[3/9/2020] [7:28:44 AM] [Global ] › ✖ error connect EHOSTUNREACH 172.20.0.2:330

[jc21]

@Kinark your first comment relates to nginx processing upstream hosts, which is not the topic of this issue and is most likely a misconfigured host.

Your second comment is more applicable, but to be sure everything is ok, is the port in your config 330 or 3306 ?