Boomi to Postgres connection error

Question

Hello,

I am trying to create a connection from Boomi to Postgres DB on Azure. My Postgres instance is a managed DB instance and I have the Boomi IP whitelisted via Networking settings. The user ID and Password works fine when I try from my local laptop but when I try from Boomi, I get below error.

Browse operation failed; Caused by: Unable to connect to database; Caused by: Unable to open database connection. FATAL: no pg_hba.conf entry for host "xx.xx.xx.xx", user "DB_User", database "Test_DB", no encryption; Caused by: FATAL: no pg_hba.conf entry for host "xx.xx.xx.xx", user "DB_User", database "Test_DB", no encryption

What am I missing with the configuration here? I am using JDBC driver for connecting to Postgres. I did restart the Postgres instance after updating the firewall rules but I still get the same error.

Answer 1

FATAL: no pg_hba.conf entry ... no encryption on Azure Database for PostgreSQL flexible server usually means the connection is reaching the server, but the server is rejecting it because the client connection settings do not meet the server requirements.

Given that:

• the same username and password work from a local laptop
• the Boomi IP is already allowed
• the error specifically says no encryption

The missing configuration is most likely SSL on the Boomi JDBC connection.

Use this troubleshooting path:

1. Verify the Boomi JDBC/PostgreSQL connection is configured to use SSL.
   • Azure Database for PostgreSQL enforces SSL by default.
   • A connection without SSL is rejected.
   • For PostgreSQL-style connection settings, use SSL mode Require.
2. Update the JDBC connection properties in Boomi so the PostgreSQL driver connects with SSL enabled.
   • The supported Azure guidance is equivalent to appending Ssl Mode=Require; to the connection string.
   • If full certificate validation is needed, also use Trust Server Certificate=false and provide the server CA certificate path.
3. Re-test from Boomi after saving the SSL setting.
   • If the error changes from no pg_hba.conf entry ... no encryption to a credential error, then networking is working and the next check is username/password.
   • If it connects, the issue was the missing SSL requirement.
4. If it still fails, confirm the firewall path again.
   • Azure Database for PostgreSQL flexible server blocks access by default unless the source IP is allowed.
   • Make sure the actual outbound Boomi runtime IP matches the IP range added in the server firewall rules.
   • Also ensure any client-side firewall allows outbound TCP 5432.
5. Validate with another client using the same Boomi-style settings.
   • Since local access already works, compare the local client connection properties against Boomi.
   • The key difference to check is SSL/encryption, not just username, password, host, and port.
6. If needed, review server logs to confirm the rejected connection details.
   • Log Analytics and server logs can be used to inspect failed connection attempts and verify the source IP and failure pattern.

For this specific error, firewall whitelisting alone is not sufficient. The no encryption portion indicates the Boomi JDBC connection is attempting a non-SSL connection, and Azure Database for PostgreSQL flexible server rejects that by default.

---

References:

• PostgreSQL troubleshooting
• Troubleshoot connection issues to Azure Database for PostgreSQL flexible server
• Firewall rules in Azure Database for PostgreSQL flexible server
• Password authentication failed for user <user-name>