supabase start password authentication issues

[clayton-cc]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

supabase start is unable to start. FATAL 28P01 (invalid_password) password authentication failed for user "supabase_admin"

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Create a github action
2. Use supabase/setup-cli@v1, version: latest for supabase, ubuntu-latest for actions runner, actions/setup-node@v3 with node-version: 18
3. Run supabase start
4. See error

Expected behavior

Supabase starts and is able to be interacted with

Screenshots

System information

• OS: ubuntu latest github actions runner
• Browser (if applies): NA
• Version of supabase-js: latest
• Version of Node.js: 18

Additional context

We've tried clearing any caches on the github action which may be impacting. I saw an issue which seems to be similar here supabase/supabase#11957 The solution there was seemingly clearing docker volumes, etc which I don't think should be an issue on gh action but I'll see if there is any cruft that exists for some reason?

[clayton-cc]

Pinning the supabase/setup-cli@v1 to 1.115.5 seems to get around it. Going back to latest reintroduces the error. I'll do a bit more poking on versions, just selected a semi-recent one (since things were working on Friday) based on NPM releases. I see a few point updates to 1.123 today, but it doesn't look like I can see exactly which version is running in the gh action retroactively when using latest

[clayton-cc]

Some additional version testing:

Version	Starting
1.123.3	❌
1.123.0	❌
1.122.0	❌
1.121.1	❌
1.121.0	❌
1.120.0	❌
1.119.1	✅
1.119.0	✅
1.115.5	✅

[drraken]

Hello, I've encounter exact same thing and reverting back to 1.119.1 helped, thank you and I'm counting that this can be fixed in the future.

[lars-sorensen]

Pinning the supabase/setup-cli@v1 to 1.115.5 seems to get around it. Going back to latest reintroduces the error. I'll do a bit more poking on versions, just selected a semi-recent one (since things were working on Friday) based on NPM releases. I see a few point updates to 1.123 today, but it doesn't look like I can see exactly which version is running in the gh action retroactively when using latest

in which file(s) should that be changed?

[timzl]

I'm running through the Self-Hosting w/Docker instructions and hitting the same issue. After changing the the default POSTGRES_PASSWORD and attempting the solutions suggested in password authentication failed for user "supabase_auth_admin" - Docker Sefl Hosting #11957, the analytics and db containers fail to start with the following errors respectively:

17:10:03.190 [error] Postgrex.Protocol (#PID<0.4729.0>) failed to connect: ** (Postgrex.Error) FATAL 28P01 (invalid_password) password authentication failed for user "supabase_admin"

192.168.48.5 2024-02-08 17:31:32.953 UTC [118] supabase_admin@postgres FATAL:  password authentication failed for user "supabase_admin"

I can then run docker compose restart to get the some of the containers to start and the Supabase GUI to load in my browser, however several of the containers are in an unhealthy state and the logs show database connections errors.

CONTAINER ID   IMAGE                              COMMAND                   CREATED          STATUS                             PORTS                                                                                                      NAMES
d7680ea347e4   supabase/storage-api:v0.46.4       "docker-entrypoint.s…"    7 minutes ago    Restarting (1) 27 seconds ago                                                                                                                 supabase-storage
940ee1055630   supabase/edge-runtime:v1.33.5      "edge-runtime start …"    7 minutes ago    Up 5 minutes                                                                                                                                  supabase-edge-functions
146f42378a80   supabase/gotrue:v2.132.3           "auth"                    7 minutes ago    Restarting (1) 6 seconds ago                                                                                                                  supabase-auth
b0b5cd543ca7   supabase/postgres-meta:v0.75.0     "docker-entrypoint.s…"    7 minutes ago    Up 5 minutes (healthy)             8080/tcp                                                                                                   supabase-meta
568155ff7fe9   kong:2.8.1                         "bash -c 'eval \"echo…"   7 minutes ago    Up 5 minutes (healthy)             0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 8001/tcp, 0.0.0.0:8443->8443/tcp, :::8443->8443/tcp, 8444/tcp   supabase-kong
a11c661fd9a9   supabase/realtime:v2.25.50         "/usr/bin/tini -s -g…"    7 minutes ago    Up 10 seconds (health: starting)                                                                                                              realtime-dev.supabase-realtime
3391cbfbcb53   supabase/studio:20240101-8e4a094   "docker-entrypoint.s…"    7 minutes ago    Up 5 minutes (unhealthy)           3000/tcp                                                                                                   supabase-studio
a240a469f4d4   postgrest/postgrest:v12.0.1        "postgrest"               7 minutes ago    Restarting (1) 5 seconds ago                                                                                                                  supabase-rest
47d642cdf029   supabase/logflare:1.4.0            "sh run.sh"               7 minutes ago    Up 7 seconds (health: starting)    0.0.0.0:4000->4000/tcp, :::4000->4000/tcp                                                                  supabase-analytics
4c9e82a3c0f0   supabase/postgres:15.1.0.147       "docker-entrypoint.s…"    7 minutes ago    Up 5 minutes (healthy)             0.0.0.0:5432->5432/tcp, :::5432->5432/tcp                                                                  supabase-db
3489ef40782c   darthsim/imgproxy:v3.8.0           "imgproxy"                7 minutes ago    Up 5 minutes (healthy)             8080/tcp                                                                                                   supabase-imgproxy
36c351ef306c   timberio/vector:0.28.1-alpine      "/usr/local/bin/vect…"    30 minutes ago   Up 4 minutes (healthy)                                                                                                                        supabase-vector

$ docker logs 146f42378a80
[...]
{"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to `host=db user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2024-02-08T17:34:50Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2024-02-08T17:35:50Z"}
{"args":[0.064195059],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-02-08T17:35:50Z"}
{"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to `host=db user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2024-02-08T17:35:50Z"}

Docker version 25.0.2, build 29cf629
Debian GNU/Linux 12