Connection Attempt Failed

Error Summary

• Hevo cannot connect to the PostgreSQL database instance due to network or connection setup issues.

Potential Causes

• The PostgreSQL service is stopped, paused, or in recovery following a crash.

• Incorrect connection parameters, such as hostname, port, database name, username, or password.

• Hevo IP addresses for your region are not in the database IP allowlist.

• The database user does not have the required permissions to access the database.

• The PostgreSQL server is terminating the connection due to internal issues.

Suggested Action(s)

• Ensure that the PostgreSQL service is running:

  • For Generic PostgreSQL, run the systemctl status postgresql command on your database host.

  • For Cloud-managed PostgreSQL services, such as Amazon RDS or Google Cloud, confirm the instance status in the cloud console.

• Verify the Source connection settings, including the database name, hostname, port, and user.

  Note: The default port for any PostgreSQL database is 5432.

• Ensure that your Source database is publicly accessible and accepts connections from the Internet.

• Specify the public IP address of your database as the Database Host. Validate it with your PostgreSQL database administrator.

• Ensure that Hevo IP addresses for your region are added to the database IP allowlist. If not, refer to the Allowlist Hevo IP addresses for your region section in your PostgreSQL variant documentation for the steps.

• For Amazon RDS databases, confirm that the Security Group and VPC subnet allow access from all Hevo IP addresses.

• Ensure that the database user has the necessary permissions to access your database.

• Connect to your Source database using an SQL client, such as DBeaver, with the configuration details.

• Check whether the database server is terminating connections due to full storage or too many concurrent connections. Review the reason in the cloud console or your database host.

Revision History