Stitch Documentation
has moved!

Please update your bookmarks to https://www.stitchdata.com/docs

If you're not automatically redirected after 5 seconds, click here.

Troubleshooting Data Warehouse Connection Errors

Receiving errors from an unsuccessful connection check to your destination? In this article, we'll help you troubleshoot some of the most common errors when a connection error surfaces.

Common Error Messages

Part of the message Stitch that displays when there’s a connection error includes the raw response Stitch receives from the destination. When troubleshooting a connection error, this message (which is highlighted in the image to the right) is where you should start.

Keep in mind that Stitch simply displays the response the database sends. This means that, unfortunately, Stitch can only the level of detail that’s in the response.

In the section below, you'll find:

  • The raw response from the destination,
  • What it means, and
  • How to fix it

If the troubleshooting steps in this article don't resolve the issue or you don't see the error you received here, please contact support.

Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
This means: Fix it by:
Stitch encountered an error when attempting to “talk” to your destination.
  • Verify that Stitch’s IP addresses are whitelisted.

    If you’re a Redshiftor Postgres-RDS user: You need to check that both the Security Group AND VPC  Subnet allow access from Stitch’s IP addresses.
    • 54.88.76.97/32
    • 52.23.137.21/32
    • 52.204.223.208/32
    • 52.204.228.32/32
    • 52.204.230.227/32
  • Verify that the port setting you entered in Stitch’s Destination Settings page is correct.
  • Verify that the hostname entered in the Destination Settings page is correct.

    If you’re a Redshift or Postgres-RDS user: check that the port has been removed from the end of the hostname string, as outlined here.

 

An I/O error occured while sending to the backend.
This means: Fix it by:
Something went wrong during the communication with the destination. This is a transient error, and should clear itself during the next re-sync.

 

FATAL: Password authentication failed for user [user_name]
This means: Fix it by:
The credentials that Stitch has for your destination are incorrect. Verify that the correct password for the user Stitch is using to connect to the destination is entered in the Destination Settings page of Stitch.

 

Connection timed out
This means: Fix it by:
The connection timed out before Stitch could successfully establish a connection. This error may be transient and resolve on its own, but if it persists, try the following before contacting support:
  • Verify that Stitch’s IP addresses are whitelisted.

    If you’re a Redshiftor Postgres-RDS user: You need to check that both the Security Group AND VPC  Subnet allow access from Stitch’s IP addresses.
    • 54.88.76.97/32
    • 52.23.137.21/32
    • 52.204.223.208/32
    • 52.204.228.32/32
    • 52.204.230.227/32
  • Verify that the port setting you entered in Stitch’s Destination Settings page is correct.

 

We encountered an error while attempting to check the type or version for this [destination]. Please select the correct destination type and try again.
This means: Fix it by:
The destination type doesn’t match the destination you selected in Stitch.

For example: you select Redshift in Stitch, but we detect that it’s actually a PostgreSQL destination.
  • Verify that you’ve selected the correct destination type in Stitch, and
  • Verify that the credentials you’ve entered are for that destination type.
If the incorrect destination type was chosen, select the correct destination type and try completing the setup again.

 

We encountered an internal error while checking the connection.
This means: Fix it by:
Stitch encountered an internal issue. This error is usually transient and will resolve on its own, but if it persists, please check our Status Page for reported service outages.

Checking Stitch’s Status

If the troubleshooting steps detailed above don’t resolve the issue or if the errors persist, we recommend checking Stitch’s Status Page for reported service issues.

Contacting Support

If there’s no reported service issue on our Status Page or you don't see the error you're receiving here, please get in touch with us.

To help us troubleshoot the problem quickly, please provide us with the following:

  • The exact error you’re receiving. Providing us with the text or a screenshot is ideal.
  • The type of destination. Ex: Redshift, PostgreSQL.
  • Verification that Stitch’s IP addresses are whitelisted.
  • Verification that the Stitch database user has the correct permissions for the type of destination you’re connecting.
Was this article helpful?
0 out of 0 found this helpful

Comments

Questions or suggestions? If something in our documentation is unclear, let us know in the comments!