This is because chrome assumes the SOCKS proxy is a SOCKS4 proxy when it is SOCKS5.
A workaround is to have chrome read the proxy configuration from a script.
Here is an example:
* .pac files are for automated proxy configuration
* This is a fix for chrome to use SOCKS5 as it assumes SOCKS4
function FindProxyForURL(url, host)
// no proxy for localhost
if (host.match('localhost') return false;
// proxy for other hosts
return "SOCKS5 localhost:8111";
Make sure your port number is the port that the socks proxy is bound to.
Save this script as ssh-tunnel.pac or similar and in chrome go to:
Options -> Under the Hood -> Network -> Change Proxy Settings
Chrome uses the same network settings as IE. So you will see the system window open and choose:
LAN settings -> Use Automatic Configuration Script
Enter the path to the ssh-tunnel.pac file you created.
Now reload the webpage in Chrome.
Creating an SSH tunnel.
If you’re not familiar with creating an SSH Socks5 proxy visit:
Windows SSH as Proxy
Linux SSH as Proxy