supabase
SUPABASE LINK HANGING IN INITIALISING LOGIN ROLE .........
I am working on Supabase free nano project for dev, it was working perfectly, but suddenly, when I tried to use the db push command or link project command in supabase CLI, it hangs on initialising login role
the debug in cli
aneesh@kb-srv-01:~/supabase$ supabase link --debug open supabase/.temp/profile: no such file or directory Using workdir /home/aneesh Supabase CLI 2.58.5 Using profile: supabase (supabase.co) Loading project ref from file: supabase/.temp/project-ref Using access token from file: /home/aneesh/.supabase/access-token 2025/12/01 06:34:15 HTTP GET: https://api.supabase.com/v1/projects Selected project: gnxiebfbhnachjnmgvwj 2025/12/01 06:34:18 HTTP GET: https://api.supabase.com/v1/projects/gnxiebfbhnachjnmgvwj 2025/12/01 06:34:18 HTTP GET: https://api.supabase.com/v1/projects/gnxiebfbhnachjnmgvwj/api-keys?reveal=true 2025/12/01 06:34:18 HTTP GET: https://api.supabase.com/v1/projects/gnxiebfbhnachjnmgvwj/config/storage 2025/12/01 06:34:18 HTTP GET: https://api.supabase.com/v1/projects/gnxiebfbhnachjnmgvwj/config/database/postgres 2025/12/01 06:34:18 HTTP GET: https://api.supabase.com/v1/projects/gnxiebfbhnachjnmgvwj/network-restrictions 2025/12/01 06:34:18 HTTP GET: https://api.supabase.com/v1/projects/gnxiebfbhnachjnmgvwj/postgrest 2025/12/01 06:34:18 HTTP GET: https://api.supabase.com/v1/projects/gnxiebfbhnachjnmgvwj/config/auth 2025/12/01 06:34:18 HTTP GET: https://api.supabase.com/v1/projects/gnxiebfbhnachjnmgvwj/config/database/pooler 2025/12/01 06:34:18 HTTP GET: https://gnxiebfbhnachjnmgvwj.supabase.co/rest/v1/ 2025/12/01 06:34:18 HTTP GET: https://gnxiebfbhnachjnmgvwj.supabase.co/auth/v1/health 2025/12/01 06:34:18 HTTP GET: https://gnxiebfbhnachjnmgvwj.supabase.co/storage/v1/version Using connection pooler: postgresql://postgres.gnxiebfbhnachjnmgvwj@aws-1-us-east-1.pooler.supabase.com:5432/postgres Initialising login role... 2025/12/01 06:34:19 HTTP POST: https://api.supabase.com/v1/projects/gnxiebfbhnachjnmgvwj/cli/login-role
Could you try setting the database password explicitly?
SUPABASE_DB_PASSWORD=<your-pass> supabase link
Could you try setting the database password explicitly?
SUPABASE_DB_PASSWORD=
supabase link
when I run it I saw multiple authentication okay message and its failed with the following error
2025/12/01 09:36:52 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} 2025/12/01 09:36:52 PG Recv: {"Type":"AuthenticationSASLFinal","Data":"v=THDCsDblDwbqgUFB4sEm1BdwkLlZjfELBx0PrByIjPQ="} 2025/12/01 09:36:52 PG Recv: {"Type":"AuthenticationOK"} failed to connect to postgres: failed to connect to host=aws-1-us-east-1.pooler.supabase.com user=postgres.gnxiebfbhnachjnmgvwj database=postgres: failed to receive message (timeout: context deadline exceeded)
