From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Eric Wadsworth <eric(at)wadhome(dot)org> |
Cc: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: SSH Tunnel port |
Date: | 2014-10-04 13:13:37 |
Message-ID: | CAECtzeXaGRt-mu7MOLC6jO_7wLmKO2ous0Dt8si4r8CeQZBSdg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi,
2014-10-04 15:04 GMT+02:00 Eric Wadsworth <eric(at)wadhome(dot)org>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Guillaume,
>
> No, you can tunnel already. I do it all the time to connect pgadmin to
> our production machines.
>
> Connect to the remote machine from your os, with the ssh command. You
> can use "-p 2222" to specify the non-standard port, and "-D 6432" to
> specify which port to tunnel, for the database traffic. I'll share the
> exact command I use on Monday, if you like, as it's on my work
> computer. Anyway, then you just connect pgadmin to a server on
> localhost, running on that tunneled port. Works great. :)
>
> (I'm assuming you're using a real OS. No idea how to do it in Windows,
> or if you can even do it.)
>
>
Thank you. I already knew that. Note that Stephen was asking about a UI
part of pgAdmin, not if it was possible to use an SSH tunnel outside of
pgAdmin.
--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Furry | 2014-10-04 17:38:07 | Re: Found a bug |
Previous Message | Eric Wadsworth | 2014-10-04 13:04:20 | Re: SSH Tunnel port |