Skip site navigation (1) Skip section navigation (2)

Re: ssl tunneling in postgres 8.1

From: "Obe, Regina" <robe(dot)dnd(at)cityofboston(dot)gov>
To: "P Kapat" <kap4lin(at)gmail(dot)com>,<pgsql-novice(at)postgresql(dot)org>
Subject: Re: ssl tunneling in postgres 8.1
Date: 2008-11-19 08:22:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice

Sorry about that I should have elaborated on the optional in that article. I'll update that article with this if this works for you.

 There is actually nothing magical about 5432.  Its just that if you have the ports the same on local and remote, you just need one forwarding rule.  If you are forwarding to different ports -  then you need a rule to go one way and a rule to go the other way.

Anyrate to fix your problem -  your tunneling should look something like this

R5432  -- > localhost:5433
L5433   --> localhost:5432

Hope that clarifies it.


-----Original Message-----
From: pgsql-novice-owner(at)postgresql(dot)org on behalf of P Kapat
Sent: Wed 11/19/2008 2:57 AM
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] ssl tunneling in postgres 8.1
On 11/18/08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Huh.  It should work then ... and does work when I try it here.
> Are you sure you put the right port numbers in the SSH command
> line (eg, 5432 is really the port Postgres is listening to)?

Thanks Tom. Your patience is extremely valuable to me. I need to get
this sorted out. So...

Something ridiculous is going on here.... I have a XP machine (say
'duh', different from 'bar' but behind the same router) at home. I
installed pgadminIII (just the frontend, not with the whole postgresql
server) from here:

And I followed the "ssh tunneling via PuTTY" instructions from here (verbatim):

And voila, everything worked perfect!!! I was able to connect to the
postgres server on foo (or bar). NOTE THE PORTS:

Source port: 5432 (on foo, I guess)
Destination: localhost:5432 (on duh, same 5432!!!)

The site also notes this:  "For personal desktop use, we tend to use
localhost:5432 (if you are not running a postgresql dev server
locally) or localhost:someotherunusedport (e.g. localhost:5433)"

Now, I do not understand this statement completely! If I use
"localhost:5433" in the Destination box in PuTTY, then I get the
following TCP error in pgadmin:

Server doesn't listen
The server doesn't accept connections: the connection library reports
could not connect to server: Connection refused (0x0000274D/10061) Is
the server running on host "" and accepting TCP/IP
connections on port 5433

Why is 5432 so sacred on the client side? For connecting from 'bar' to
'foo' (or vice versa), I can not do this, there is already a local
postgresql server running on 5432.


--------------------------------------  #402424

Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
To make changes to your subscription:

The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.

In response to


pgsql-novice by date

Next:From: Ognjen BlagojevicDate: 2008-11-19 09:42:19
Subject: Mailing list problem: TLD .rs not recognized as valid
Previous:From: P KapatDate: 2008-11-19 07:57:08
Subject: Re: ssl tunneling in postgres 8.1

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group