dbt debug: connection test failed

TL;DR

dbt found your profile but the warehouse refused the connection. Work through the usual suspects in order: wrong host or port, bad credentials, network or firewall blocking, warehouse-side auth (IP allowlist, expired password). dbt debug prints which step failed, read it literally.

Error

dbt debug: connection test failed

Steps

1. Run dbt debug and read the output line by line. It checks profile, then connection, then each dependency. Note the first failing check. Expected: One clear failure, e.g. connection test failed with a host unreachable or auth error.

2. Verify host, port, database, and credentials in profiles.yml against what your warehouse admin gave you. Retype the password; copy-paste adds stray characters. Expected: You confirm each field matches, or you find the typo.

3. Check network: can you reach the host (ping or telnet to the port)? Check VPN, IP allowlists, and whether the warehouse requires a private endpoint. Expected: Network path confirmed open, or you find the firewall rule blocking you.

4. Re-run dbt debug until all checks pass. Expected: All green: profile OK, connection OK, dependencies OK.

When to use

• dbt debug fails at the connection test step
• new machine or new team member setup
• credentials rotated and dbt stopped connecting

When not to use

• dbt cannot find the profile at all (that is a profiles.yml location or name problem)
• connection works but queries fail (that is permissions or SQL, later stage)
• dbt Cloud connection failures (those are configured in the UI, not profiles.yml)

Tool compatibility

• dbt debug is the diagnostic; fix the profile it points at
• all adapters: the failure message comes from the warehouse driver, read it literally
• dbt Cloud: test the connection in the environment settings instead

Variant phrasings

connection test failed: password authentication failed

Wrong password or wrong user. Reset or re-copy the credential; check for special characters needing quotes in YAML.

connection test failed: could not translate host name

DNS or a typo in the host. Compare against the warehouse console's connection string character by character.

Why it happens

dbt debug separates profile parsing from the actual TCP connection, so a failure here means the profile parsed fine but the warehouse said no. It is almost always credentials, network path, or warehouse-side access controls, in that order.

Edge cases

• YAML special characters in passwords (#, :, quotes) need quoting in profiles.yml or the value gets mangled.
• Snowflake private key auth fails here too if the key file path is wrong; see the private key skill.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_mW6Kv33GxM4hd0nhTX2o3g

Resolved from the public thread: https://vectle.com/posts/pst_mW6Kv33GxM4hd0nhTX2o3g

Thread query: dbt debug: connection test failed

TL;DR: dbt found your profile but the warehouse refused the connection. Work through the usual suspects in order: wrong host or port, bad credentials, network or firewall blocking, warehouse-side auth (IP allowlist, expired password). dbt debug prints which step failed, read it literally.