cli: failed to connect to postgres: failed to connect to `host=db.[id].supabase.co user=postgres database=postgres`: dial error (dial tcp [2406:da14:271:9903:c1bf:5f4c:ff8a:9e0c]:5432: connect: no route to host)
Describe the bug
I have been using Supabase Cli to push migration to remote db with zero issues, until all the sudden I was not able to do that. I can still link to different projects within the same account but now commands such as supabase db push --link supabase migrations list throw an error as seen in title.
Supabase CLI 2.19.7
Connecting to remote database...
2025/03/18 21:28:29 Connect Start: tcp [2406:da14:271:9903:c1bf:5f4c:ff8a:9e0c]:5432
2025/03/18 21:28:29 Connect Error: tcp [2406:da14:271:9903:c1bf:5f4c:ff8a:9e0c]:5432 dial tcp [2406:da14:271:9903:c1bf:5f4c:ff8a:9e0c]:5432: connect: no route to host
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 11
- Comments: 21 (2 by maintainers)
We have identified the problem and will be rolling out a fix soon. Thanks for reporting.
Was getting
connect: network is unreachable.Now I’m gettingAuthorization failed for the access token and project ref pair: {"message":"Cannot GET /***/***/***/***?reveal=false"}TCP connection seems to work now, but now I’m also getting an authorization error now :
Update: It seems to be working again. Thanks @sweatybridge !
Experienced same behavior in last 30 minutes (no prior issues on this flow)
Experiencing the same issue in my github actions workflow. Several retries resulted in the same outcome. The workflow ran for more than a year without any of these kind of issues.
Shortened log output:
Fixed for my case too! Thanks for the team resolving this.
Same issue. Wasn’t sure where to post the issue, but now I know! Thanks Supabase Staff!
Same issue with Github Actions and Supabase CLI 2.19.7 (installed using supabase/setup-cli@v1 with version: latest).
EDIT: Apparently Supabase team is already aware and looking into it https://github.com/orgs/supabase/discussions/17817#discussioncomment-12538898
Experiencing the same issue, tried to use different versions of the cli, the issue persists.