I am trying to connect Geoserver (installed in a VPS) to a PostgreSql database wich is running into my pc(localhost). I have follow the steps to allow this kind of connection(I do not know if all needed):
POSTGRESQL:
1.- Edit pg_hba.config of PostgreSql to allow Ip of VPS(Geoserver):
host all all ip_VPS/24 md5
2.- Edit postgresql.conf to allow remote connections:
listen_addresses ='*'
WINDOWS:
1.- Firewall configuration to allow Ip(VPS) access.
,but i still getting this connection error:
Unable to obtain connection: Cannot create PoolableConnectionFactory
(Connection to My_Ip(pc):5432 refused. Check that the hostname and
port are correct and that the postmaster is accepting TCP/IP
connections.).
Would i have to make other configuration ?.
Thanks in advance.
0k. You have in pg_hba.config:
host all all ip_VPS/24 md5
Maybe you should try this:
host all all ip_VPS/24 trust
Then you should restart postgres.
(For the parameter "trust" or "md5" I recommend reviewing:
www.postgresql.org/docs/9.5/static/auth-pg-hba-conf.html)
Greetings.
Related
I have a remote heroku database ('hobby' tier) and want to establish a remote psql connection but when I type:
heroku pg:psql
I am receiving the following error:
psql: could not connect to server: Operation timed out
Is the server running on host "ec2-54-163-230-199.compute-1.amazonaws.com" (54.163.230.199) and accepting
TCP/IP connections on port 5432?
I've edited postgresql.conf such that
listen_addresses = '*'
and added the line:
host all all 0.0.0.0/0 md5
to pg_hba.conf as I thought the issue may be my postgres configuration only accepting connections to localhost, but having restarted Postgres I am still getting the same error.
Anyone have any advice on what may be going wrong? If my firewall is blocking this would anyone have any advice on how to change that? Thanks in advance.
There must be network restrictions or firewall settings as it should work without making changes to conf file.
I cannot connect to my postgresql instance remotely on port 5432. Connection times out. I cannot connect remotely using psql, pgAdmin or telnet. I feel like I have everything configured correctly. Postgresql has been restarted several times with these settings. Remote connection works fine.
What could I be missing?
netstat:
postgressql.conf
pg_hba.conf:
Try referring this link for help
https://www.thegeekstuff.com/2014/02/enable-remote-postgresql-connection/?utm_source=tuicool
in short you have to the following steps
1. Add the following line to the pg_hba.conf server. This will allow connection from “192.168.xxx.xx” ip-address (This is the client ip)
# vi /var/lib/pgsql/data/pg_hba.conf
host all all 192.168.xxx.xx/xx trust
Change the Listen Address in postgresql.conf
# grep listen /var/lib/pgsql/data/postgresql.conf
listen_addresses = '*'
Test the Remote Connection
You just need to change the method md5 to trust and and enter the address as 0.0.0.0/0.
Open the config file
vi /var/lib/pgsql/data/pg_hba.conf
Insert the following line
host all all 0.0.0.0/0 trust
Maybe it will work.
I successfully installed postgres through homebrew, and i set it run automatically by doing
launchctl load ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist
So, right now i can access to psql from my terminal (i use iterm2 + oh my zsh)
psql (9.6.1)
Type "help" for help.
ty2kim=#
The problem is, postgres management tools like postico, pgadmin cannot access to it
for postico, error message is
could not connect to server: Connection refused
Is the server running on host "localhost" (::1) and accepting
TCP/IP connections on port 5435?
could not connect to server: Connection refused
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5435?
which is weird because from my understanding, accessing to the database from terminal and management tools are basically the same if configured correctly
My pg_hba.conf and postgresql.conf are set as default (didn't make any changes there), but i tried doing
listen_addresses = 'localhost'
=>
listen_addresses = '*'
(restart server)
still didn't work
Please help!
Port 5435 is not standard for PostgreSQL. Are you sure PG is running on it? If you didn't change it in postgresql.conf it must be 5432. Please check it.
must check pg_hba.conf. If there doesn't have much restriction, you can put to end of this file by below line:
host all all all trust
After that, reload/restart instance.
Check if your PC is using firewall. If yes, please turn off it.
I just recently install PostgreSQL on our server via SSH. The installation went successful, until the time I tried to connect to it using pgAdmin on my Windows machine.I received this kind of error:
could not connect to server: Connection refused (0x0000274D/10061) Is
the server running on host "xxx.xxx.xxx.xxx" and accepting TCP/IP
connections on port 5432?
xxx.xxx.xxx.xxx = my server's public IP.
The docs suggest this can be fixed by setting the value of listen_addresses = '*' in the /etc/postgresql/9.1/main/postgresql.conf. I did that but still it won't let me.
additional error came up
FATAL: no pg_hba.conf entry for host "xxx.xx.xxx.xxx", user
"postgres", database "postgres", SSL on FATAL: no pg_hba.conf entry
for host "xxx.xx.xxx.xxx", user "postgres", database "postgres", SSL
off
xxx.xx.xxx.xxx = my IP address.
What seems to be I'm missing?
Things that could block a postgres connection:
misconfigured listen_address in postgresql.conf
selinux (?)
iptables
pg_hba.conf (although this should cause a different error, not server doesn't listen)
Can you connect to the server locally, if you ssh in and run psql?
On our internal dev servers, I just turn off selinux and iptables. This is a bad idea from a security standpoint, but it might serve as a temporary step to help you narrow down where the problem is.
You might need to change more than one configuration file. In your case, you probably need to edit pg_hba.conf, too. Search that file for "non-local connections".
I like to keep configuration files under version control. It's easier to recover from mistakes that way.
You probably need to restart the PostgreSQL server after making those changes.
After changing listen_addresses settings on the server, make sure to restart the PostgreSQL server (send SIGHUP to the postmaster process, with kill -HUP, etc).
Make sure that postgresql.conf port is set to 5432
Make sure that if a firewall is running on the server, that port 5432 is open for connections coming from the window's (client) machine you are using
Check pg_hba.conf to make sure that the subnet of your client machine is given access
Try using psql locally
So I had PostgreSQL working in Ubuntu 11.04 using 8.4(?), however, when I upgraded it also upgraded PostgreSQL to 9.1 and now I can't connect using JDBC.
I added the following to my pg_hba.conf
host all all 127.0.0.1/32 trust
host all all 0.0.0.0/0 trust
and the following to my postgres.conf...
listen_addresses = '*'
but I get the following connecting with SQuirrel
My Local PostgresSQL: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Any ideas?
Per this site the default port is 5432, however, per the postgres.conf file that came installed by default the port is set to 5433...
port = 5433
So if someone else has this problem try the new port.
I think it has to do with the install incrementing the port when it sees the existing 8.4
Perhaps a IPv4 vs IPv6 issue? Try adding this line
host all all ::1/128 trust
and try connecting to the hostname localhost.
If that's not a solution, please try md5 instead of trust and give the connecting user a password. Just to be sure to rule this out.