Description
While working with Postgres Source and Sink connector, you may encounter errors like below.
“Timed out while attempting to connect to your database. We will keep retrying. If this persists, please check that your database is up and reachable”
“Please verify the connection properties and make sure that an instance of Postgres is running on the host and accepting TCP/IP connections at the port, as well as that the database you are trying to read from exists.”
“Encountered error "FATAL: password authentication failed" while trying to connect to the database. Please make sure that the right password is provided to access the PostgresSQL database for the requested user.”
Applies To
Postgres Source and Sink connector
Confluent Cloud
Cause
These error messages can be seen in the Confluent Cloud UI while working with Postgres Source and Sink connector because of the database is either not ready or not reachable or database host is not accepting TCP/IP connection on the database port. All of these could lead to database connection failure.
Resolution
To resolve such error, we should check and verify the followings.
1. Make sure that the database are up, ready and reachable.
2. Make sure that there is no firewall or restriction on the database host/port restricting the TCP/IP connection from the client/connector.
3. Make sure to use correct username and password and also the database user should have the right permission to make the database connection and access to the database schema.
4. In case if private networking is required for fully-managed connectors, make sure to setup the proper networking beforehand. You may want to have PrivateLink, VPC (Virtual Private Cloud) Peering, or configuring private DNS records to ensure the connector can reach the required Oracle database. For details, refer Manage Networking for Confluent Cloud Connectors.
- For private networking connectivity IP address details, refer to Egress IP address ranges.
- Public egress IP address are used to securely establish outbound connections to endpoints of external data sources and sink over the secure public endpoints. To use set of public egress IP addresses, see Public Egress IP Addresses for Confluent Cloud Connectors.
- Refer this blog discussing on How to Securely Connect Confluent Cloud with Services on Amazon Web Services (AWS), Azure, and Google Cloud Platform (GCP)