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".

book

Article ID: KB0083483

calendar_today

Updated On:

Products Versions
Spotfire Analyst All Versions

Description

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

Unable to connect to data source "/shared/PostgreSQL_Test" at

   "jdbc:postgresql://10.107.162.198:5432/public".  Make sure the URL information, user name and password are correct.  [datasrc-3961025]

Cause: FATAL: no pg_hba.conf entry for host "10.107.162.176", user "postgres", database "public", SSL off

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

Note: This may also occur when using the Spotfire data connector for PostgreSQL, but this has not been tested using the data connector. 

Symptoms:
The following is an example of a typical error:
 
 "Cause: FATAL: no pg_hba.conf entry for host "[HOST]", user "[USERNAME]", database "[DATABASE NAME]",  SSL off"
 
Cause:
The user needs explicit access to the PostgreSQL database when it is accessed from remote machines.

Issue/Introduction

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".

Resolution

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.

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

Additional Information

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