The only error I get is this: using the official health check path, when it fails, it ends with this log. However, in the general console, it appears that Docker doesn't have permissions or access to the DB even when I configure the variables with Postgres variables. Env example:

ENABLE_ALPINE_PRIVATE_NETWORKING="true"

MB_DB_DBNAME="${{Postgres.PGDATABASE}}"

MB_DB_HOST="${{Postgres.PGHOST}}"

MB_DB_PASS="${{Postgres.PGPASSWORD}}"

MB_DB_PORT="${{Postgres.PGPORT}}"

MB_DB_TYPE="postgres"

MB_DB_USER="${{Postgres.PGUSER}}"

MB_PASSWORD_COMPLEXITY="strong"

MB_SITE_URL="https://${{RAILWAY_PUBLIC_DOMAIN}}"

PORT="3000"

Build Log:

i think the db is the root of the failed health checks. maybe try to connect to db manually using psql or gui based like DBeaver with the same credential. if you can connect to db manually, then the metabase-postgres connection might be the culprit.

try to set the environment variables using Railway’s Variables tab, not just Dockerfile or docker-compose.

something like this (direct values)

MB_DB_TYPE=postgres

MB_DB_DBNAME=mydb

MB_DB_PORT=5432

MB_DB_USER=postgres

MB_DB_PASS=supersecret

MB_DB_HOST=containers-us-west-xxx.railway.app

If you’re still stuck, feel free to paste the exact DB logs or deployment config (YAML/compose/envs), and I’ll help you further.