On Sunday, August 8th, 2021 at 12:50 AM, David G. Johnston <david.g.johnston@xxxxxxxxx> wrote:
> On Saturday, August 7, 2021, ourdiaspora <ourdiaspora@xxxxxxxxxxxxxx> wrote:
>
> > SHOW hba_file;
> >
> > /etc/postgresql/9.6/main/pg_hba.conf
>
> Please post the contents of this file. The one shown at the link is invalid.
local all postgres peer
# TYPE DATABASE USER ADDRESS METHOD
# "local" is for Unix domain socket connections only
local all all peer
# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 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 md5
#host replication postgres ::1/128 md5
local cpacweb cpaca trust
Ok. The first line is just redundant but I see that the last line has been made valid.
The reported error: FATAL: no pg_hba.conf entry for host "::1", user "cpaca", database "cpacweb", SSL off
When put against that pg_hba.conf file doesn’t make sense. That was the crux of the original post - everything here has just caused things to be worse off since now we are seeing not listening errors
David J.
