Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Local dev: Supabase start failing sasl authentication #3274

Open
2 tasks done
bhimeshchauhan opened this issue Mar 7, 2025 · 2 comments
Open
2 tasks done

Local dev: Supabase start failing sasl authentication #3274

bhimeshchauhan opened this issue Mar 7, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@bhimeshchauhan
Copy link

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

Running supabase start returns following error:

➜  scrubs git:(dev) supabase start
WARN: no SMS provider is enabled. Disabling phone login
15.1.1.41: Pulling from supabase/postgres
6aae4cfdd5a1: Pull complete
75b0a584ca74: Pull complete
fb49e9e3a887: Pull complete
d02bd79f1770: Pull complete
dfb3a927a9f5: Pull complete
1e6ff4b21b98: Pull complete
726a20438873: Pull complete
1dc9b99e4e68: Pull complete
2f4b7982f80f: Pull complete
2faab6d23dcf: Pull complete
81fdf712b3e1: Pull complete
cd0ae25548f1: Pull complete
5e6a41da81b1: Pull complete
736e2923e323: Pull complete
ad069659eb9c: Pull complete
facbd915e56a: Pull complete
a76966536613: Pull complete
d622fe6a715f: Pull complete
eea3e5638929: Pull complete
6a11ac25cd35: Pull complete
5f02ae5d1df9: Pull complete
b7db72fb312d: Pull complete
12e52d03a558: Pull complete
e4b773b01ca3: Pull complete
Digest: sha256:b954155da45d6ac4cde6c9b681e9b4867eedec4c7b6944aca99828d7d8add095
Status: Downloaded newer image for public.ecr.aws/supabase/postgres:15.1.1.41
2.8.1: Pulling from supabase/kong
9b18e9b68314: Pull complete
7fd91e922960: Pull complete
450997ae687c: Pull complete
d8380bfcbd9b: Pull complete
Digest: sha256:1b53405d8680a09d6f44494b7990bf7da2ea43f84a258c59717d4539abf09f6d
Status: Downloaded newer image for public.ecr.aws/supabase/kong:2.8.1
v2.168.0: Pulling from supabase/gotrue
cb8611c9fe51: Pull complete
efa94caa7799: Pull complete
92e94f0d53f0: Pull complete
deab6c84367d: Pull complete
d0a6ca4af46a: Pull complete
cb6d72129a62: Pull complete
Digest: sha256:9b98b1a89a40c76b50c09d60a0901f92b47acfcbe5654ff46e20cccdaf31b7c9
Status: Downloaded newer image for public.ecr.aws/supabase/gotrue:v2.168.0
3.0.3: Pulling from supabase/inbucket
f97344484467: Pull complete
c93cd632d565: Pull complete
7cadd1efbbe6: Pull complete
9853c0941218: Pull complete
b6f6817b1d4a: Pull complete
c5c956c4e9fc: Pull complete
59cbfb43403a: Pull complete
9c842edb6049: Pull complete
Digest: sha256:dc912ab76de647ca2a363fe285515e512e964cf699166773f3c2c73f5e7f71c0
Status: Downloaded newer image for public.ecr.aws/supabase/inbucket:3.0.3
v2.34.31: Pulling from supabase/realtime
failed to display json stream: toomanyrequests: Rate exceeded
Retrying after 4s: public.ecr.aws/supabase/realtime:v2.34.31
v2.34.31: Pulling from supabase/realtime
6d29a096dd42: Pull complete
bc38f88e152a: Pull complete
c106c8d9425a: Pull complete
2e1c626baf42: Pull complete
682f143a9682: Pull complete
07c59e22c884: Pull complete
bc91d6a0da55: Pull complete
ad30bdc414a0: Pull complete
Digest: sha256:1793b6c80d4768f7d6d59774db45355e1adffdd0c9586e90d23f999e1ac4286a
Status: Downloaded newer image for public.ecr.aws/supabase/realtime:v2.34.31
v12.0.2: Pulling from supabase/postgrest
d519a3a2a796: Pull complete
4e0059d9a247: Pull complete
1ed0fb2de4f4: Pull complete
Digest: sha256:79369c0cdf9d7112ed4e327bc1b80156be11575dd66fbda245077a2d13b803bc
Status: Downloaded newer image for public.ecr.aws/supabase/postgrest:v12.0.2
v1.17.1: Pulling from supabase/storage-api
0152682790bb: Pull complete
3080fd8461c2: Pull complete
f6abfa9fdc18: Pull complete
ea3a1da93fdb: Pull complete
211d9a3890e9: Pull complete
2a78033e6351: Pull complete
21d0e8f54bd5: Pull complete
94ea9fdf2516: Pull complete
bf02de7ad9d1: Pull complete
b56a3c80109e: Pull complete
Digest: sha256:587778b5fe332eabd3892c1db365c20ca9408270b25457fe661f47c8bc177167
Status: Downloaded newer image for public.ecr.aws/supabase/storage-api:v1.17.1
v3.8.0: Pulling from supabase/imgproxy
df8e44b0463f: Pull complete
b0f1dd53d7c3: Pull complete
ead8ac122bf1: Pull complete
4667765ff03a: Pull complete
744485a3a3a9: Pull complete
8650da0c91b5: Pull complete
Digest: sha256:0facd355d50f3be665ebe674486f2b2e9cdaebd3f74404acd9b7fece2f661435
Status: Downloaded newer image for public.ecr.aws/supabase/imgproxy:v3.8.0
v1.67.2: Pulling from supabase/edge-runtime
4d2547c08499: Pull complete
c4194328be1a: Pull complete
1b0a492f3d1f: Pull complete
1820033bfc3d: Pull complete
8c7ec07431d0: Pull complete
9713ccbefa48: Pull complete
Digest: sha256:1359500175db2a8eb3837e4582191689d9dca7b103470ac6febac0fae9c28e9d
Status: Downloaded newer image for public.ecr.aws/supabase/edge-runtime:v1.67.2
v0.86.0: Pulling from supabase/postgres-meta
failed to display json stream: Get "https://public.ecr.aws/v2/supabase/postgres-meta/manifests/sha256:96771f0cd5f721c52b0ea0581ffad8494d4eed094e868838e9667d7633c8ed97": proxyconnect tcp: dial tcp 192.168.65.1:3128: i/o timeout
Retrying after 4s: public.ecr.aws/supabase/postgres-meta:v0.86.0
v0.86.0: Pulling from supabase/postgres-meta
4d2547c08499: Already exists
2476b939e842: Pull complete
5abb1ac0e1b3: Pull complete
91082d37f79b: Pull complete
348849d14ed6: Pull complete
476853c83e2e: Pull complete
4f621b67c6cb: Pull complete
c5e51bcbe97f: Pull complete
608ffcbf4965: Pull complete
0223ca6619eb: Pull complete
Digest: sha256:8318284f9d3633245b33a716a93369bd0906180bb8894ed94f5d686d488926ff
Status: Downloaded newer image for public.ecr.aws/supabase/postgres-meta:v0.86.0
20250224-d10db0f: Pulling from supabase/studio
4d2547c08499: Already exists
2476b939e842: Already exists
5abb1ac0e1b3: Already exists
91082d37f79b: Already exists
348849d14ed6: Already exists
a48bd9f7cb9e: Pull complete
99082fbca284: Pull complete
c3797e477d0d: Pull complete
886173e58049: Pull complete
0cb31da90c47: Pull complete
2a4002e200ef: Pull complete
Digest: sha256:d13aae7c70a8361886bc6cc9060c874fbbee36363009ccd3964dac3824b77813
Status: Downloaded newer image for public.ecr.aws/supabase/studio:20250224-d10db0f
supabase_auth_scrubs container logs:
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:25:40Z"}
{"args":[0.006539292],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:25:40Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:25:40Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:25:40Z"}
{"args":[0.00526075],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:25:40Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:25:40Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:25:40Z"}
{"args":[0.006192542],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:25:40Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:25:40Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:25:41Z"}
{"args":[0.005533083],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:25:41Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:25:41Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:25:42Z"}
{"args":[0.007652959],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:25:42Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:25:42Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:25:43Z"}
{"args":[0.006529209],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:25:43Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:25:43Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:25:47Z"}
{"args":[0.006756],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:25:47Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:25:47Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:25:53Z"}
{"args":[0.008199875],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:25:53Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:25:53Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:26:06Z"}
{"args":[0.008943708],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:26:06Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:26:06Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:26:32Z"}
{"args":[0.007875958],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:26:32Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:26:32Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2025-03-07T05:27:24Z"}
{"args":[0.011407458],"component":"pop","level":"info","msg":"%.4f seconds","time":"2025-03-07T05:27:24Z"}
{"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=supabase_db_scrubs user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2025-03-07T05:27:24Z"}
supabase_realtime_scrubs container logs:
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
1048576
Running migrations
05:25:51.398 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
1048576
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
Running migrations
05:25:51.970 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
1048576
Running migrations
05:25:52.698 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
1048576
Running migrations
05:25:53.663 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
1048576
Running migrations
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
05:25:55.017 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
+ ulimit -n
1048576
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
Running migrations
05:25:57.158 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
1048576
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
Running migrations
05:26:00.924 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
+ ulimit -n
1048576
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
Running migrations
05:26:07.886 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
1048576
Running migrations
05:26:22.262 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
1048576
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
Running migrations
05:26:48.406 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
1048576
Running migrations
05:27:40.125 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
supabase_rest_scrubs container logs:
07/Mar/2025:05:25:55 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:25:55 +0000: Attempting to connect to the database...
07/Mar/2025:05:25:55 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:55 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:55 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
07/Mar/2025:05:25:55 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:25:55 +0000: Attempting to connect to the database...
07/Mar/2025:05:25:55 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:55 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:55 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
07/Mar/2025:05:25:56 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:25:56 +0000: Attempting to connect to the database...
07/Mar/2025:05:25:56 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:56 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:56 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
07/Mar/2025:05:25:56 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:25:56 +0000: Attempting to connect to the database...
07/Mar/2025:05:25:56 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:56 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:56 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
07/Mar/2025:05:25:57 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:25:57 +0000: Attempting to connect to the database...
07/Mar/2025:05:25:57 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:57 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:57 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
07/Mar/2025:05:25:59 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:25:59 +0000: Attempting to connect to the database...
07/Mar/2025:05:25:59 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:59 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:25:59 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
07/Mar/2025:05:26:02 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:26:02 +0000: Attempting to connect to the database...
07/Mar/2025:05:26:02 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:26:02 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:26:02 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
07/Mar/2025:05:26:09 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:26:09 +0000: Attempting to connect to the database...
07/Mar/2025:05:26:09 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:26:09 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:26:09 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
07/Mar/2025:05:26:22 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:26:22 +0000: Attempting to connect to the database...
07/Mar/2025:05:26:22 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:26:22 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:26:22 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
07/Mar/2025:05:26:47 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:26:47 +0000: Attempting to connect to the database...
07/Mar/2025:05:26:47 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:26:47 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:26:47 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
07/Mar/2025:05:27:39 +0000: Starting PostgREST 12.0.2 (a4e00ff)...
07/Mar/2025:05:27:39 +0000: Attempting to connect to the database...
07/Mar/2025:05:27:39 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:27:39 +0000: {"code":"PGRST000","details":"FATAL:  password authentication failed for user \"authenticator\"\n","hint":null,"message":"Database connection error. Retrying the connection."}
07/Mar/2025:05:27:39 +0000: FATAL:  password authentication failed for user "authenticator"

postgrest: thread killed
supabase_storage_scrubs container logs:
{"level":50,"time":"2025-03-07T05:26:09.412Z","pid":1,"hostname":"330a2a4deccd","region":"not-specified","type":"startupError","error":{"raw":"{\"length\":118,\"name\":\"error\",\"severity\":\"FATAL\",\"code\":\"28P01\",\"file\":\"auth.c\",\"line\":\"326\",\"routine\":\"auth_failed\"}","name":"error","message":"password authentication failed for user \"supabase_storage_admin\"","stack":"error: password authentication failed for user \"supabase_storage_admin\"\n    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)\n    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)\n    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)\n    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)"},"msg":"Server not started with error"}
{"level":50,"time":"2025-03-07T05:26:10.077Z","pid":1,"hostname":"330a2a4deccd","region":"not-specified","type":"startupError","error":{"raw":"{\"length\":118,\"name\":\"error\",\"severity\":\"FATAL\",\"code\":\"28P01\",\"file\":\"auth.c\",\"line\":\"326\",\"routine\":\"auth_failed\"}","name":"error","message":"password authentication failed for user \"supabase_storage_admin\"","stack":"error: password authentication failed for user \"supabase_storage_admin\"\n    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)\n    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)\n    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)\n    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)"},"msg":"Server not started with error"}
{"level":50,"time":"2025-03-07T05:26:10.854Z","pid":1,"hostname":"330a2a4deccd","region":"not-specified","type":"startupError","error":{"raw":"{\"length\":118,\"name\":\"error\",\"severity\":\"FATAL\",\"code\":\"28P01\",\"file\":\"auth.c\",\"line\":\"326\",\"routine\":\"auth_failed\"}","name":"error","message":"password authentication failed for user \"supabase_storage_admin\"","stack":"error: password authentication failed for user \"supabase_storage_admin\"\n    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)\n    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)\n    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)\n    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)"},"msg":"Server not started with error"}
{"level":50,"time":"2025-03-07T05:26:11.864Z","pid":1,"hostname":"330a2a4deccd","region":"not-specified","type":"startupError","error":{"raw":"{\"length\":118,\"name\":\"error\",\"severity\":\"FATAL\",\"code\":\"28P01\",\"file\":\"auth.c\",\"line\":\"326\",\"routine\":\"auth_failed\"}","name":"error","message":"password authentication failed for user \"supabase_storage_admin\"","stack":"error: password authentication failed for user \"supabase_storage_admin\"\n    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)\n    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)\n    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)\n    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)"},"msg":"Server not started with error"}
{"level":50,"time":"2025-03-07T05:26:13.220Z","pid":1,"hostname":"330a2a4deccd","region":"not-specified","type":"startupError","error":{"raw":"{\"length\":118,\"name\":\"error\",\"severity\":\"FATAL\",\"code\":\"28P01\",\"file\":\"auth.c\",\"line\":\"326\",\"routine\":\"auth_failed\"}","name":"error","message":"password authentication failed for user \"supabase_storage_admin\"","stack":"error: password authentication failed for user \"supabase_storage_admin\"\n    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)\n    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)\n    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)\n    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)"},"msg":"Server not started with error"}
{"level":50,"time":"2025-03-07T05:26:15.503Z","pid":1,"hostname":"330a2a4deccd","region":"not-specified","type":"startupError","error":{"raw":"{\"length\":118,\"name\":\"error\",\"severity\":\"FATAL\",\"code\":\"28P01\",\"file\":\"auth.c\",\"line\":\"326\",\"routine\":\"auth_failed\"}","name":"error","message":"password authentication failed for user \"supabase_storage_admin\"","stack":"error: password authentication failed for user \"supabase_storage_admin\"\n    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)\n    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)\n    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)\n    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)"},"msg":"Server not started with error"}
{"level":50,"time":"2025-03-07T05:26:20.122Z","pid":1,"hostname":"330a2a4deccd","region":"not-specified","type":"startupError","error":{"raw":"{\"length\":118,\"name\":\"error\",\"severity\":\"FATAL\",\"code\":\"28P01\",\"file\":\"auth.c\",\"line\":\"326\",\"routine\":\"auth_failed\"}","name":"error","message":"password authentication failed for user \"supabase_storage_admin\"","stack":"error: password authentication failed for user \"supabase_storage_admin\"\n    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)\n    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)\n    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)\n    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)"},"msg":"Server not started with error"}
{"level":50,"time":"2025-03-07T05:26:27.221Z","pid":1,"hostname":"330a2a4deccd","region":"not-specified","type":"startupError","error":{"raw":"{\"length\":118,\"name\":\"error\",\"severity\":\"FATAL\",\"code\":\"28P01\",\"file\":\"auth.c\",\"line\":\"326\",\"routine\":\"auth_failed\"}","name":"error","message":"password authentication failed for user \"supabase_storage_admin\"","stack":"error: password authentication failed for user \"supabase_storage_admin\"\n    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)\n    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)\n    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)\n    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)"},"msg":"Server not started with error"}
{"level":50,"time":"2025-03-07T05:26:40.635Z","pid":1,"hostname":"330a2a4deccd","region":"not-specified","type":"startupError","error":{"raw":"{\"length\":118,\"name\":\"error\",\"severity\":\"FATAL\",\"code\":\"28P01\",\"file\":\"auth.c\",\"line\":\"326\",\"routine\":\"auth_failed\"}","name":"error","message":"password authentication failed for user \"supabase_storage_admin\"","stack":"error: password authentication failed for user \"supabase_storage_admin\"\n    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)\n    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)\n    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)\n    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)"},"msg":"Server not started with error"}
{"level":50,"time":"2025-03-07T05:27:06.941Z","pid":1,"hostname":"330a2a4deccd","region":"not-specified","type":"startupError","error":{"raw":"{\"length\":118,\"name\":\"error\",\"severity\":\"FATAL\",\"code\":\"28P01\",\"file\":\"auth.c\",\"line\":\"326\",\"routine\":\"auth_failed\"}","name":"error","message":"password authentication failed for user \"supabase_storage_admin\"","stack":"error: password authentication failed for user \"supabase_storage_admin\"\n    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)\n    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)\n    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)\n    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)"},"msg":"Server not started with error"}
Stopping containers...
supabase_auth_scrubs container is not ready: unhealthy
supabase_realtime_scrubs container is not ready: unhealthy
Error status 503:
supabase_storage_scrubs container is not ready: unhealthy
Try rerunning the command with --debug to troubleshoot the error.

To Reproduce

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

  1. run supabase start

Expected behavior

Should start the containers in healthy state

Screenshots

If applicable, add screenshots to help explain your problem.

System information

  • OS: [macOS]
  • Version of supabase [2.15.8]
  • Version of supabase-js: [2.49.1]
  • Version of Node.js: [18.20.4]

Additional context

Add any other context about the problem here.
@bhimeshchauhan bhimeshchauhan added the bug Something isn't working label Mar 7, 2025
@w3b6x9 w3b6x9 transferred this issue from supabase/supabase Mar 9, 2025
@Hallidayo
Copy link

Hi, I've moved this issue over from the supabase repo as it looks like a cli issue.

@bhimeshchauhan
Copy link
Author

@Hallidayo thank you 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bhimeshchauhan @Hallidayo