Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got PostgreSQL installed on a Ubuntu server and I'm trying to connect to that server using PGAdmin on a remote macbook.

I've created an ssh tunnel -

macbook:~postgres$ ssh -L 5423:localhost:5432

And I can connect using psql on the macbook as expected -

macbook:~ me$ psql -U postgres -p 5423 -h localhost

In the 'New Server Registration' window on PGAdminIII I'm entering the following credentials -

Name - MyServer
Host - localhost
Port - 5423
Maintenance DB - postgres
Username - postgres
Password - <remote_postgres_password>

However the connection fails -

Error connecting to the server: FATAL: password authentication failed for user "postgres"

Not sure what's going on here, these seem to be the same credentials I've used for psql.

My pg_hba.conf file only has the following lines -

# Database administrative login by Unix domain socket
local   all             postgres                                peer
# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
host    all             all               md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
share|improve this question
First place I'd look is the postgres lines in /etc/postgresql/9.X/main/pg_hba.conf – datashaman Nov 15 '12 at 17:42
Thanks @MarlinForbes. I've spent an hour or so playing around with pg_hba.conf to no avail. I'll update my question to include my current configuration. – Aidan Ewen Nov 15 '12 at 17:58

Check if changing your postgres local line to trust (instead of peer) works.

share|improve this answer
Thanks Marlin, I'm trying to make my db server as secure as possible. I don't really want to start using trust authentication (particularly not on the postgres role). – Aidan Ewen Dec 8 '12 at 20:05
Agreed, I'm suggesting trying that to see if it's the authentication that is the issue. Don't leave it like that if that's a problem. :) – datashaman Dec 12 '12 at 8:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.