Connect with SSH through a proxy

Question

I have no real idea what I m doing here so please bear that in mind if you can help me   I am trying to connect to my virtual server through a proxy but I can t connect  it just hangs  I m assuming this is because it s not getting through our proxy   I have tried exactly the same thing at home and it works perfectly  I m on OSX using Terminal to connect   Can anyone advise me how I can get through the proxy with SSH

User · Answer

Here s how to do Richard Christensen s answer as a one-liner  no file editing required  replace capitalized with your own settings  PROXYPORT is frequently 80     ssh USER FINAL DEST -o  ProxyCommand nc -X connect -x PROXYHOST PROXYPORT  h  p    You can use the same -o     option for scp as well  see https   superuser com a 752621 39364  If you get this in OS X    nc  invalid option -- X  Try  nc --help  for more information    it may be that you re accidentally using the homebrew version of netcat  you can see by doing a which -a nc command-- usr bin nc should be listed first    If there are two then one workaround is to specify the full path to the nc you want  like ProxyCommand  usr bin nc      For CentOS nc has the same problem of invalid option --X  connect-proxy is an alternative  easy to install using yum and works --   ssh -o ProxyCommand  connect-proxy -S PROXYHOST PROXYPORT  h  p  USER FINAL DEST

User · Answer

rogerdpack for windows platform it is really hard to find a nc exe with -X http proxy   however  I have found nc can be replaced by ncat  full example as follows   Host github com      HostName github com           ProxyCommand nc -X connect -x 127 0 0 1 1080  h  p          ProxyCommand ncat --proxy 127 0 0 1 1080  h  p      User git      Port 22      IdentityFile D  Users Administrator  ssh github key   and ncat with --proxy can do a perfect work

User · Answer

For windows   shoaly parameters didn t completely work for me  I was getting this error   NCAT DEBUG  Proxy returned status code 501  Ncat  Proxy returned status code 501  ssh exchange identification  Connection closed by remote host   I wanted to ssh to a REMOTESERVER and the SSH port had been closed in my network  I found two solutions but the second is better    To solve the problem using Ncat    I downloaded Tor Browser  run and wait to connect  I got Ncat from Nmap distribution and extracted ncat exe into the current directory  SSH using Ncat as ProxyCommand in Git Bash with addition --proxy-type socks4 parameter   ssh -o  ProxyCommand   ncat --proxy-type socks4 --proxy 127 0 0 1 9150  h  p  USERNAME REMOTESERVER   Note that this implementation of Ncat does not support socks5   THE BETTER SOLUTION    Do the previous step 1  SSH using connect c as ProxyCommand in Git Bash   ssh -o  ProxyCommand connect -a none -S 127 0 0 1 9150  h  p    Note that connect c supports socks version 4 4a 5     To use the proxy in git commands using ssh  for example while using GitHub  -- assuming you installed Git Bash in C  Program Files Git  -- open    ssh config and add this entry   host github com     user git     hostname github com     port 22     proxycommand   c Program Files Git mingw64 bin connect exe  -a none -S 127 0 0 1 9150  h  p

User · Answer

This is how I solved it  hoping to help others later  My system is debian 10  and minimal installation  I also have the same problem like this  git clone git github com nothing nothing git Cloning into  nothing     nc  invalid option --  x  nc -h for help ssh exchange identification  Connection closed by remote host fatal  Could not read from remote repository   Please make sure you have the correct access rights and the repository exists   Or git clone git github com nothing nothing git Cloning into  nothing      usr bin nc  invalid option --  X  nc -h for help ssh exchange identification  Connection closed by remote host fatal  Could not read from remote repository   Please make sure you have the correct access rights and the repository exists   So  I know the nc has different versions like openbsd-netcat and GNU-netcat  you can change the nc in debian to the openbsd version  but I choose to change the software like corkscrew  because the names of the two versions of nc in system are same  and many people don   t understand it well  My approach is as follows  sudo apt install corkscrew  Then  vim    ssh config  Change this file like this  Host github com     User git     ProxyCommand corkscrew 192 168 1 22 8118  h  p  192 168 1 22 and 8118 is my proxy server s address and port  you should change it according to your server address  It s work fine  Thanks  han

User · Answer

If your SSH proxy connection is going to be used often  you don t have to pass them as parameters each time  you can add the following lines to    ssh config  Host foobar example com     ProxyCommand          nc -X connect -x proxyhost proxyport  h  p     ServerAliveInterval   10   then to connect use  ssh foobar example com   Source   http   www perkin org uk posts ssh-via-http-proxy-in-osx html

User · Answer

Try  -o  quot ProxyCommand nc --proxy HOST PORT  h  p quot  for command in question  It worked on OEL6 but need to modify as mentioned for OEL7

User · Answer

I use -o  ProxyCommand nc -X 5 -x proxyhost proxyport  h  p  ssh option to connect through socks5 proxy on OSX

User · Answer

I was using the following lines in my  ssh config  which can be replaced by suitable command line parameters  under Ubuntu  Host remhost   HostName      my host com   User          myuser   ProxyCommand  nc -v -X 5 -x proxy-ip 1080  h  p 2 gt  ssh-err log   ServerAliveInterval 30   ForwardX11 yes   When using it with Msys2  after installing gnu-netcat  file ssh-err log showed that option -X does not exist  nc --help confirmed that  and seemed to show that there is no alternative option to handle proxies   So I installed openbsd-netcat  pacman removed gnu-netcat after asking  since it conflicted with openbsd-netcat   On a first view  and checking the respective man pages  openbsd-netcat and Ubuntu netcat seem to very similar  in particular regarding options -X and -x  With this  I connected with no problems

User · Answer

which nc  bin nc    rpm -qf  bin nc nmap-ncat-7 40-7 fc26 x86 64    ssh -o  ProxyCommand nc --proxy  lt addr  port  gt   h  p  USER HOST    ssh -o  ProxyCommand nc --proxy  lt addr  port  gt  --proxy-type  lt type gt  --proxy-auth  lt auth gt   h  p  USER HOST

User · Answer

In my case since I had a jump host or Bastion host on the way  and because the signatures on these bastion nodes had changed since they were imported into known hosts file  I just needed to delete those entries lines from the following file    Users a abdi-kelishami  ssh known hosts   From above file  delete those lines referring to the bastion hosts

User · Answer

ProxyCommand nc -proxy xxx com 8080  h  p   remove -X connect and use -proxy  instead   Worked for me

User · Answer

I use proxychains ssh user host  from proxychains-ng  see https   github com rofl0r proxychains-ng   By default it uses a socks4 proxy at 127 0 0 1 9050 but it can be changed in the conf file  etc proxychains conf or you can specify another conf file proxychains -f custom conf

[ssh] Connect with SSH through a proxy

Examples related to ssh

Examples related to proxy

Examples related to terminal