PostgreSQL problem

[TiTo Sands]

I have installed PT3 with PostgreSQL by default without any modification in configuration files.
I can access the server via localhost (127.0.0.1), not via external IP 192.168.33.135 (even if I try it locally with pgAdmin).

I tried to change 'localhost' to '*' in the postgresql.conf

Code: Select all

listen_addresses = '*'      # what IP address(es) to listen on;

Now it's listen on 192.168.33.135 but when I try to connect this gimme another error.

[ img ]

I have added the line host all all 192.168.0.0/24 md5 to the pg_hba.conf file and it's the same error.

Any idea?

[kraada]

You need both listen_addresses = '*' in postgresql.conf and the host line in pg_hba.conf - once both lines are there, stop and restart your PostgreSQL server (Start --> Programs --> PostgreSQL --> Stop Service followed by Start --> Programs --> PostgreSQL --> Start Service) and then you should be able to connect. You may need to make sure that your router/firewall are configured properly as well.

[TiTo Sands]

You need both listen_addresses = '*' in postgresql.conf and the host line in pg_hba.conf - once both lines are there, stop and restart your PostgreSQL server (Start --> Programs --> PostgreSQL --> Stop Service followed by Start --> Programs --> PostgreSQL --> Start Service) and then you should be able to connect. You may need to make sure that your router/firewall are configured properly as well.

I have both lines, I follow the hint in the image and the error continue.

No router or firewall problem, it's connecting with the server and get access denied.
This seem to be a problem with the line host all all 192.168.0.0/24 md5 because it's not recognized.

[kraada]

You are certain there is no # sign in front of the line right? If the # sign is there, the line won't be interpreted.

[TiTo Sands]

There's not # sign in front of the line.

I only change the line listen_addresses = '*' and add my IP to the list in the file pg_hba.conf
Is there anything else I should change or install?

[kraada]

No, that should be it. Please create a remote session request and we'll help you out in a more real time fashion to get this resolved.