I have a SOCKS5 proxy set up through PuTTY with port 7777 configured as a dynamic port. I can use firefox/filezilla/etc by configuring them to use a SOCKS proxy with localhost and port 7777. But I can't figure out how to ssh (through Cygwin) to a remote server by using the dynamic port. Is this possible?

I've tried using ProxyCommand via the following method.

  1. Create ~/.ssh/config with the following line:

    ProxyCommand /usr/bin/nc -X connect -x %h %p
  2. Run ssh -p22 user@remotehost

The message I get is ssh_exchange_identification: Connection closed by remote host

  • 1
    To make a program whuch does not support SOCKS go through SOCKS, you can use a so-called proxifer; see en.wikipedia.org/wiki/Comparison_of_proxifiers . In particular, I recommand my open source tun2socks proxifer ( code.google.com/p/badvpn/wiki/tun2socks ). Commented Jul 26, 2012 at 15:34
  • Thanks for the comment Ambroz. I need it to work in cygwin, and I see from the wikipedia page on proxifiers that all of the ones it mentions are either not implemented in cygwin or not applicable. Is there a way to get a proxifier to work in cygwin?
    – Rusty Lemur
    Commented Jul 26, 2012 at 15:41
  • you don't need it to specifically support Cygwin. Cygwin programs are in the end just Windows programs, but with a POSIX interface implemented as a library. If a proxifier works on Windows, it should be able to proxify Cygwin programs just fine. Commented Jul 26, 2012 at 16:50

6 Answers 6


You are using 'connect' for HTTPS as your proxy version, this is from man nc:

-X proxy_version Requests that nc should use the specified protocol when talking to the proxy server. Supported protocols are ''4'' (SOCKS v.4), ''5'' (SOCKS v.5) and 'connect' (HTTPS proxy). If the protocol is not specified, SOCKS version 5 is used.

So you should use the following to use SOCKS 5:

ProxyCommand /usr/bin/nc -X 5 -x %h %p

Or simply:

ProxyCommand /usr/bin/nc -x %h %p

I hope it helps.

  • Thanks Saman, that worked! Also, thanks for the explanation, it helps.
    – Rusty Lemur
    Commented Jul 26, 2012 at 18:19
  • The ProxyCommand must be the first line of your ~/.ssh/config', or else nested inside a specify Host` section. Not really sure why. It doesn't work if it's the last line in the ~/.ssh/config Commented Jul 14, 2016 at 19:21
  • @AaronMcDaid: From man ssh_config: "For each parameter, the first obtained value will be used." Therefore... global settings need to be before any Host sections. The last line of ~/.ssh/config is part of the final Host section.
    – mpb
    Commented Jun 26, 2017 at 2:41
  • Worth mentioning is that netcat is in /bin/nc on Debian and Ubuntu. Commented May 18, 2018 at 10:25
  • 2
    Worth noting that netcat-traditional doesn't work. Install netcat-openbsd for this purpose.
    – iBug
    Commented Mar 11, 2022 at 17:01
ssh -o ProxyCommand='nc --proxy-type socks4 --proxy %h %p' user@host

fc19 x86_64, Ncat: Version 6.25

  • just curious - why proxy-type socks4?
    – suspectus
    Commented Oct 19, 2013 at 9:57
  • 4
    Can you add a little more explanation to this to say why it's the solution.
    – ChrisF
    Commented Oct 19, 2013 at 10:48
  • 1
    @ChrisF it is the same as accepted solution, but it is one-liner! No need to modify any config file.
    – j123b567
    Commented Dec 2, 2015 at 9:39
  • 2
    This is the nmap ncat program (comes via apt install nmap on APT systems like Ubuntu and Debian), which is different from netcat (be it netcat-openbsd or Hobbit's netcat-traditional).
    – Adam Katz
    Commented Nov 5, 2016 at 0:07
  • 1
    @suspectus related to @Adam Katz comment, the proxy-type is socks4 because the nmap ncat program didn't support sock5 until more recently. Indeed, this is an issue even now (Nov 2017), as RHEL 7/Centos 7 switched to the nmap package but used an older build that does not support socks5
    – Randall
    Commented Nov 27, 2017 at 16:09

tsocks (http://tsocks.sourceforge.net/) is a nice wrapper that uses LD_PRELOAD to make any program use SOCKS proxy transparently:

tsocks ssh example.com

Just works, remember to configure SOCKS proxy IP in /etc/tsocks.conf

  • it's too complex to have a configuration file
    – Jiang YD
    Commented Mar 14, 2017 at 3:10
  • 1
    tsocks is the only solution that worked for me, so I think this is an important answer to maintain here. the tsocks config file is fairly simple
    – Arlo
    Commented Jul 23, 2020 at 22:50
  • 1
    thanks. it's straightforward to use. just use export LD_PRELOAD=libtsocks.so
    – Akhil
    Commented Nov 19, 2021 at 8:44

Just to make it more simple, you could put these in ~/.ssh/config

host = example.com
ProxyCommand nc -X 5 -x %h %p

Any ssh command in terminal will now get through this proxy.

  • it's pity, netcat not support socks5 with username:password
    – yurenchen
    Commented Sep 20, 2022 at 20:58

This following command will do, to just use nc:

ssh examplehost.com -o "ProxyCommand=nc --proxy localhost:7000 %h %p"

Default is HTTP proxy, there is an HTTP proxy running on port 7000.

  • 1
    ssh root@server -p 22 -o "ProxyCommand=nc -X 5 -x %h %p" works
    – a55
    Commented Apr 21, 2021 at 9:27

ssh is able to understand ALL_PROXY environment variable so apparently something like this

ALL_PROXY=socks5:// ssh example.com

does the trick also for me at least.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .