How do I use and jump through one server to reach another using ssh on a Linux or Unix-like systems? Is it possible to connect to another host via an intermediary so that the client can act as if the connection were direct using ssh? Can you give me SSH ProxyCommand and ProxyJump example?

You can jump host using ProxyCommand.
Tutorial details
Difficulty level Easy
Root privileges No
Requirements ssh
Est. reading time 5m
Some times you can only access a remote server via ssh by first login into an intermediary server (or firewall/jump host). So you first login into to the intermediary server and then ssh to another server. You need to authenticate twice and the chain can be long and is not limited to just two hosts. This page provide SSH ProxyCommand example

Our SSH ProxyCommand example setup

     +-------+       +----------+      +-----------+
     | Laptop|       | Jumphost |      | FooServer |
     +-------+       +----------+      +-----------+


     +-------+       +----------+      +-----------+
     | Laptop|       | Firewall |      | FooServer |
     +-------+       +----------+      +-----------+

I can can only access a remote server named ‘FooServer’ via ssh by first login into an intermediary server called ‘Jumphost’. First, login to Jumphost:
$ ssh vivek@Jumphost
Next, I must ssh through the intermediary system as follows:
$ ssh vivek@FooServer

Passing through a gateway or two

I can connect to the target host named by first making a ssh connection to the jump host called and then establishing a TCP forwarding to the ultimate destination from there:
ssh -J Jumphost FooServer
ssh -J Jumphost vivek@FooServer
ssh -J
ssh -J

Command to use when the -J option not available

In older versions of openssh the -J is not available. So use the following syntax:
$ ssh -o ProxyCommand="ssh -W %h:%p Jumphost" FooServer
$ ssh -o ProxyCommand="ssh -W %h:%p"
$ ssh -o ProxyCommand="ssh -W %h:%p" root@wp-admin-server

The oldest clients don’t support the -W option

In this case the ssh -tt command. Instead of typing two ssh command, I can type the following all-in-one command. This is useful for connecting to FooServer via firewall called ‘Jumphost’ as the jump host:
$ ssh -tt Jumphost ssh -tt FooServer
$ ssh -tt vivek@Jumphost ssh -tt vivek@FooServer
$ ssh -tt vivek@Jumphost ssh -tt vivek@FooServer command1 arg1 arg2
$ ssh -tt vivek@Jumphost ssh -tt vivek@FooServer htop
$ ssh -tt vivek@Jumphost ssh -tt vivek@FooServer screen -dR


  • The -t option passed to the ssh command force pseudo-tty allocation. This can be used to execute arbitrary screen-based programs on a remote machine. Multiple -tt options force tty allocation, even if ssh has no local tty.

How to pass through a gateway using stdio forwarding

The syntax is simple as explained above. You no longer need nc installed due ProxyCommand syntax:
ssh -o ProxyCommand="ssh -W %h:%p"
Say the user accounts names are different on the two Unix or Linux server. Here, ‘tom’ is the account on the second machine which is the final target. The user ‘jerry’ is the account on the intermediary or jump host:

ssh -l tom \
      -o 'ProxyCommand ssh -l jerry %h nc 22' \
      -o 'HostKeyAlias' \

An updated version of my ~/.ssh/config file:

Host webserver
        ProxyCommand ssh -W %h:%p
Host mysftpserver
        ProxyCommand ssh -W %h:%p

Now all I have to do is type the following ssh command or sftp command:
ssh webserver

How to pass through One or more gateways/firewall using ProxyJump

OpenSSH version 7.3 or above includes simple syntax for ~/.ssh/config file:

Host forum
        User vivek

One can set multiple jump host using a comma-separated list and the servers will be visited in the order listed:

Host www-admin-box
        User vivek

How do I recursively chain gateways using stdio forwarding?

Try the following ProxyJump syntax hich is available starting with OpenSSH version 7.3 or above in your ~/.ssh/config file:

