pg_settings still show localhost. I went back and added the line that someone suggested to my "pg_hba" file so the end of mine now looks like this: host all all 0.0.0.0/0 md5 host all all ::1/128 md5 When I run "netstat -nlt | grep 5432", I still only get "tcp 127.0.0.1:5432." As I mentioned be-fore, I also see "127.0.0.1" on various ports including 5432 but I have a listing for tcp6 that has my static IP using port 32305. Is it supposed to be like that? Also, her is the weird thing, I have two "postgresql.conf" and "pg_hba" files in two different locations. I have one in "/usr/local/pgsql/data" and another set at "/etc/postgresql/9.4/main." I just discovered this situation. I edited both sets of files to have the same setting and still nothing. It seems that some-thing very screwy is going on. Jason L. Amerson -----Original Message----- From: Tom Lane <tgl@xxxxxxxxxxxxx> Sent: Thursday, November 21, 2019 02:53 PM To: Mark Johnson <remi9898@xxxxxxxxx> Cc: Jason L. Amerson <drjason@xxxxxxxxxxxxxxx>; Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>; Adrian Klaver <adrian.klaver@xxxxxxxxxxx>; PostgreSQL <pgsql-general@xxxxxxxxxxxxxxxxxxxx> Subject: Re: Remote Connection Help Mark Johnson <remi9898@xxxxxxxxx> writes: > As I recall, if the listening address is set to '*' but is showing > localhost, then the problem you describe is likely due to missing an > IPv6 address in pg_hba.conf. No, the contents of pg_hba.conf don't directly impact the listen_addresses setting. Also, if that's where the problem is, I'd expect a failure complaining about "no pg_hba.conf entry for <connection info>". The reported "connection refused" message suggests strongly that the postmaster isn't actually listening on the desired port, which also implicates listen_addresses rather than anything else. (I think it could also be caused by a firewall filter, if the firewall is configured to send back a TCP RST rather than just drop the packet. But if "show listen_addresses" isn't showing what we expect, that's the first thing to fix.) The OP may well need to adjust pg_hba.conf too, but he's not got that far yet :-( regards, tom lane
