Creating an Information Services data source to PostgreSQL throws an error similar to: "Cause: FATAL: no pg_hba.conf entry for host "[HOST]", user "[USERNAME]", database "[DATABASE NAME]", SSL off".

Creating an Information Services data source to PostgreSQL throws an error similar to: "Cause: FATAL: no pg_hba.conf entry for host "[HOST]", user "[USERNAME]", database "[DATABASE NAME]", SSL off".

Creating an Information Services data source to a PostgreSQL database throws an error that is similar to the following:

Symptoms:
The following is an example of a typical error: Cause:
The user needs explicit access to the PostgreSQL database when it is accessed from remote machines.

Make the following changes to the PostgreSQL configuration files to address this behavior. If this is for a customer's environment, ensure that they discuss these options with their Database Administrators (DBAs) first.

 

============================

1). Add or edit the following line in your "postgresql.conf" file:

 

listen_addresses = '*'

2). Add the following line as the first line of your "pg_hba.conf" file. It allows access to all databases for all users with an encrypted password:

# TYPE DATABASE USER CIDR-ADDRESS  METHOD

host  all  all 0.0.0.0/0 md5

3). Once you have added these changes, restart the database server service.

============================

http://dba.stackexchange.com/questions/83984/connect-to-postgresql-server-fatal-no-pg-hba-conf-entry-for-host