Internal Error 500

Question

Internal Error 500

Closed this issue 4 months ago · 19 comments

DevGoran commented 4 months ago

The bug

After deploying AirTrail via Portainer, I recieve error 500 when opening the web interface

Operating System that is running AirTrail

Docker

AirTrail Version

latest

Your docker-compose.yml content

services:
  db:
    container_name: airtrail_db
    image: postgres:16-alpine
    restart: always
    env_file:
      - stack.env
    environment:
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_PASSWORD: ${DB_PASSWORD}
    volumes:
      - db_data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U ${DB_USERNAME} -d ${DB_DATABASE_NAME}"]
      interval: 5s
      timeout: 5s
      retries: 5
  airtrail:
    container_name: airtrail
    image: johly/airtrail:latest
    restart: always
    env_file:
      - stack.env
    ports:
      - 3000:3000
    depends_on:
      db:
        condition: service_healthy

volumes:
  db_data:

Your .env content

ORIGIN=http://hostIP:3000
DB_URL=postgres://airtrail:PASSWORD_HERE@db:5432/airtrail
DB_PASSWORD=PASSWORD_HERE
DB_DATABASE_NAME=airtrail
DB_USERNAME=airtrail

Reproduction steps

Deploy AirTrail
Open Web interface

Relevant log output

