Обсуждение: BUG #13463: fatal 28000 no pg_hba.conf entry for host

The following bug has been logged on the website:

Bug reference:      13463
Logged by:          Anastasiia
Email address:      nanaska_91@mail.ru
PostgreSQL version: 9.4.0
Operating system:   Windows Server 2012 R2
Description:

I can't connect to remote PostgreSQL database: error "28000 no pg_hba.conf
entry for host" occurs.

I've opened port 5432 in Firewall, my pg_hba.conf file looks like:

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# IPv4 local connections:
hostnossl     all     all     0.0.0.0/0     md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#host    replication     postgres        127.0.0.1/32            md5
#host    replication     postgres        ::1/128                 md5

But I can't connect anyway. What should I do? Please, help!

Thanks!

On 6/23/2015 9:09 AM, nanaska_91@mail.ru wrote:
> I can't connect to remote PostgreSQL database: error "28000 no pg_hba.conf
> entry for host" occurs.
>
> I've opened port 5432 in Firewall, my pg_hba.conf file looks like:

what is the listen_addresses parameter in postgresql.conf ?  the default
is to listen to localhost only.   change it to...

listen_addresses = '*'

and restart postgresql to take effect.



--
john r pierce, recycling bits in santa cruz

nanaska_91@mail.ru writes:
> I can't connect to remote PostgreSQL database: error "28000 no pg_hba.conf
> entry for host" occurs.
> I've opened port 5432 in Firewall, my pg_hba.conf file looks like:
> # IPv4 local connections:
> hostnossl     all     all     0.0.0.0/0     md5
> # IPv6 local connections:
> host    all             all             ::1/128                 md5

Most likely bet seems to be that your remote connection is coming in over
IPv6.  You're allowing IPv6 connections only from localhost in this
configuration.

Another possibility is that the client is trying to use SSL.  By default
I think most clients would fall back to non-SSL after failing, but maybe
you have it set up not to.

            regards, tom lane