Stitch periodically performs checks on the connection to your destination to ensure the connection remains active and healthy. Below are some of the most common errors you might see if Stitch has trouble performing the connection check to your destination and how to resolve them.

Meaning

Stitch encountered an error when attempting to ‘talk’ to your destination.


Troubleshooting
  • Verify that the hostname entered in the Destination Settings page is correct.

    For Redshift and Postgres-RDS: check that the port has been removed from the end of the hostname string.

  • Verify that the port setting entered in the Destination Settings page is correct.

  • Verify that Stitch’s IP addresses (see below) are whitelisted.

    For Redshift and Postgres-RDS: Check that the Security Group and VPC Subnet associated with the database allows access from all Stitch’s IP addresses.

    • 52.23.137.21/32
    • 52.204.223.208/32
    • 52.204.228.32/32
    • 52.204.230.227/32
Meaning

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.


Troubleshooting

Verify that you’ve selected the correct destination type. If the incorrect destination type was chosen, select the correct destination type and try completing the setup again.

Meaning

Something went wrong during the communication with the database.


Troubleshooting

This is a transient error and should clear itself during the next replication job. If this error persists, refer to these troubleshooting tips to diagnose and treat the issue.

Meaning

The credentials that Stitch has for your destination are incorrect.


Troubleshooting

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.

Meaning

The connection timed out before Stitch could successfully establish a connection.


Troubleshooting

This error may be transient and resolve on its own, but if it persists, try the following before contacting support:

  • Verify that the port setting entered in the Destination Settings page is correct.

  • Verify that Stitch’s IP addresses (see below) are whitelisted.

    For Redshift and Postgres-RDS: Check that the Security Group and VPC Subnet associated with the database allows access from all Stitch’s IP addresses.

    • 52.23.137.21/32
    • 52.204.223.208/32
    • 52.204.228.32/32
    • 52.204.230.227/32
Meaning

Stitch encountered an internal issue.


Troubleshooting

This error is usually transient and will resolve on its own, but if it persists, please check our Status Page for reported service outages.


Contact Stitch support

To help us troubleshoot the problem quickly, we ask that you provide us with the following:

  1. The exact error you’re receiving. Providing us with the text or a screenshot is ideal.
  2. The type of destination. Ex: Redshift.

  3. Verification that the Stitch database user has the correct permissions for the type of destination you’re connecting.

Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.