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.

In this reference:

Common connection errors

The following errors are applicable to all destinations:

I/O error 

An I/O error occurred while sending to the backend.
Applicable to

Amazon Redshift and PostgreSQL-backed destinations
Level Critical
Category

Communication
Potential cause(s)

A transient communication error with the database occurred.
Suggested action(s)

If this error persists, refer to these troubleshooting tips to diagnose and treat the issue.

Back to Common error list
Back to top

Connection refused 

Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Applicable to

All destinations
Level Critical
Category

Communication
Potential cause(s)

Stitch is unable to connect to the destination. This is typically a result of incorrectly entering connection details into Stitch, or a failure to whitelist Stitch’s IP addresses.
Suggested action(s)
  • Verify that the hostname entered in the Destination Settings page is correct.
  • Verify that the port entered in the Destination Settings page is correct.

  • Verify that Stitch’s IP addresses are whitelisted.

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

Back to Common error list
Back to top

Connection timeout 

Connection timed out.
Applicable to

All destinations
Level Critical
Category

Communication
Potential cause(s)

The connection to the destination timed out before Stitch could successfully establish a connection.
Suggested action(s)

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

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

Back to Common error list
Back to top

Incorrect password for database user 

FATAL: Password authentication failed for user [user_name]
Applicable to

All destinations
Level Critical
Category

User credentials
Potential cause(s)

The credentials for the database user authorizing the connection are incorrect.
Suggested action(s)

Verify that the password entered into the Destination Settings page for the authorizing user is correct.

Back to Common error list
Back to top

Database type mismatch 

We encountered an error while attempting to check the type or version for this destination. Please select the correct destination type and try again.
Applicable to

All destinations
Level Critical
Category

Incorrect Stitch setup
Potential cause(s)

The destination type doesn’t match the destination you selected in Stitch.

For example: You select Amazon Redshift in Stitch, but we detect that it’s actually a PostgreSQL database.
Suggested action(s)

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.

Back to Common error list
Back to top

Internal error 

We encountered an internal error while checking the connection.
Applicable to

All destinations
Level Critical
Category

Internal
Potential cause(s)

Stitch encountered an internal issue.
Suggested action(s)

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

Back to Common error list
Back to top

Amazon S3 connection errors

Missing challenge file 

An error occurred (404) when calling the HeadObject operation: Not Found
Applicable to

Amazon S3 destinations
Level Critical
Category

Destination setup
Potential cause(s)

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.
Suggested action(s)
  • 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.

Back to Amazon S3 error list
Back to top

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.