Host nixcraftserver1
        User vivek
        IdentityFile /home/vivek/.ssh/nixcraftserver1_e25519
        Port 22
Host nixcraftserver2
        User vivek
        IdentityFile /home/vivek/.ssh/nixcraftserver2_e25519
        Port 22
        ProxyCommand ssh -W %h:%p nixcraftserver1
Host nixcraftserver3
        User fred
        IdentityFile /home/vivek/.ssh/nixcraftserver3_e25519
        Port 22
        ProxyCommand ssh -W %h:%p nixcraftserver2

Next I type the following:
ssh nixcraftserver3

Say hello to the ProxyCommand with netcat (older method)

The syntax is as follows and works with all clients
$ ssh -o ProxyCommand='ssh firewall nc remote_server1 22' remote_server1
$ ssh -o ProxyCommand='ssh vivek@Jumphost nc FooServer 22' vivek@FooServer
## -t option is needed to run commands ###
$ ssh -t -o ProxyCommand='ssh vivek@Jumphost nc FooServer 22' vivek@FooServer htop

The netcat (nc) command is needed to set and establish a TCP pipe between Jumphost (or firewall) and FooServer. Now, my laptop (local system) is connected to Jumphost it now connected FooServer. In this example, the utility netcat (nc) is for reading and writing network connections directly. It can be used to pass connections to a 2nd server such as FooServer.

Update ~/.ssh/config file (older method with netcat [nc])

Edit the $HOME/.ssh/config file using a text editor such as vi, enter:
$ vi ~/.ssh/config
Append the following configuration:

Host fooserver
HostName FooServer
User vivek
ProxyCommand ssh vivek@Jumphost nc %h %p

Save and close the file. Where,

  1. Host fooserver : Set nickname of your choice.
  2. HostName FooServer : Set the real remote server/host name.
  3. User vivek : Set the real user name for remote server/host.
  4. ProxyCommand ssh vivek@Jumphost nc %h %p : Specifies the command to use to connect to the server. In this example, I’m using nc command. Any occurrence of %h will be substituted by the host name to connect, %p by the port, and %r by the remote user name.

To test enter:
$ ssh fooserver
To see the details, pass the -v option to the ssh command. Here is another snippet:

Host server1
HostName v.server1
User root
Port 22
ProxyCommand ssh root@v.backup2 nc %h %p %r

Now, run:
$ ssh -v server1
Sample outputs:

OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/veryv/.ssh/config
debug1: /Users/veryv/.ssh/config line 1: Applying options for server1
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 102: Applying options for *
debug1: Executing proxy command: exec ssh root@v.backup2 nc v.server1 22 root
debug1: permanently_drop_suid: 501
debug1: identity file /Users/veryv/.ssh/id_rsa type 1
debug1: identity file /Users/veryv/.ssh/id_rsa-cert type -1
debug1: identity file /Users/veryv/.ssh/id_dsa type -1
debug1: identity file /Users/veryv/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr none
debug1: kex: client->server aes128-ctr none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA d2:07:84:79:21:a7:84:84:14:ef:f1:7a:84:a5:a1:7s
debug1: Host 'v.server1' is known and matches the RSA host key.
debug1: Found key in /Users/veryv/.ssh/known_hosts:37
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/veryv/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: Authentication succeeded (publickey).
Authenticated to v.server1 (via proxy).
debug1: channel 0: new [client-session]
debug1: Requesting
debug1: Entering interactive session.
debug1: Sending environment.
Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-52-generic x86_64)

 * Documentation:
Last login: Sun May 17 15:41:26 2015 from

The sftp syntax

The syntax is as follows:

sftp -o 'ProxyCommand=ssh %h nc 22' \
       -o '' \


You learned about SSH ProxyCommand and ProxyJump command with examples. Here is a quick summary:
SSH ProxyCommand and ProxyJump example
See openssh docs here for more info.

🐧 Get the latest tutorials on Linux, Open Source & DevOps via RSS feed or Weekly email newsletter.

🐧 13 comments so far... add one

