On 8/26/19 1:07 PM, Howard Wells wrote:
On my first post, I asked the person in charge of the firewall if 5432 was open
and he told me it was. When I checked it myself later, I found out that it
wasn't. Before I post to this list again, I'll check all assumptions myself.
"Only when I go to
On my first post, I asked the person in charge of the firewall if 5432 was open
and he told me it was. When I checked it myself later, I found out that it
wasn't. Before I post to this list again, I'll check all assumptions myself.
"Only when I go to the IP address of the server with the Post
On 8/25/19 2:59 PM, Howard Wells wrote:
I solved this problem. All four servers are behind a firewall, but port 5432
was not open on the firewall. When I opened 5432, the problem disappeared.
Glad you solved. Confused as to how:
1) From first post:
"All four are behind the same firewall, wi
I solved this problem. All four servers are behind a firewall, but port 5432
was not open on the firewall. When I opened 5432, the problem disappeared.
Thanks to Rob Sargent, Adrian Klaver and Condor for your help.
Howard
‐‐‐ Original Message ‐‐‐
On Sunday, August 25, 2019 12:20 PM, R
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
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, R
>
> console.
> The pg_hba.conf has these lines enabled:
> pg_hba.conf:
> hostall [username] 0.0.0.0/0 trust
> hostall all 0.0.0.0/0 md5
> hostall all ::/0
On 8/25/19 11:46 AM, Howard Wells wrote:
I have enabled logging. I chose the highest level of recording so I would have
the best chance of finding out what's wrong. My error log is written to a .csv
file. I initiated a browser-based transaction to insert records into a
database. That trans
I have enabled logging. I chose the highest level of recording so I would have
the best chance of finding out what's wrong. My error log is written to a .csv
file. I initiated a browser-based transaction to insert records into a
database. That transaction produced 1,299 records, with what ap
On 25-08-2019 02:54, Adrian Klaver wrote:
On 8/24/19 3:42 PM, Howard Wells wrote:
I have three servers behind a load balancer and a fourth server solely
for Postgres 10 database that is not behind the load balancer. All
four are behind the same firewall, with port 5432 open.
I have a simple
On 8/24/19 3:42 PM, Howard Wells wrote:
I have three servers behind a load balancer and a fourth server solely
for Postgres 10 database that is not behind the load balancer. All four
are behind the same firewall, with port 5432 open.
I have a simple browser-based html form to submit email add
> On Aug 24, 2019, at 4:42 PM, Howard Wells wrote:
>
> I have three servers behind a load balancer and a fourth server solely for
> Postgres 10 database that is not behind the load balancer. All four are
> behind the same firewall, with port 5432 open.
>
> I have a simple browser-based ht
I have three servers behind a load balancer and a fourth server solely for
Postgres 10 database that is not behind the load balancer. All four are behind
the same firewall, with port 5432 open.
I have a simple browser-based html form to submit email addresses, usernames
and passwords; the form
13 matches
Mail list logo
