Supabase link fails to connect to postgres on latest (2.61.2)

[pkabra]

Describe the bug
Running supabase link using 2.61.2 (latest as of writing this issue) fails to connect to postgres with error:

Connecting to remote database...
failed to connect to postgres: failed to connect to `host=db.REDACTED.supabase.co user=cli_login_postgres database=postgres`: dial error (dial tcp [REDACTED_IPv6_ADDRESS]:5432: connect: no route to host)

To Reproduce
Steps to reproduce the behavior:

1. Run npx supabase@latest link
2. Select a project
3. Encounter connection error

Expected behavior
Supabase CLI should successfully link to the specified project.

System information
Rerun the failing command with --create-ticket flag.

• Ticket ID: 49599b7ca3494a39967aa11b736876f3
• Version of OS: macOS 15.6.1 (also failing on Github actions runner Ubuntu 24.04)
• Version of CLI: 2.61.2
• Version of Docker: v28.4.0

Additional context

This also occurs from Github Actions error. The same error occurs.

[sweatybridge]

Could you attach the debug logs?

supabase link --debug

[engPabloMartinez]

same here... here it goes

supabase link --debug
open supabase/.temp/profile: no such file or directory
Supabase CLI 2.61.2
Using profile: supabase (supabase.co)
Loading project ref from file: supabase/.temp/project-ref
Using access token from credentials store...
2025/11/25 16:05:23 HTTP GET: https://api.supabase.com/v1/projects
Selected project: NAME
2025/11/25 16:05:25 HTTP GET: https://api.supabase.com/v1/projects/NAME
2025/11/25 16:05:25 HTTP GET: https://api.supabase.com/v1/projects/NAME/api-keys?reveal=true
2025/11/25 16:05:25 HTTP GET: https://api.supabase.com/v1/projects/NAME/config/auth
2025/11/25 16:05:25 HTTP GET: https://api.supabase.com/v1/projects/NAME/config/storage
2025/11/25 16:05:25 HTTP GET: https://api.supabase.com/v1/projects/NAME/postgrest
2025/11/25 16:05:25 HTTP GET: https://api.supabase.com/v1/projects/NAME/network-restrictions
2025/11/25 16:05:25 HTTP GET: https://api.supabase.com/v1/projects/NAME/config/database/postgres
2025/11/25 16:05:26 HTTP GET: https://api.NAME.com/v1/projects/NAME/config/database/pooler
2025/11/25 16:05:26 HTTP GET: https://NAME.supabase.co/rest/v1/
2025/11/25 16:05:26 HTTP GET: https://NAME.supabase.co/auth/v1/health
2025/11/25 16:05:26 HTTP GET: https://NAME.supabase.co/storage/v1/version
Initialising login role...
2025/11/25 16:05:28 HTTP POST: https://api.supabase.com/v1/projects/NAME/cli/login-role
Connecting to remote database...
failed to connect to postgres: failed to connect to host=db.NAME.supabase.co user=cli_login_postgres database=postgres: dial error (dial tcp [ADDRESS]:5432: connect: no route to host)

[MicyToy]

v2.56.1 is ok.
Rolling back to v2.56.1 can resolve this issue temporarily.

[sweatybridge]

For those on macOS, could you also share the nslookup result for your project?

nslookup db.<ref>.supabase.co

[engPabloMartinez]

nslookup db.REF.supabase.co
Server: Local_ip
Address: Local_ip#53

Non-authoritative answer:
*** Can't find db.REF.supabase.co: No answer

But it is also happening in Github Actions as mentioned before

[pkabra]

Thanks for the quick turnaround on this @sweatybridge! Sorry didn't get the logs to you but looks like @engPabloMartinez was able to help out.

[engPabloMartinez]

any idea when we expect this to be released?

[sweatybridge]

We've just released a fix for this in v2.62.5. Let me know if it works for you.

[engPabloMartinez]

sweet... thanks... that worked locally and in the github actions too...