From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
---|---|
To: | David(dot)Bear(at)asu(dot)edu, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: tunneling through ssh |
Date: | 2004-08-18 23:21:24 |
Message-ID: | 200408181621.24097.scrawford@pinpointresearch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wednesday 18 August 2004 4:13 pm, David Bear wrote:
> I'm attempting to run pgsql through a tunnel. I'm using the default
> pg_hba.conf file for now which has the relevant information:
>
> ------------
> local all all
> trust
> host all all 127.0.0.1 255.255.255.255
> trust
> ------------
>
> I assume this means that the back end will bind to 127.0.0.1:5432
> since that seems to be the default port number.
>
> Yet, when trying to come through the tunnel I get this in my logs
> on the 'server' machine - the one running postgres backend.
>
> -----------
> Aug 18 16:00:40 dbsrv1 sshd[41006]: error: connect_to ::1 port
> 5432: Connection refused
> Aug 18 16:00:40 dbsrv1 sshd[41006]: error: connect_to 127.0.0.1
> port 5432: Connection refused
> Aug 18 16:00:40 dbsrv1 sshd[41006]: error: connect_to localhost
> port 5432: failed.
> -----------
>
> Am I missing something obvious?
Is PG set to accept tcp/ip connections? Check postgresql.conf for:
tcpip_socket=true
127.0.0.1 is connecting through tcp/ip, not local domain sockets.
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | David Bear | 2004-08-19 00:58:11 | Re: tunneling through ssh |
Previous Message | David Bear | 2004-08-18 23:13:12 | tunneling through ssh |