I enabled "host all all 0.0.0.0/0 trust" in pg_hba.conf and restarted Postgres, but I still get the same behavior. It looks like password authentication is not the issue. I enabled MD5, but I didn't know I would have to do anything else; from this test, that doesn't seem to be the problem. I'm getting the load balancer info. Thanks again.
Howard ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, August 25, 2019 12:48 PM, Howard Wells <mr...@protonmail.com> wrote: > Thanks for the replies. I am getting the information requested by Adrian > Klaver. Rob Sargent, I am going to temporary enable full trust because the > password authentication could be the issue. Then I'll write back. > > Howard > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Sunday, August 25, 2019 12:20 PM, Rob Sargent robjsarg...@gmail.com wrote: > > > > > > > > > > > > > > > > > console. > > > > > > > The pg_hba.conf has these lines enabled: > > > > > > > pg_hba.conf: > > > > > > > host all [username] 0.0.0.0/0 trust > > > > > > > host all all 0.0.0.0/0 md5 > > > > > > > host all all ::/0 md5 > > > > > > > host all all all > > > > Who is encrypting the password? > > > > >
