Cannot connect to database using supervisor port (5432) after change password

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:19 PM

I'm getting

psql: error: connection to server at "<ip>", port 5432 failed: FATAL:  Authentication error, reason: "Authentication query failed: %DBConnection.ConnectionError{message: \"connection not available and request was dropped from queue after 14999ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\\n\\n  1. Ensuring your database is available and that you can connect to it\\n  2. Tracking down slow queries and making sure they are running fast enough\\n  3. Increasing the pool_size (although this increases resource consumption)\\n  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval\\n\\nSee DBConnection.start_link/2 for more information\\n\", severity: :error, reason: :queue_timeout}"

psql: error: connection to server at "<ip>", port 5432 failed: FATAL:  Authentication error, reason: "Authentication query failed: %DBConnection.ConnectionError{message: \"connection not available and request was dropped from queue after 14999ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\\n\\n  1. Ensuring your database is available and that you can connect to it\\n  2. Tracking down slow queries and making sure they are running fast enough\\n  3. Increasing the pool_size (although this increases resource consumption)\\n  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval\\n\\nSee DBConnection.start_link/2 for more information\\n\", severity: :error, reason: :queue_timeout}"

psql: error: connection to server at "<ip>", port 5432 failed: FATAL:  Authentication error, reason: "Authentication query failed: %DBConnection.ConnectionError{message: \"connection not available and request was dropped from queue after 14999ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\\n\\n  1. Ensuring your database is available and that you can connect to it\\n  2. Tracking down slow queries and making sure they are running fast enough\\n  3. Increasing the pool_size (although this increases resource consumption)\\n  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval\\n\\nSee DBConnection.start_link/2 for more information\\n\", severity: :error, reason: :queue_timeout}"

psql: error: connection to server at "<ip>", port 5432 failed: FATAL:  Authentication error, reason: "Authentication query failed: %DBConnection.ConnectionError{message: \"connection not available and request was dropped from queue after 14999ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\\n\\n  1. Ensuring your database is available and that you can connect to it\\n  2. Tracking down slow queries and making sure they are running fast enough\\n  3. Increasing the pool_size (although this increases resource consumption)\\n  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval\\n\\nSee DBConnection.start_link/2 for more information\\n\", severity: :error, reason: :queue_timeout}"

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:29 PM

inside supervisor container I get

