Connecting to Puppet Enterprise PostgreSQL manually fails with an "Unable to connect...timeout expired" error

After you set up a new user with a password for the PE PostgreSQL database, you try to connect to Puppet Enterprise PostgreSQL from that account remotely, it fails with an Unable to connect...timeout expired error.

Error messages and logs

Unable to connect to server: connection to server at "<FQDN>" (<IP ADDRESS>), port 5432 failed: timeout expired

To connect to PE PostgreSQL, you must use the SSL certificates generated by the Puppet certificate authority. In other words, you need to connect using users generated by Puppet that are authorized by the Puppet CA certificate. If you try to connect by other methods, you get an Unable to connect error.

Version and installation information

PE version: All supported

Solution

You can run queries against PE PostgreSQL using PuppetDB API queries and using Puppet Query Language (PQL). Learn more from our API documentation and from this list of resources on PQL.

If you’d prefer to examine the data using pgAdmin, you can dump PE PostgreSQL data by running running /opt/puppetlabs/server/bin/pg_dump on the primary server and restoring it in a separate external PostgreSQL installation.

Note We can’t provide support for third-party software.