Diagnosing phpPgAdmin Login Issues

Introduction

The following are some basic steps that you can take for diagnosing login issues for PHPPGAdmin. 

Procedure

Check to be sure that the /var/lib/pgsql/data/pg_hba.conf file is valid. It should look something like this:

# TYPE DATABASE USER CIDR-ADDRESS METHOD

# "local" is for Unix domain socket connections only
# IPv4 local connections:
# IPv6 local connections:

local samerole all md5
host samerole all 127.0.0.200 255.255.255.255 pam pamservice=postgresql_cpses
host samerole all 127.0.0.1 255.255.255.255 md5
host samerole all ::1/128 md5
local all postgres md5
host all postgres 127.0.0.1 255.255.255.255 md5

Next, check to ensure that the permissions and ownership of the cPanel session keys directory are correct. Here is an example of the correct ownership and permissions:

namei -l /var/cpanel/cpses/keys/
f: /var/cpanel/cpses/keys/
dr-xr-xr-x root root /
drwxr-xr-x root root var
drwx--x--x root root cpanel
drwxr-x--- root cpses cpses
drwxr-x--- root cpses keys

Finally, ensure that connections to 127.0.0.200 on port 5432 are not going through. This can be tested with telnet:

# telnet 127.0.0.200 5432
Trying 127.0.0.200...
Connected to 127.0.0.200.
Escape character is '^]'.
^]q
telnet> q
Connection closed.

Connectivity over this local address is needed for PAM authentication to set up the temporary session users when accessing phpPgAdmin.