From: | Justin Clift <jc(at)telstra(dot)net> |
---|---|
To: | Michael J Martin <mike(at)mike-martin(dot)com> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: pgAdmin can't connect to port 5432 |
Date: | 2004-08-16 00:24:11 |
Message-ID: | 411FFEAB.2080007@telstra.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi Michael,
In the PostgreSQL data directory on the server, there is a file called
"pg_hba.conf". (It stands for PostgreSQL "Host Based Access"
configuration I think)
This file contains the list of IP addresses plus user names and
databases that people are allowed to connect to remotely. The error
you're getting indicates that you've connected to the database server,
but it's not letting you actually "get in" because your IP address, user
name (and so on) isn't listed in this configuration file.
You'll need to add your details there, then tell the PostgreSQL server
to reload this configuration file:
$ pg_ctl reload
The configuration file itself is quite a lot of verbose text, describing
how to add entries in there. Generally you can just copy an existing
entry and change it appropriately.
Hope that helps.
Regards and best wishes,
Justin Clift
Michael J Martin wrote:
> Just to mention the error I get is not a 'process isn't running' error
> it is:
>
> Error connecting to the server: FATAL: no pg_hba.conf entry for host
> "212.159.49.21", user "mike", database "template1", SSL off
>
> Hope this helps.
>
> Michael
From | Date | Subject | |
---|---|---|---|
Next Message | paul.n.shortis | 2004-08-16 04:04:28 | pgadmin III - database backup / restore |
Previous Message | Andreas Pflug | 2004-08-15 23:49:40 | Re: pgAdmin can't connect to port 5432 |