Timeout: context deadline exceeded

[rrcabrera9625]

Im trying to supabase db pull --schema storage and Im getting the below error:

failed to connect to postgres: failed to connect to host=aws-0-us-east-1.pooler.supabase.com user=cli_login_postgres.xxxx database=xxxx: failed to receive message (timeout: context deadline exceeded)

Retried a few minutes ago and get:

failed to connect to postgres: failed to connect to host=aws-0-us-east-1.pooler.supabase.com user=cli_login_postgres.xxxx database=xxxx: failed SASL auth (invalid SCRAM server-final-message received from server)

Also with supabase link Im getting:

failed to connect to postgres: failed to connect to host=aws-0-us-east-1.pooler.supabase.com user=cli_login_postgres.xxxx database=xxxx: failed to receive message (timeout: context deadline exceeded)

What is happening here?

[ServeBeez]

https://supabase.com/dashboard/project/your-project id/database/settings (Go to your project > Database > Under configuration (Settings) > scroll down you'll see the banned ips > then unban

[skogler]

@ServeBeez Thanks a lot, this just saved us a lot of headaches, since supabase decided to ban our deployment github action :)

[drewbietron]

This keeps happening even after removing an IP from the ban list in settings. We have multiple build steps within GitHub actions that may pull the schema to create types. Our builds no longer work if multiple actions are executed. The first will re-add the IP to the ban list and all subsequent supabase link fail as the IP is now banned..

[samducker]

latest version of cli with --skip-pooler when linking worked for me.