Обсуждение: SSH Tunnel port
I need to tunnel through one server to my database server (which only allows connections from that server), but SSH is on a non-standard port. According to the internet, there is an update that would add a "Port" field to the settings window for this use case, but apparently that is not in a released version of pgAdmin yet. Any idea when this update will be included? Thanks for any info! -- Stephen
<p dir="ltr">Le 4 oct. 2014 13:42, "Stephen Cook" <<a href="mailto:sclists@gmail.com">sclists@gmail.com</a>> a écrit:<br /> ><br /> > I need to tunnel through one server to my database server (which only allows connections fromthat server), but SSH is on a non-standard port.<br /> ><br /> > According to the internet, there is an updatethat would add a "Port" field to the settings window for this use case, but apparently that is not in a released versionof pgAdmin yet.<br /> ><br /> > Any idea when this update will be included?<br /> ><p dir="ltr">It shouldbe in the beta release already available
-----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.) - --- wad On 10/04/2014 06:44 AM, Guillaume Lelarge wrote: > Le 4 oct. 2014 13:42, "Stephen Cook" <sclists@gmail.com > <mailto:sclists@gmail.com>> a écrit : >> >> I need to tunnel through one server to my database server (which >> only > allows connections from that server), but SSH is on a non-standard > port. >> >> According to the internet, there is an update that would add a >> "Port" > field to the settings window for this use case, but apparently that > is not in a released version of pgAdmin yet. >> >> Any idea when this update will be included? >> > > It should be in the beta release already available > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlQv8FQACgkQD+WWuyKfye0mZACfXIg4hQpkliYQVyFYjrZYG9Ga seUAn1JgEYFdDBJ6tDoSpVtvAHx1+n+w =ellz -----END PGP SIGNATURE-----
Hi,
2014-10-04 15:04 GMT+02:00 Eric Wadsworth <eric@wadhome.org>:
--
2014-10-04 15:04 GMT+02:00 Eric Wadsworth <eric@wadhome.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.
--