pg_dump: error
stefan@MacBookPro own-expo-supabase-starter % supabase migrations list
Initialising login role... Connecting to remote database...
Local | Remote | Time (UTC) -------|--------|------------ stefan@MacBookPro own-expo-supabase-starter % supabase db pull Initialising login role... Connecting to remote database... Dumping schema from remote database... pg_dump: error: connection to server at "aws-1-us-east-1.pooler.supabase.com" (18.213.155.45), port 5432 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? connection to server at "aws-1-us-east-1.pooler.supabase.com" (3.227.209.82), port 5432 failed: FATAL: {:shutdown, :db_termination} error running container: exit 1 Try rerunning the command with --debug to troubleshoot the error.
Initialising login role... Connecting to remote database...
Local | Remote | Time (UTC) -------|--------|------------ stefan@MacBookPro own-expo-supabase-starter % supabase db pull Initialising login role... Connecting to remote database... Dumping schema from remote database... pg_dump: error: connection to server at "aws-1-us-east-1.pooler.supabase.com" (18.213.155.45), port 5432 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? connection to server at "aws-1-us-east-1.pooler.supabase.com" (3.227.209.82), port 5432 failed: FATAL: {:shutdown, :db_termination} error running container: exit 1 Try rerunning the command with --debug to troubleshoot the error.
3 Replies
Hey! Those errors suggest a couple of possible issues. Can you try these steps:
1. If your project is paused (common on free tier after a week of inactivity), go to the dashboard and unpause it first - you won't be able to run any commands until you. If it's showing as active in the dashboard, try running a quick
SELECT 1; in the SQL Editor to ensure the database is responsive, then retry the CLI command.
2. If that still does not work, Run with the debug flag to see more details:
This can give us a bit more helpful information for debuggin purposes.
3. Check your project status in the dashboard:
- Make sure the database shows as "Active" (green indicator)
- Verify there are no paused/billing issues as well please.
Let me know what the debug output shows and if it still fails! We can explore these further and even jump on a call if necessary!What do you mean by wake up the db? the paused projects are not even allowed to run any sql queries. project is saved to disk and stopped from running. You have to unpause and only then you get access
Ah my bad, i mistyped it. let me correct it.