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.
Applicable to Amazon S3 destinations only. This error occurs when the Stitch challenge file isn’t found in the specified S3 bucket.
The challenge file is used to test Stitch’s connection to the bucket. Stitch will surface this error if it cannot find the challenge file, whether because the file was removed or never created.
Troubleshooting
- If you still have access to the challenge file name, follow these instructions to create the file in your S3 bucket.
-
If you no longer have access to the challenge file name, you’ll need to create a new S3 destination using these instructions.
Note: Creating a new destination doesn’t mean you’ll need to re-replicate all of your data. During the destination change process, you can choose to pick up replication where it left off or to queue a historical re-replication.
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
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.
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.
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.
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
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.
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.