psequel app fatal no pg hba conf entry for host ssl off

Psql: could not connect to server: Connection refused SELECT conninfo FROM repmgr.show_nodes WHERE (upstream_node_name IS NULL OR upstream_node_name = '') AND active=true Postgresql-repmgr 17:02:20.23 DEBUG => Executing SQL command: Postgresql-repmgr 17:02:20.22 INFO => Querying all partner nodes for common upstream node. Postgresql-repmgr 17:02:20.21 INFO => Validating settings in POSTGRESQL_* env vars. Postgresql-repmgr 17:02:20.21 INFO => Validating settings in REPMGR_* env vars. Postgresql-repmgr 17:02:20.18 INFO => ** Starting PostgreSQL with Replication Manager setup ** Postgresql-repmgr 17:02:20.17 DEBUG => Configuring libnss_wrapper. Postgresql-repmgr 17:02:20.17 Submit issues and feature requests at Postgresql-repmgr 17:02:20.17 Subscribe to project updates by watching Postgresql-repmgr 17:02:20.16 Welcome to the Bitnami postgresql-repmgr container We also re-generated the certs to only support TLS Web server authentication (removed the client authentication) - but the error persists - what is weird is that the log message says FATAL, but the DB(s) are actually up and we can connect via pgpool.įYI we also tried to change the cert's common name to match the database user name as mentioned in the above link and it still did not make a difference as far as the error is concerned.

According to the official docs - Postgres does seem to support client cert authentication (even though we don’t intend to use it here).

We are passing username/password at runtime to HELM and are able to successfully connect to the postgres DB from a desktop client - so why do you think Postgres is using client cert authentication?.

Thank you you say client cert authentications is not supported - can you please elaborate? I am creating an internal task in our backlog in order to provide that functionality, but I can not provide an ETA for this. Hi, Sorry, I didn't notice until now that you are trying to use client cert authentication, and that is not supported currently. # persistence.enabled Enable persistence using PVC # persistence disable to auto clean up pvc when deleting/uninstalling chart # volumePermissions.enabled Enable init container to adapt volume permissions # Name of an existing secret that contains the certificates # Enable TLS traffic support for end-client connections # If provided, PgPool will authenticate TLS/SSL clients by requesting them a certificate # Name of an existing secret that contains the certificatesĬertificatesSecret: postgres-certificates-tls # Whether to use the server's TLS cipher preferences rather than the client's

Hostssl all all 0.0.0.0/0 cert clientcert=1 # Otherwise, a nf will be generated based on the environment variables # You can use this parameter to specify the content for pg_hba.conf # postgresql.pgHbaConfiguration PostgreSQL client authentication configuration # fullnameOverride String to fully override template

# nameOverride String to partially override template (will maintain the release name) See repeating log of 'FATAL: connection requires a valid client certificate'.Create tls secret resource with data 'ca.pem', 'tls.key', 'tls.crt'.I have followed stackoverflow link, to verify the certs with the openssl verify CAfile command as well as updating the pg_hba.conf file to include 'clientcert=1' at the end of the hostssl config lines. I do not have anything connecting to the deployment and the logs show something is trying to connect via TLS. Postgres server log still shows 'FATAL: connection requires a valid client certificate' Enabled TLS on postgres and disabled TLS on pgpool.

Psequel app fatal no pg hba conf entry for host ssl off