-
Notifications
You must be signed in to change notification settings - Fork 1
Description
error: no pg_hba.conf entry for host "10.0.39.12", user "master", database "merchencoder", no encryption
Identifying the Issue: The error "no pg_hba.conf entry for host..." typically arises due to a mismatch in the encryption algorithm for password authentication. With the upgrade to PostgreSQL 14.5, the default encryption algorithm changes to "scram-sha-256," which might not be supported by your client driver.
Root Cause Analysis: Further investigation revealed that this error occurs in newer PostgreSQL versions (14.x and above) due to the introduction of the 'scram-sha-256' algorithm in the JDBC driver. Older JDBC drivers may not support this newer algorithm, resulting in failed connections.
Resolution Steps: AWS provided the following steps to address the issue:
a. Modify the "password_encryption" parameter in your custom parameter group to "MD5."
b. Apply the updated parameter group to your instance.
c. Ensure synchronization of the new parameter group.
d. Reset the master user password to ensure the use of the MD5 encryption algorithm.
Reference: how to fix "FATAL: no pg_hba.conf entry for host" for aws rds postgres #21616