CategoryList of Unix and Linux commands
Disk space analyzersncdu pydf
File Managementcat
FirewallAlpine Awall CentOS 8 OpenSUSE RHEL 8 Ubuntu 16.04 Ubuntu 18.04 Ubuntu 20.04
Network UtilitiesNetHogs dig host ip nmap
OpenVPNCentOS 7 CentOS 8 Debian 10 Debian 8/9 Ubuntu 18.04 Ubuntu 20.04
Package Managerapk apt
Processes Managementbg chroot cron disown fg jobs killall kill pidof pstree pwdx time
Searchinggrep whereis which
User Informationgroups id lastcomm last lid/libuser-lid logname members users whoami who w
WireGuard VPNAlpine CentOS 8 Debian 10 Firewall Ubuntu 20.04
13 comments… add one
  • Jalal Hajigholamali May 18, 2015 @ 8:41

    Thanks a lot…
    Nice article

  • DrScriptt May 19, 2015 @ 2:40

    Good article Vivek.

    If you liked this and want to see how to take it to the next level, take a look at my Empowering OpenSSH article

    I use this technique to reach hundreds of servers 2 or 3 or 4 jumps deep in my clients network. It works like a champ.

  • Rabin May 19, 2015 @ 16:46

    just a note, you can use -W instead running nc
    ProxyCommand ssh gateway -W %h:%p

    • MJ Mar 18, 2017 @ 11:50

      I don’t have `nc` on the jumpbox, so this worked better. Thanks :)

  • Mike T. May 23, 2015 @ 22:34

    Why are you using fooserver in your example?? Is that server 1, server 2, a server at a Chinese food restaurant?? Just use common sense terms (server 1, server 2, local computer, etc.) so that people can understand what you are trying to say.

    Please stop the Foo pollution!! Dumbest thing Linux people do.

  • Mike Hunt Feb 9, 2016 @ 4:44

    I agree with the use of FOO(server).. At first I wasn’t sure and had to look twice. Caught on finaly (my bad?). SERVER1, SERVER2 etc would allow more folk to understand IMHO (My Humble Opinion:). Thanks for the info however..

  • Master Foo May 30, 2016 @ 15:16

    To all the people complaining about the use of Foo: Please go read up on unix hacker culture. There is a rich history behind the chosen meta-syntactic variables in this example. The way I see if, if you are trying to learn SSH before FOO you need to take a step back and read a few dusty books. Show some respect for those who came before you (and provided all this great free software).

    • Master F̶o̶o̶ Jun 20, 2016 @ 9:30

      I don’t know about what hacker culture you’re talking about. And not sure if I really care about it. I am an exclusive UNIX user/sysop/dev since 1994 and always find foo bar bah behehe annoying and more like today’s pseudo-language of lol, rofl, etc, that only shows lack of imagination and shallowness, the same over-confident mindset that gave birth to RTFM partly from inability to verbalize one’s supposed knowledge, partly, and mostly, from the lack of it.
      I bet you’re a perl guy, just because its gibberish syntax makes you feel special.

      • FooDefender Aug 8, 2017 @ 2:13

        Since only 1994? Get off my lawn!

  • Old Unix Dude May 30, 2016 @ 15:17

    Great article however you should be using ‘ssh -W’ instead of ‘ssh … nc’ for the “hop” command.

  • Dale Dec 9, 2020 @ 17:24

    I Have tried to set this up, but when I connect to the openssh jump server and jump to a cisco device it only returns one line at a time and you can not see the entire output. What do I need to do fix this?

    • 🐧 Vivek Gite Dec 9, 2020 @ 19:49

      Start the ssh session with the -v option and see if you get any warnings or errors:

      ssh -v arg1 arg2 user@host

      Look into DNS in your sshd_config on server and turn it off or configure proper name resolution:

       UseDNS no

      Look into multiplexing

Leave a Reply

Your email address will not be published.

Use HTML <pre>...</pre> for code samples. Still have questions? Post it on our forum