Linux – How to tunnel HTTP over SSH via SOCKS

linuxPROXYsocks-proxyssh

This should be a simple issue to solve, but for some reason it's not working for me.

ssh vps works just fine (I use authentication keys)

I set up the tunnel with the command:

ssh -C2TNv -D 8080 vps

I then modify Firefox network settings:

  • manual config
    • http proxy: localhost, port: 8080
    • use this proxy server for all protocols
    • SOCKS v5
  • about:config
    • network.proxy.socks_remote_dns: true

Terminal output:

$ ssh -C2TNv -D 8080 vps
OpenSSH_6.0p1, OpenSSL 1.0.1a 19 Apr 2012
debug1: Reading configuration data /home/ting/.ssh/config
debug1: /home/ting/.ssh/config line 47: Applying options for vps
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to vps.server.com [1.1.1.1] port 22.
debug1: Connection established.
debug1: identity file /home/ting/.ssh/id_rsa type 1
debug1: identity file /home/ting/.ssh/id_rsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.5p1 Debian-6+squeeze1
debug1: match: OpenSSH_5.5p1 Debian-6+squeeze1 pat OpenSSH_5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.0
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 zlib@openssh.com
debug1: kex: client->server aes128-ctr hmac-md5 zlib@openssh.com
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 <removed>
debug1: Host 'vps.server.com' is known and matches the RSA host key.
debug1: Found key in /home/ting/.ssh/known_hosts:10
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_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/ting/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: Enabling compression at level 6.
debug1: Authentication succeeded (publickey).
Authenticated to vps.server.com ([1.1.1.1]:22).
debug1: Local connections to LOCALHOST:8080 forwarded to remote address socks:0
debug1: Local forwarding listening on ::1 port 8080.
debug1: channel 0: new [port listener]
debug1: Local forwarding listening on 127.0.0.1 port 8080.
debug1: channel 1: new [port listener]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.

I then try visiting a site using Firefox, SSH output:

debug1: Connection to port 8080 forwarding to socks port 0 requested.
debug1: channel 2: new [dynamic-tcpip]
debug1: channel 2: free: dynamic-tcpip, nchannels 3
debug1: Connection to port 8080 forwarding to socks port 0 requested.
debug1: channel 2: new [dynamic-tcpip]
debug1: channel 2: free: dynamic-tcpip, nchannels 3

Despite the proxy seemingly working, visiting any site with Firefox just returns with the error "The connection was reset".

Best Answer

Your SSH command with -D is fine (so the SOCKS will tunnel it's just the connecting to the SOCKS via HTTP, that you have to sort out)

I get good output with

curl --socks5 127.0.0.1:8080 http://blah

but I get the same wrong output you get if I do

 curl --proxy 127.0.0.1:8080 http://blah

So, firefox is connecting as if it's an HTTP Proxy

Looking at the firefox window

manual config YES

you said you ticked "use this proxy server for all protocols" That is a totally wrong move! You want to enter a SOCKS proxy, and if you do that then the SOCKS box get nulled/greyed out and you can only enter an HTTP Proxy.

So don't tick that.

And do, enter the socks proxy ip.

and remove where it says no proxy for 127.0.0.1,localhost . if it says that, which is default.