URGENT: Site is down, errors say "permission issues" but I can't figure out why.
I also can't "supabase link" to my staging db to try and fix
2025/08/11 13:11:37 PG Recv: {"Type":"ErrorResponse","Severity":"FATAL","SeverityUnlocalized":"FATAL","Code":"XX000","Message":"Authentication error, reason: "Authentication query failed: %DBConnection.ConnectionError{message: \"connection not available and request was dropped from queue after 10000ms. 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}"","Detail":"","Hint":"","Position":0,"InternalPosition":0,"InternalQuery":"","Where":"","SchemaName":"","TableName":"","ColumnName":"","DataTypeName":"","ConstraintName":"","File":"","Line":0,"Routine":"","UnknownFields":null}
panic: io: read/write on closed pipe
1 Reply
getting this weird cryptic error:
2025/08/11 13:27:18 PG Recv: {"Type":"ParameterStatus","Name":"server_version","Value":"15.8"}
panic: io: read/write on closed pipe
goroutine 148 [running]:
github.com/supabase/cli/internal/debug.(Proxy).DialFunc.func1()
github.com/supabase/cli/internal/debug/postgres.go:64 +0x338
created by github.com/supabase/cli/internal/debug.(Proxy).DialFunc in goroutine 1
github.com/supabase/cli/internal/debug/postgres.go:47 +0x13c
(base) vp@Victors-MacBook-Pro tmp-supabase-crixet %
this is JUST with db link to the staging db that should have NO traffic
raise exc_value.with_traceback(exc_tb)
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/pool/impl.py", line 167, in _do_get
return self._create_connection()
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/pool/base.py", line 393, in _create_connection
return _ConnectionRecord(self)
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/pool/base.py", line 678, in init
self.connect()
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/pool/base.py", line 903, in connect
pool.logger.debug("Error on connect(): %s", e)
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/langhelpers.py", line 146, in exit
raise exc_value.with_traceback(exc_tb)
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/pool/base.py", line 898, in connect
self.dbapi_connection = connection = pool._invoke_creator(self)
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/create.py", line 645, in connect
return dialect.connect(cargs, **cparams)
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 616, in connect
return self.loaded_dbapi.connect(cargs, **cparams)
File "/usr/local/lib/python3.9/site-packages/psycopg2/init__.py", line 122, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "aws-0-us-west-1.pooler.supabase.com" (52.8.172.168), port 5432 failed: error received from server in SCRAM exchange: Wrong password
(Background on this error at: https://sqlalche.me/e/20/e3q8)
It's resolved now. I manually setup a new migration that only copied over grants. idk how this happened but it was very disruptive
As best I can tell this was caused by some sort of rollout out of IPv6 and my router isn't configured for it