#548 Error login postgresql in version 4.3.1

[Dwi Fahni Denni]

Since version 4.3.1 i can't login to PostgreSQL using same user and password configuration.

Unable to connect to PostgreSQL server: FATAL: password authentication failed for user "username"

[Jakub Vrána]

Please try to clear your cookies.

[Krief]

Hello,

I'm discovering Postgres 9.6 on new Debian Stretch plaform.
Installed Adminer version is 4.3.1 (with an SQLite3 enhancement).
I'm also having the same connection issue as original poster.

May I ask the following questions:

1. When Adminer and Postgres are installed on the same box, how does Adminer connect to Postgres database ? Using "local Unix socket" or "local IPv4 connection" ?

2. Unix socket is configured on my box pg_hba.conf file with:
   local all all peer
   Local IPv4 connection is configured with:
   host all all 127.0.0.1/32 md5
   Is it correct to understand that when peer method is used (Unix socket), no password should be given to Adminer login screen ?
   Is it correct to summurize things this way "when peer method is used (Local IPv4 connection), Postgres user's password is required in Adminer login screen" ?

Best regards

[Melroy van den Berg]

Please open issue again! It's a bug for sure.

I will give the error:

Unable to connect to PostgreSQL server: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

That is because PostgreSQL version 9.6 is by default installed on Debian Stretch instead of 9.4. The socker file path becomes: /var/run/postgresql/.s.PGSQL.5433.

/var/run/postgresql# file .s.PGSQL.5433
.s.PGSQL.5433: socket

Notice the last version number change, which is the result of the new PostgreSQL version (5432 vs 5433)!

Please fix Adminer.

[Jakub Vrána]

Adminer doesn't specify the port, it can be changed in PHP configuration.