Use PD DigitalOcean PostgreSQL to find the intended database service’s endpoint and credentials, then configure a compatible PostgreSQL client with TLS and the correct database.

Open the connection window

Open the client service’s Information page and choose View connection details once the cluster is ready. Enable Client: Connection details on the package. Copy Host, Port, Database and Username from this service; reveal the masked password with Show only when needed.

Use the displayed port rather than assuming the default PostgreSQL port. The application database name and user must match the service you intend to access. Keep passwords and credential-bearing connection strings out of screenshots, public posts and support messages.

Configure the PostgreSQL client

The module’s example uses psql with sslmode=require, alongside the host, port, user and database. Configure those values through your application or database client’s supported fields. Supply the password through its credential setting or prompt, without placing it in a public command example.

Standard and Advanced Edition use PostgreSQL client settings, but an edition label does not establish every application’s compatibility with a selected engine version. Review the application and driver requirements before changing a live connection.

Configure CA and hostname verification

sslmode=require requests an encrypted connection; do not treat it as proof of hostname verification. Use Download CA certificate when offered and configure the client’s matching trust and verification settings. In libpq-based clients, sslmode=verify-full checks the certificate chain and the server hostname against the certificate when configured with trusted CA material.

Use the service’s hostname and the matching CA, and keep verification enabled. PostgreSQL explains these modes in its SSL client verification documentation. Other drivers may name the settings differently; follow their supported configuration rather than copying an unrelated client’s switch.

Diagnose a failed connection

Check the current service state, allowed source IPv4 address, host/port, database, username/password and TLS trust. A Running banner or visible stored credential is not a fresh application test; failed provider reads can leave stored status or endpoint values visible.

Review the error alongside the client software and version. Do not recreate the database or repeatedly reset the password to diagnose an uncertain failure. Role, extension, connection-pool and database administration are separate from the module’s connection window.

See the PD DigitalOcean PostgreSQL Blesta guide for related setup, or explore PD DigitalOcean PostgreSQL.