Database Error 250001: Could not connect to Snowflake backend after 0 attempt(s).

Hi,

My dbt setup used to work perfectly, but suddenly I started to get this error after dbt debug. I uninstalled dbt several times, installed it in different venvs, change the profiles.yml file in several ways (although the one I’m attaching here is the supposedly correct format, and the one that was working for me and my team), looked up every similar issue in Google… I really have no clue how to fix it. Please help!

Error message (changing personal info):

(dbt-snowflake) name.surname@WX577G44TP dbt % dbt debug               
19:43:25  Running with dbt=1.3.2
dbt version: 1.3.2
python version: 3.9.16
python path: /Users/name.surname/.virtualenv/dbt-snowflake/bin/python
os info: macOS-13.0-arm64-arm-64bit
Using profiles.yml file at /Users/name.surname/.dbt/profiles.yml
Using dbt_project.yml file at /Users/name.surname/projects/saltdata-build-tool/dbt/dbt_project.yml

Configuration:
  profiles.yml file [OK found and valid]
  dbt_project.yml file [OK found and valid]

Required dependencies:
 - git [OK found]

Connection:
  account: rt11111.eu-west-1
  user: NAME.SURNAME@COMPANY.CO
  database: NAMES
  schema: MARTS
  warehouse: DATA_ANALYSTS
  role: NAMES
  client_session_keep_alive: False
  Connection test: [ERROR]

1 check failed:
dbt was unable to connect to the specified database.
The database returned the following error:

  >Database Error
  250001: Could not connect to Snowflake backend after 0 attempt(s).Aborting

profiles.yml file:

saltdata_sf:
  target: loc
  outputs:
    loc:
      type: snowflake
      threads: 4
      account: rt11111.eu-west-1
      authenticator: 'externalbrowser'
      user: NAME.SURNAME@COMPANY.CO
      role: NAMES
      database: NAMES
      schema: MARTS
      warehouse: DATA_ANALYSTS
      query_tag: dbt

@carrerapcl you happen to find a solution for this? I’m experiencing the same issue but on wondows

Hello, did you manage to find a solution? I am currently having the same issue

Same here. i’m having the same issue.