16:28:24.126 region=local [error] Postgrex.Protocol (#PID<0.3621.0>) failed to connect: ** (Postgrex.Error) FATAL 28P01 (invalid_password) password authentication failed for user "pgbouncer"

16:28:24.126 region=local [error] Postgrex.Protocol (#PID<0.3621.0>) failed to connect: ** (Postgrex.Error) FATAL 28P01 (invalid_password) password authentication failed for user "pgbouncer"

16:28:24.126 region=local [error] Postgrex.Protocol (#PID<0.3621.0>) failed to connect: ** (Postgrex.Error) FATAL 28P01 (invalid_password) password authentication failed for user "pgbouncer"

16:28:24.126 region=local [error] Postgrex.Protocol (#PID<0.3621.0>) failed to connect: ** (Postgrex.Error) FATAL 28P01 (invalid_password) password authentication failed for user "pgbouncer"

but I already changed password for user pgbouncer

SSalem Yaslem سالم يسلم Hello, I built my own solution based on Supabase and it great success (~50 custo...

I

ibrahim•9/22/25, 4:32 PM

should the .env be where the password is stored for database connections?

I

ibrahim•9/22/25, 4:32 PM

what is the command you are runnning

Iibrahim should the .env be where the password is stored for database connections?

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:33 PM

yes, the variable

POSTGRES_PASSWORD

POSTGRES_PASSWORD

POSTGRES_PASSWORD

POSTGRES_PASSWORD is there

Iibrahim what is the command you are runnning

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:33 PM

you mean the command for password change?

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:34 PM

ALTER USER supabase_admin WITH PASSWORD '[REDACTED]';
ALTER USER postgres WITH PASSWORD '[REDACTED]';
ALTER USER authenticator WITH PASSWORD '[REDACTED]';
ALTER USER pgbouncer WITH PASSWORD '[REDACTED]';
ALTER USER supabase_auth_admin WITH PASSWORD '[REDACTED]';
ALTER USER supabase_functions_admin WITH PASSWORD '[REDACTED]';
ALTER USER supabase_storage_admin WITH PASSWORD '[REDACTED]';

ALTER USER supabase_admin WITH PASSWORD '[REDACTED]';
ALTER USER postgres WITH PASSWORD '[REDACTED]';
ALTER USER authenticator WITH PASSWORD '[REDACTED]';
ALTER USER pgbouncer WITH PASSWORD '[REDACTED]';
ALTER USER supabase_auth_admin WITH PASSWORD '[REDACTED]';
ALTER USER supabase_functions_admin WITH PASSWORD '[REDACTED]';
ALTER USER supabase_storage_admin WITH PASSWORD '[REDACTED]';

ALTER USER supabase_admin WITH PASSWORD '[REDACTED]';
ALTER USER postgres WITH PASSWORD '[REDACTED]';
ALTER USER authenticator WITH PASSWORD '[REDACTED]';
ALTER USER pgbouncer WITH PASSWORD '[REDACTED]';
ALTER USER supabase_auth_admin WITH PASSWORD '[REDACTED]';
ALTER USER supabase_functions_admin WITH PASSWORD '[REDACTED]';
ALTER USER supabase_storage_admin WITH PASSWORD '[REDACTED]';

ALTER USER supabase_admin WITH PASSWORD '[REDACTED]';
ALTER USER postgres WITH PASSWORD '[REDACTED]';
ALTER USER authenticator WITH PASSWORD '[REDACTED]';
ALTER USER pgbouncer WITH PASSWORD '[REDACTED]';
ALTER USER supabase_auth_admin WITH PASSWORD '[REDACTED]';
ALTER USER supabase_functions_admin WITH PASSWORD '[REDACTED]';
ALTER USER supabase_storage_admin WITH PASSWORD '[REDACTED]';

I

ibrahim•9/22/25, 4:35 PM

hmm i'm not sure altering the users like that is a good idea. What guide were you following?

I

ibrahim•9/22/25, 4:36 PM

are you trying to connect to local or remote database?

Iibrahim are you trying to connect to local or remote database?

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:37 PM

remote database self-hosted in vm

Iibrahim hmm i'm not sure altering the users like that is a good idea. What guide were yo...

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:37 PM

I didn't find any offical guide and just followed: https://github.com/supabase/supabase/issues/22605#issuecomment-2455781878

GitHub

Also Add Password Changing Guidelines · Issue #22605 · supabase/s...

Improve documentation Link https://supabase.com/docs/guides/self-hosting/docker Describe the problem When password is changed like for postgres in .env , It causes an error when started again docke...

SSalem Yaslem سالم يسلم I didn't find any offical guide and just followed: https://github.com/supabase/s...

I

ibrahim•9/22/25, 4:40 PM

i'm going to try and take a look at this and get back to you though i'm not too experienced with self hosting supabase

I

inder•9/22/25, 4:44 PM

Are the containers healthy after you made this change and recreated the instance

Iinder Are the containers healthy after you made this change and recreated the instance

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:48 PM

yes, they are healthy

[REDACTED]  supabase/supavisor:2.5.1  "/usr/bin/tini -s -g…"  43 hours ago  Up 20 minutes (healthy)  0.0.0.0:5432->5432/tcp, [::]:5432->5432/tcp, 0.0.0.0:6543->6543/tcp, [::]:6543->6543/tcp                                [REDACTED]-supabase-pooler

[REDACTED]  supabase/supavisor:2.5.1  "/usr/bin/tini -s -g…"  43 hours ago  Up 20 minutes (healthy)  0.0.0.0:5432->5432/tcp, [::]:5432->5432/tcp, 0.0.0.0:6543->6543/tcp, [::]:6543->6543/tcp                                [REDACTED]-supabase-pooler

[REDACTED]  supabase/supavisor:2.5.1  "/usr/bin/tini -s -g…"  43 hours ago  Up 20 minutes (healthy)  0.0.0.0:5432->5432/tcp, [::]:5432->5432/tcp, 0.0.0.0:6543->6543/tcp, [::]:6543->6543/tcp                                [REDACTED]-supabase-pooler

[REDACTED]  supabase/supavisor:2.5.1  "/usr/bin/tini -s -g…"  43 hours ago  Up 20 minutes (healthy)  0.0.0.0:5432->5432/tcp, [::]:5432->5432/tcp, 0.0.0.0:6543->6543/tcp, [::]:6543->6543/tcp                                [REDACTED]-supabase-pooler

`

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:48 PM

the error only happen for supervisor/pooler

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:48 PM

the application is up and working: https://suhol.ai

suhol.ai - سهول

حول أفكارك إلى مشاريع منظمة ومهام قابلة للتنفيذ مع أداة تحليل المشاريع المدعومة بالذكاء الاصطناعي. واجهة بسيطة وسهلة الاستخدام.

SSalem Yaslem سالم يسلم yes, they are healthy ``` [REDACTED] supabase/supavisor:2.5.1 "/usr/bin/tini -...

I

inder•9/22/25, 4:49 PM

Also the db?

Iinder Also the db?

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:49 PM

yes, it working and accept all requests

I

inder•9/22/25, 4:50 PM

And you recreated containers after updating password?

Iinder And you recreated containers after updating password?

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:51 PM

yes, all of container restarted

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:51 PM

I got only this error when try to connect to database with old/new password:

I

inder•9/22/25, 4:52 PM

I remember this guide working last time I had to update password. I'll test and get back to you.
Just to be sure you took down the containers using docker compose down and then ran

up

up

up

up again?

Iinder I remember this guide working last time I had to update password. I'll test and ...

S

Salem Yaslem سالم يسلمOP•9/22/25, 4:59 PM

it was just restart and I just tried down and up the container and still same issue

SSalem Yaslem سالم يسلم it was just restart and I just tried down and up the container and still same is...

I

inder•9/22/25, 6:58 PM

Ok I can reproduce the issue and I don't have a proper solution but a workaround. This seems to be an issue with supavisor.

If I revert back to old password, then I can login again. But as you have exposed the password, this won't be of any help to you
If I connect directly to db without supavisor in between then I can login to db

Iinder Ok I can reproduce the issue and I don't have a proper solution but a workaround...

S

Salem Yaslem سالم يسلمOP•9/22/25, 6:59 PM

I cannot use both workarounds because as you said first solution is to use already exposed password which is insecure

S

Salem Yaslem سالم يسلمOP•9/22/25, 6:59 PM

second solution will not work with supabase cli

I

inder•9/22/25, 6:59 PM

it will

I

inder•9/22/25, 7:00 PM