Support Article
FATAL: no pg_hba.conf entry for host
SA-64624
Summary
Pega 7.4 is installed on the AWS Cloud environment and the database configured is AWS Relational Database Services (RDS) PostgreSQL 9.6.3. The schema is created using Data Definition Language (DDL) scripts. However, error occurs and install.sh script fails.
Error Messages
/app/Pega/scripts/setupDatabase.xml:1467: Failed to connect using provided properties. FATAL: no pg_hba.conf entry for host "127.0.0.1", user "pega_cloud_stg_master", database "pega_cloud_stg_master", SSL off
Steps to Reproduce
- Provision AWS PostgreSQL 9.6.3 RDS.
- Install Pega 7.4 application using the install.sh script.
Root Cause
This behavior is as per Pega product design.
Resolution
Here's the explanation for the reported behavior:
PostgreSQL parameters are required for setupDatabase.properties used by the install.sh script in an AWS environment. AWS does not manually update the pg_hba.conf file as outlined in the Pega 7.4 Installation Guide. Additionally, SSL must be reenabled.
Update the setupDatabase.properties file as below.
pega.jdbc.driver.jar=/app/software/postgresql-42.2.2.jar
pega.jdbc.driver.class=org.postgresql.Driver
pega.database.type=postgres
pega.jdbc.url=jdbc:postgresql://<host>:5432/<dbname>?ssl=true&sslfactory=org.postgresql.ssl.NonValidatingFactory
pega.jdbc.username=xxxxxx
pega.jdbc.password=xxxxxx
pega.admin.password=xxxxxx
Published October 17, 2018 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.