Listening on 0.0.0.0:3000
530 |         result = new this._Promise((resolve, reject) => {
531 |           query.callback = (err, res) => (err ? reject(err) : resolve(res))
532 |         }).catch((err) => {
533 |           // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
534 |           // application that created the query
535 |           Error.captureStackTrace(err)
                      ^
error: relation "app_config" does not exist
 code: "42P01"
      at /app/node_modules/pg/lib/client.js:535:17
      at processTicksAndRejections (native:1:1)
      at /app/node_modules/kysely/dist/esm/dialect/postgres/postgres-driver.js:104:21

Additional information

No response

Answer 1 · 2024-10-18T21:58:50.000Z

+1 same error

Answer 2 · 2024-10-19T07:40:43.000Z

This is a known error related to the arm64 build. I will be able to fix this within a day and publish a new release.
If this isn't running on arm, please include the first few lines of the docker container logs, as it looks like a migration error.

Answer 3 · 2024-10-19T07:55:04.000Z

airtrail_db  | 
airtrail_db  | PostgreSQL Database directory appears to contain a database; Skipping initialization
airtrail_db  | 
airtrail_db  | 2024-10-19 07:53:26.541 UTC [1] LOG:  starting PostgreSQL 16.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
airtrail_db  | 2024-10-19 07:53:26.541 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
airtrail_db  | 2024-10-19 07:53:26.541 UTC [1] LOG:  listening on IPv6 address "::", port 5432
airtrail_db  | 2024-10-19 07:53:26.547 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
airtrail_db  | 2024-10-19 07:53:26.551 UTC [28] LOG:  database system was interrupted; last known up at 2024-10-19 07:49:59 UTC
airtrail_db  | 2024-10-19 07:53:26.717 UTC [28] LOG:  database system was not properly shut down; automatic recovery in progress
airtrail_db  | 2024-10-19 07:53:26.719 UTC [28] LOG:  invalid record length at 0/1978C98: expected at least 24, got 0
airtrail_db  | 2024-10-19 07:53:26.719 UTC [28] LOG:  redo is not required
airtrail_db  | 2024-10-19 07:53:26.723 UTC [26] LOG:  checkpoint starting: end-of-recovery immediate wait
airtrail_db  | 2024-10-19 07:53:26.731 UTC [26] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.002 s, total=0.010 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB; lsn=0/1978C98, redo lsn=0/1978C98
airtrail_db  | 2024-10-19 07:53:26.735 UTC [1] LOG:  database system is ready to accept connections
airtrail     | Applying migrations...
airtrail     | Resolving dependencies
airtrail     | Resolved, downloaded and extracted [26]
airtrail     | Saved lockfile
airtrail     | Starting server...
airtrail     | Listening on 0.0.0.0:3000

and then the error

airtrail_db  | 2024-10-19 07:54:26.415 UTC [107] ERROR:  relation "app_config" does not exist at character 15
airtrail_db  | 2024-10-19 07:54:26.415 UTC [107] STATEMENT:  select * from "app_config" limit $1
airtrail     | 530 |         result = new this._Promise((resolve, reject) => {
airtrail     | 531 |           query.callback = (err, res) => (err ? reject(err) : resolve(res))
airtrail     | 532 |         }).catch((err) => {
airtrail     | 533 |           // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
airtrail     | 534 |           // application that created the query
airtrail     | 535 |           Error.captureStackTrace(err)
airtrail     |                       ^
airtrail     | error: relation "app_config" does not exist
airtrail     |  code: "42P01"
airtrail     | 
airtrail     |       at /app/node_modules/pg/lib/client.js:535:17
airtrail     |       at processTicksAndRejections (native:1:1)
airtrail     |       at /app/node_modules/kysely/dist/esm/dialect/postgres/postgres-driver.js:104:21
airtrail     |

Answer 4 · 2024-10-19T09:09:23.000Z

Same here. Not on ARM but on AMD via ProxMox LXC container. Brand new setup, not a migration.

Linux airtrail 6.8.12-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-2 (2024-09-05T10:03Z) x86_64 GNU/Linux

DB Log:

waiting for server to shut down...2024-10-19 09:05:38.354 UTC [40] LOG:  received fast shutdown request
.2024-10-19 09:05:38.358 UTC [40] LOG:  aborting any active transactions
2024-10-19 09:05:38.362 UTC [40] LOG:  background worker "logical replication launcher" (PID 46) exited with exit code 1
2024-10-19 09:05:38.362 UTC [41] LOG:  shutting down
2024-10-19 09:05:38.365 UTC [41] LOG:  checkpoint starting: shutdown immediate
2024-10-19 09:05:38.610 UTC [41] LOG:  checkpoint complete: wrote 924 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.018 s, sync=0.217 s, total=0.248 s; sync files=301, longest=0.007 s, average=0.001 s; distance=4267 kB, estimate=4267 kB; lsn=0/191AB68, redo lsn=0/191AB68
2024-10-19 09:05:38.617 UTC [40] LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

2024-10-19 09:05:38.679 UTC [1] LOG:  starting PostgreSQL 16.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
2024-10-19 09:05:38.679 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-10-19 09:05:38.679 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2024-10-19 09:05:38.687 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-10-19 09:05:38.696 UTC [56] LOG:  database system was shut down at 2024-10-19 09:05:38 UTC
2024-10-19 09:05:38.703 UTC [1] LOG:  database system is ready to accept connections
2024-10-19 09:06:05.421 UTC [95] ERROR:  relation "app_config" does not exist at character 15
2024-10-19 09:06:05.421 UTC [95] STATEMENT:  select * from "app_config" limit $1

Answer 5 · 2024-10-19T15:11:27.000Z

Same issue in proxmox lxc. app_config not setup correctly?

Answer 6 · 2024-10-19T18:33:51.000Z

This may very well be fixed by #76, which will be available in the next release. I'll let you know when it releases.

Answer 7 · 2024-10-19T20:04:27.000Z

v0.3.2 has just been released. Do let me know if this fixed the issue.

Answer 8 · 2024-10-19T20:17:38.000Z

Fixed here.

Answer 9 · 2024-10-19T20:20:57.000Z

Fixed for me. Thanks.

Answer 10 · 2024-10-19T20:34:11.000Z

Awesome, glad to hear it!

Answer 11 · 2024-11-01T21:59:15.000Z

Even though I'm running the latest version, the problem is still there for me.

airtrail_db  | 2024-11-01 21:52:46.666 UTC [71] FATAL:  password authentication failed for user "airtrail"
airtrail_db  | 2024-11-01 21:52:46.666 UTC [71] DETAIL:  Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
airtrail     |       at /app/node_modules/pg-pool/index.js:45:11
airtrail     |
airtrail     | 40 |     res = resolve
airtrail     | 41 |     rej = reject
airtrail     | 42 |   }).catch((err) => {
airtrail     | 43 |     // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
airtrail     | 44 |     // application that created the query
airtrail     | 45 |     Error.captureStackTrace(err)
airtrail     |                ^
airtrail     | error: password authentication failed for user "airtrail"
airtrail     |  code: "28P01"
airtrail     |
airtrail     |       at /app/node_modules/pg-pool/index.js:45:11
```

Answer 12 · 2024-11-01T22:04:01.000Z

@lukasitaly that looks like your db credentials are mismatched. If you use the default docker-compose config, these two values need to be the same

Answer 13 · 2024-11-01T22:07:54.000Z

# The database URL used by the application.
# If you are using the provided docker-compose file, you should only change the GJAVCXMWshKCnxzy
# If you are using your own database, you should change this to the correct URL
DB_URL=postgres://airtrail:GJAVCXMWshKCnxzy@db:5432/airtrail

# Values below this line are only for the default provided postgres database
###################################################################################
# Connection secret for postgres. You should change it to a random password
# Please use only the characters `A-Za-z0-9`, without special characters or spaces
# When you change the DB_PASSWORD, you should also update the DB_URL accordingly
DB_PASSWORD=GJAVCXMWshKCnxzy

I used the bash script to install AirTrail, and it seems like it was executed correctly, the credentials don't mismatch

EDIT: Don't worry I'll change the credentials once the problem is solved ;)

Answer 14 · 2024-11-01T22:13:47.000Z

That is pretty weird. Can you show me your docker compose file and the first few lines of logs when starting docker compose? Including the database container starting.

(P.S. technically the password is just a formality in this case, as only other containers in the same compose file (or docker network) have access to the database as it isn't exposed)

Answer 15 · 2024-11-01T22:28:27.000Z

Compose:

services:
  db:
    container_name: airtrail_db
    image: postgres:16-alpine
    restart: always
    env_file:
      - .env
    environment:
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_PASSWORD: ${DB_PASSWORD}
    volumes:
      - db_data:/var/lib/postgresql/data
    healthcheck:
      test:
        - CMD-SHELL
        - pg_isready -U ${DB_USERNAME} -d ${DB_DATABASE_NAME}
      interval: 5s
      timeout: 5s
      retries: 5
  airtrail:
    container_name: airtrail
    image: johly/airtrail:latest
    restart: always
    env_file:
      - .env
    ports:
      - 3000:3000
    depends_on:
      db:
        condition: service_healthy
volumes:
  db_data: null
networks: {}

Env:

# Your domain, e.g https://example.com
# You might have to add :443 if you are using https through a reverse proxy
ORIGIN=http://192.168.1.66:3000

# The database URL used by the application.
# If you are using the provided docker-compose file, you should only change the GJAVCXMWshKCnxzy
# If you are using your own database, you should change this to the correct URL
DB_URL=postgres://airtrail:GJAVCXMWshKCnxzy@db:5432/airtrail

# Values below this line are only for the default provided postgres database
###################################################################################
# Connection secret for postgres. You should change it to a random password
# Please use only the characters `A-Za-z0-9`, without special characters or spaces
# When you change the DB_PASSWORD, you should also update the DB_URL accordingly
DB_PASSWORD=GJAVCXMWshKCnxzy

# The values below this line do not need to be changed
###################################################################################
DB_DATABASE_NAME=airtrail
DB_USERNAME=airtrail

Logs:

airtrail     | Applying migrations...
airtrail     | Resolving dependencies
airtrail     | Resolved, downloaded and extracted [26]
airtrail     | Saved lockfile
airtrail     | Prisma schema loaded from prisma/schema.prisma
airtrail     | Datasource "db": PostgreSQL database "airtrail", schema "public" at "db:5432"
airtrail     | 
airtrail     | Error: P1000: Authentication failed against database server at `db`, the provided database credentials for `airtrail` are not valid.
airtrail     | 
airtrail     | Please make sure to provide valid database credentials for the database server at `db`.
airtrail     | Starting server...
airtrail     | Listening on 0.0.0.0:3000
airtrail     | 40 |     res = resolve
airtrail     | 41 |     rej = reject
airtrail     | 42 |   }).catch((err) => {
airtrail     | 43 |     // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
airtrail     | 44 |     // application that created the query
airtrail     | 45 |     Error.captureStackTrace(err)
airtrail     |                ^
airtrail     | error: password authentication failed for user "airtrail"
airtrail     |  code: "28P01"
airtrail     | 
airtrail     |       at /app/node_modules/pg-pool/index.js:45:11
airtrail     | 
airtrail     | 40 |     res = resolve
airtrail     | 41 |     rej = reject
airtrail     | 42 |   }).catch((err) => {
airtrail     | 43 |     // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
airtrail     | 44 |     // application that created the query
airtrail     | 45 |     Error.captureStackTrace(err)
airtrail     |                ^
airtrail     | error: password authentication failed for user "airtrail"
airtrail     |  code: "28P01"
airtrail     | 
airtrail     |       at /app/node_modules/pg-pool/index.js:45:11
airtrail     | 
airtrail     | 40 |     res = resolve
airtrail     | 41 |     rej = reject
airtrail     | 42 |   }).catch((err) => {
airtrail     | 43 |     // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
airtrail     | 44 |     // application that created the query
airtrail     | 45 |     Error.captureStackTrace(err)
airtrail     |                ^
airtrail     | error: password authentication failed for user "airtrail"
airtrail     |  code: "28P01"
airtrail     | 
airtrail     |       at /app/node_modules/pg-pool/index.js:45:11
airtrail     | 
airtrail     | 40 |     res = resolve
airtrail     | 41 |     rej = reject
airtrail     | 42 |   }).catch((err) => {
airtrail     | 43 |     // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
airtrail     | 44 |     // application that created the query
airtrail     | 45 |     Error.captureStackTrace(err)
airtrail     |                ^
airtrail     | error: password authentication failed for user "airtrail"
airtrail     |  code: "28P01"
airtrail     | 
airtrail     |       at /app/node_modules/pg-pool/index.js:45:11
airtrail     | 
airtrail_db  | 
airtrail_db  | PostgreSQL Database directory appears to contain a database; Skipping initialization
airtrail_db  | 
airtrail_db  | 2024-11-01 21:52:20.229 UTC [1] LOG:  starting PostgreSQL 16.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
airtrail_db  | 2024-11-01 21:52:20.229 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
airtrail_db  | 2024-11-01 21:52:20.229 UTC [1] LOG:  listening on IPv6 address "::", port 5432
airtrail_db  | 2024-11-01 21:52:20.237 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
airtrail_db  | 2024-11-01 21:52:20.248 UTC [28] LOG:  database system was shut down at 2024-11-01 21:52:09 UTC
airtrail_db  | 2024-11-01 21:52:20.258 UTC [1] LOG:  database system is ready to accept connections
airtrail_db  | 2024-11-01 21:52:32.206 UTC [46] FATAL:  password authentication failed for user "airtrail"
airtrail_db  | 2024-11-01 21:52:32.206 UTC [46] DETAIL:  Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
airtrail_db  | 2024-11-01 21:52:40.011 UTC [54] FATAL:  password authentication failed for user "airtrail"
airtrail_db  | 2024-11-01 21:52:40.011 UTC [54] DETAIL:  Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
airtrail_db  | 2024-11-01 21:52:42.278 UTC [63] FATAL:  password authentication failed for user "airtrail"
airtrail_db  | 2024-11-01 21:52:42.278 UTC [63] DETAIL:  Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
airtrail_db  | 2024-11-01 21:52:46.666 UTC [71] FATAL:  password authentication failed for user "airtrail"
airtrail_db  | 2024-11-01 21:52:46.666 UTC [71] DETAIL:  Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
airtrail_db  | 2024-11-01 21:54:55.582 UTC [252] FATAL:  password authentication failed for user "airtrail"
airtrail_db  | 2024-11-01 21:54:55.582 UTC [252] DETAIL:  Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
airtrail_db  | 2024-11-01 21:57:20.346 UTC [26] LOG:  checkpoint starting: time
airtrail_db  | 2024-11-01 21:57:20.374 UTC [26] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.008 s, sync=0.003 s, total=0.028 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=0 kB; lsn=0/195C2C8, redo lsn=0/195C290

Once I try to access the service via 192.168.1.66:3000:

airtrail_db  | 2024-11-01 22:27:22.655 UTC [3013] FATAL:  password authentication failed for user "airtrail"
airtrail_db  | 2024-11-01 22:27:22.655 UTC [3013] DETAIL:  Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
airtrail     | 40 |     res = resolve
airtrail     | 41 |     rej = reject
airtrail     | 42 |   }).catch((err) => {
airtrail     | 43 |     // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
airtrail     | 44 |     // application that created the query
airtrail     | 45 |     Error.captureStackTrace(err)
airtrail     |                ^
airtrail     | error: password authentication failed for user "airtrail"
airtrail     |  code: "28P01"
airtrail     | 
airtrail     |       at /app/node_modules/pg-pool/index.js:45:11
airtrail     | 
airtrail_db  | 2024-11-01 22:27:23.061 UTC [3014] FATAL:  password authentication failed for user "airtrail"
airtrail_db  | 2024-11-01 22:27:23.061 UTC [3014] DETAIL:  Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
airtrail     | 40 |     res = resolve
airtrail     | 41 |     rej = reject
airtrail     | 42 |   }).catch((err) => {
airtrail     | 43 |     // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
airtrail     | 44 |     // application that created the query
airtrail     | 45 |     Error.captureStackTrace(err)
airtrail     |                ^
airtrail     | error: password authentication failed for user "airtrail"
airtrail     |  code: "28P01"
airtrail     | 
airtrail     |       at /app/node_modules/pg-pool/index.js:45:11
airtrail     |

Answer 16 · 2024-11-01T22:40:17.000Z

Using your exact configuration works on my machine. Can you send the beginning of the logs as well? They should contain the database startup logs which look something like this

airtrail_db  | 
airtrail_db  | PostgreSQL Database directory appears to contain a database; Skipping initialization
airtrail_db  | 
airtrail_db  | 2024-11-01 22:36:21.438 UTC [1] LOG:  starting PostgreSQL 16.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
airtrail_db  | 2024-11-01 22:36:21.438 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
airtrail_db  | 2024-11-01 22:36:21.438 UTC [1] LOG:  listening on IPv6 address "::", port 5432
airtrail_db  | 2024-11-01 22:36:21.448 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
airtrail_db  | 2024-11-01 22:36:21.460 UTC [29] LOG:  database system was shut down at 2024-11-01 22:35:59 UTC
airtrail_db  | 2024-11-01 22:36:21.468 UTC [1] LOG:  database system is ready to accept connections
airtrail     | Applying migrations...

Answer 17 · 2024-11-02T09:20:59.000Z

Sure! Here you go:

airtrail  | Applying migrations...
airtrail  | Resolving dependencies
airtrail  | Resolved, downloaded and extracted [26]
airtrail  | Saved lockfile
airtrail_db  |
airtrail_db  | PostgreSQL Database directory appears to contain a database; Skipping initialization
airtrail_db  |
airtrail_db  | 2024-11-02 09:20:03.159 UTC [1] LOG:  starting PostgreSQL 16.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
airtrail_db  | 2024-11-02 09:20:03.159 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
airtrail_db  | 2024-11-02 09:20:03.159 UTC [1] LOG:  listening on IPv6 address "::", port 5432
airtrail_db  | 2024-11-02 09:20:03.166 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
airtrail_db  | 2024-11-02 09:20:03.176 UTC [29] LOG:  database system was shut down at 2024-11-01 23:01:43 UTC
airtrail_db  | 2024-11-02 09:20:03.186 UTC [1] LOG:  database system is ready to accept connections
lukas@lukas:/mnt/nasdrive/Server/airtrail$ docker compose logs
airtrail_db  |
airtrail_db  | PostgreSQL Database directory appears to contain a database; Skipping initialization
airtrail_db  |
airtrail_db  | 2024-11-02 09:20:03.159 UTC [1] LOG:  starting PostgreSQL 16.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
airtrail_db  | 2024-11-02 09:20:03.159 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
airtrail_db  | 2024-11-02 09:20:03.159 UTC [1] LOG:  listening on IPv6 address "::", port 5432
airtrail     | Applying migrations...
airtrail_db  | 2024-11-02 09:20:03.166 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
airtrail     | Resolving dependencies
airtrail     | Resolved, downloaded and extracted [26]
airtrail     | Saved lockfile
airtrail     | Prisma schema loaded from prisma/schema.prisma
airtrail     | Datasource "db": PostgreSQL database "airtrail", schema "public" at "db:5432"
airtrail     |
airtrail     | Error: P1000: Authentication failed against database server at `db`, the provided database credentials for `airtrail` are not valid.
airtrail     |
airtrail     | Please make sure to provide valid database credentials for the database server at `db`.
airtrail     | Starting server...
airtrail     | Listening on 0.0.0.0:3000
airtrail_db  | 2024-11-02 09:20:03.176 UTC [29] LOG:  database system was shut down at 2024-11-01 23:01:43 UTC
airtrail_db  | 2024-11-02 09:20:03.186 UTC [1] LOG:  database system is ready to accept connections
airtrail_db  | 2024-11-02 09:20:15.121 UTC [47] FATAL:  password authentication failed for user "airtrail"
airtrail_db  | 2024-11-02 09:20:15.121 UTC [47] DETAIL:  Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"

Answer 18 · 2024-11-02T12:57:44.000Z

error: password authentication failed for user "airtrail"
airtrail | code: "28P01"

Can you login to DB from cli directly?

Answer 19 · 2024-11-02T21:22:32.000Z

@mkaatman yes I was able to login to the DB from cli