Thread: BUG #15284: SSL connection is off

The following bug has been logged on the website:

Bug reference:      15284
Logged by:          Chiranjeevi Medicharla
Email address:      chiranjeevi@greycampus.com
PostgreSQL version: 9.5.13
Operating system:   centos
Description:

psql -h 185.168.192.147 -U postgres
psql: FATAL:  no pg_hba.conf entry for host "183.82.105.209", user
"postgres", database "postgres", SSL off
my pg_hba.conf has 
 "local" is for Unix domain socket connections only
local   all             all                                     md5
# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
host    all             all             0.0.0.0/0               md5
host    all             all              ::/0                   md5
host    all             all             all                     md5
hostssl all             all             0.0.0.0/0               md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     postgres                                peer
#host    replication     postgres        127.0.0.1/32            ident
#host    replication     postgres        ::1/128                 ident
and my
postgresql.conf  has
listen_address = '*'

=?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes:
> psql -h 185.168.192.147 -U postgres
> psql: FATAL:  no pg_hba.conf entry for host "183.82.105.209", user
> "postgres", database "postgres", SSL off

Hmm.  This line:

> host    all             all             0.0.0.0/0               md5

certainly ought to match that connection attempt.  So I can think of
two possibilities:

1. You are not looking at the pg_hba.conf file that the running server
is actually using.  "SHOW hba_file" could be used to confirm which one
that is.

2. You modified the file since the server was started, and didn't
SIGHUP the server to tell it to re-read the file.  ("pg_ctl reload"
would fix that, or your packager may have provided a wrapper script
for it.)

            regards, tom lane