DB01: FATAL error when configuring 360Suite Web Platform Web Platform Postgre SQL database

Symptom

DB01: FATAL: no pg_hba.conf entry for host "x.x.x.x/x", user "Postgres", "database "three60suite", SSL off

Environment

  • 360Suite Web Platform
  • PostgreSQL (any version)

Reproducing the issue

  1. Connect to the 360Suite Web Platform Administration Console.
  2. Fill in the details to configure the deployed PostgreSQL database.
  3. Click Save.
  4. The error occurs.

Cause

To connect to a PostGreSQL schema, 2 steps are required.

First you need a valid username and password, then the PostGreSQL configuration should authorize communication with the server initiating a client connection.
For security reasons, PostGreSQL allows local machine connections only.

In order to open connections from a distant machine, the default pg_hba.conf configuration file must be updated.

Resolution

  1. Navigate to folder <PostgreSQL>/data.
  2. Select and edit file pg_hba.conf.
  3. Specify the allowed connections to your PostGreSQL database.
  4. Restart Postgre SQL instance.
You can find more explanation and examples on the official PostGreSQL website: https://www.postgresql.org/docs/9.6/auth-pg-hba-conf.html

Sample configuration

# Allow any user from host 192.168.12.10 to connect to database
# "postgres" if the user's password is correctly supplied.
#
# TYPE  DATABASE        USER            ADDRESS                 METHOD
  host  all             all             0.0.0.0/0               md5
# Allow any user from host 192.168.12.10 to connect to database
# "three60suite" if the user's password is correctly supplied.
#
# TYPE  DATABASE        USER            ADDRESS                 METHOD
  host  three60suite    all             192.168.12.10/32        md5

Keywords

DB01, FATAL, no pg_hba.conf, entry,  host, user, Postgres, database, three60suite, SSL off, 360suite, WP

Product

Product or Product version

  • 360Suite Web Platform

Languages

  • English US
  • English UK
  • French

Last updated over 3 years ago