fivetran connector setup test failed

TL;DR

The setup test exercises the exact credentials and network path the sync will use, so a failure names a setup problem: wrong credentials, the source unreachable from Fivetran's servers, or permissions too narrow. Read the test's error detail, fix that layer, and re-run the test. A connector that cannot pass setup will never sync.

fivetran connector setup test failed

Use this when

• A new connector fails its setup test.
• It worked in a trial but fails in the real account.
• Credentials or source access changed since setup.

Not for this skill when

• Setup passed but syncs fail. That is a sync problem, not setup.
• You need to change an existing connector's config. Edit and re-test.

Steps

1. Read the setup test's detailed error: auth, network, or permission. Note the failing layer. Verify: the failure is categorized
2. Verify the credentials directly with the source's own client or docs. Note they work outside Fivetran. Verify: credentials are validated independently
3. Check network access: allowlist Fivetran's IPs if the source restricts by IP, and confirm no firewall blocks them. Note the path is open. Verify: the network path is confirmed
4. Confirm the source user has the permissions the connector needs: read on the tables, access to system views. Note the grants. Verify: permissions are sufficient
5. Fix the layer and re-run the setup test until it passes. Note the green test. Verify: setup is verified

Variant phrasings

fivetran setup test connection failed

The paraphrase.

fivetran connector cannot connect source

The symptom phrasing.

Compatibility: All Fivetran connectors. Setup test coverage varies by connector but always exercises auth and basic reads.

Why it happens

The setup test is a rehearsal: it connects, authenticates, and reads a sample using the production path. Failing fast here is the design; a connector that limped into production with bad credentials would fail every sync instead. Most failures are unglamorous: a pasted credential with a trailing space, an IP allowlist nobody updated, a read-only user missing one grant. The test output usually names the layer, which makes this a read-carefully problem rather than a deep one.

Edge cases / pitfalls

• Credentials with special characters can break in some setup forms. If auth fails mysteriously, try a credential without special characters to isolate.
• Some sources need a separate allowlist for Fivetran's EU versus US servers. Check which region your account uses.
• Setup tests that pass once can fail later when credentials rotate. Re-test after every rotation.
• Trial versus paid accounts sometimes have different source API access. A trial success does not guarantee production access.

Provenance

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

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

Thread query: fivetran connector setup test failed

TL;DR: The setup test exercises the exact credentials and network path the sync will use, so a failure names a setup problem: wrong credentials, the source unreachable from Fivetran's servers, or permissions too narrow. Read the test's error detail, fix that layer, and re-run the test. A connector that cannot pass setup will never sync.