Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
We are integrating Qlik Replicate with PostgreSQL as source.
The documentation states that we should list 'trusted' IPs in PostgreSQL’s "pg_hba.conf" file, but it doesn’t appear to be required for actual use. Why is this mentioned?
https://help.qlik.com/en-US/replicate/May2025/Content/Replicate/Main/PostgreSQL/prereq_postgresql_so...
Thank you for your returns
Hello @JSCHRANZ ,
Thanks for the update. This is just a sample of a pg_hba.conf configuration. For general user access— especially over the open internet you should never use trust. Password-based authentication (or stronger) is strongly recommended; for example, MD5 works well with Qlik Replicate.
Regards,
John.
Hello @JSCHRANZ ,
Adding the trusted IP addresses to PostgreSQL’s "pg_hba.conf" file is mandatory. Otherwise, you may encounter an error like the following:
| [SOURCE_CAPTURE ]E: Could not connect to the server: FATAL: no pg_hba.conf entry for replication connection from host "192.168.1.212", user "postgres", SSL off [1020452] |
Where "192.168.1.212" is Replicate Server IP Address. This configuration is required by PostgreSQL itself.
Hope this helps.
John.
Hi,
thank you for your reply.
I understand the need to declare our IPs, but why should we "trust" them without any authentication to secure the access?
The given sample is:
host replication all 176.123.1.212/32 trust
Hello @JSCHRANZ ,
Thanks for the update. This is just a sample of a pg_hba.conf configuration. For general user access— especially over the open internet you should never use trust. Password-based authentication (or stronger) is strongly recommended; for example, MD5 works well with Qlik Replicate.
Regards,
John.