| copyright |
|
||
|---|---|---|---|
| lastupdated | 2026-02-25 | ||
| keywords | troubleshooting for PostgreSQL, connecting postgresql deployment, postgres endpoints | ||
| subcollection | databases-for-postgresql-gen2 | ||
| content-type | troubleshoot |
{{site.data.keyword.attribute-definition-list}}
{: #troubleshoot-connect} {: troubleshoot} {: support}
[Gen 2]{: tag-purple}
If you encounter errors when connecting to your {{site.data.keyword.databases-for-postgresql_full}} deployment, review these common causes and resolutions. {: shortdesc}
You receive an error message or fail to connect to a {{site.data.keyword.databases-for-postgresql}} deployment. If reviewing application logs, you might see errors that mention intermittent connection timeouts or unable to connect. {: tsSymptoms}
Review the following information to troubleshoot and resolve common connectivity problems: {: tsResolve}
- An unsecured connection is a common cause of connectivity errors. All {{site.data.keyword.databases-for-postgresql}} connections use TLS/SSL encryption; {{site.data.keyword.databases-for-postgresql}} rejects unsecured connections. To avoid errors, make sure you configured a secure connection. Refer to Getting started for an example of a secure connection.
- If you are using a private endpoint, make sure that you specify connection strings that contain the private endpoint (see Credentials for private endpoints) and that you followed the steps in Connecting through private endpoints.
- If your application log captures a short connection interruption, that behavior is expected as a normal part of operations for this managed service. You want to design your applications to retry connections when errors are caused by a temporary loss in connectivity to your deployment or to {{site.data.keyword.cloud_notm}}. However, if you experience several minutes of connection interruption check the Cloud Status for the service. For more information, see Application-level high-availability.