Question
PGAdmin III - Access to database denied
I have a Pega 7.2.1 Personal Edition instance and want to investigate some of the data. I have used PGAdmin on other instances so I know it is working fine. However, on this instance I enter the server connection information, am prompted for the password then get an error:
"Access to database denied" - FATAL: no pg_hba.conf entry for host "<removed IP address>", user "pega", database "postgres", SSL off
I am then instructed to add something to the pg_hba.conf file, but when I make the edits I am still seeing the same errors again.
I do not have this issue with other Pega instances (like one's I used for training).
***Updated by moderator: Lochan to remove proprietary info; updated topic categories***
I created the pg_hba.conf file and entered the text below into the file. Restarted the VM and I was then able to access the database. Saved the file in my VM root folder.
host all all XXX.XXX.XX.X md5
***Updated by Moderator: Marissa to remove proprietary information***
Cheers!
Phil DeGuzman
Hi John,
What type of changes did you made?
To access a database on a PostgreSQL server, you first have to grant primary access to the server for your client (Host Based Authentication). PostgreSQL will check the pg_hba.conf file if a pattern that matches your client address / username / database is present and enabled before any SQL GRANT access control lists are evaluated.
The initial settings in pg_hba.conf are quite restrictive, in order to avoid unwanted security holes caused by unreviewed but mandatory system settings. You'll probably want to add/update something like
host all all XXX.XX.XX.XX/16 md5
/16 meaning that the first 16 bits(192.168) will be fixed and the remaining bits(0.0) can be anything.
This example grants MD5 encrypted password access to all databases to all users on the private network XXX.XX.XX.XX/16. You can use the pg_hba.conf editor that is built into pgAdmin III to edit the pg_hba.conf configuration file.
After changing pg_hba.conf, you need to trigger a server configuration reload using pg_ctl or by stopping and restarting the server process.
Let me know if this helps.
***Updated by Moderator: Marissa to remove proprietary information***