I have a socks 5 proxy set up using ssh on a vps. Recently clients have been unable to connect using any chromium based browser (specifically chrome, opera and vivaldi). I'm assuming its because of a recent update but am not sure. The latest versions which I downloaded to test all don't work. The instructions that used to work are here: https://www.chromium.org/developers/design-documents/network-stack/socks-proxy For some reason, it only affects some websites but not others. google works, as does whatismyip.com. Yahoo and ebay were two examples that don't work. As far as I can tell, it seems that the connections start, it receives some data (on the order of hundreds of bytes), then just stops receiving data.

Even more strangely, the proxy works perfectly fine on Firefox and MS Edge.

I'm pretty lost at this point. My next step is to try older versions of chromium, but am hoping someone else might have an idea.

  • Is it perhaps choking on QUIC (UDP/443), HTTP/2 or Speedy, or perhaps even Websockets? – Cameron Kerr May 23 '17 at 9:16
  • Any ideas on how to test that? It should work fine for any tcp or udp connection... – Kayson May 23 '17 at 15:52
  • Did you figure this out? I'm also having trouble with a socks 5 proxy in Chrome. It works in Firefox, and it used to work in Chrome, but it just suddenly doesn't anymore. – Lars Nyström Sep 4 '18 at 8:15
  • Yes. My provider had a DNS outage, and Chrome defaults to DNS over SOCKS5 instead of locally. Firefox, on the other hand, defaults to local DNS when using SOCKS. See: bugs.chromium.org/p/chromium/issues/detail?id=725362#c8 Hope that helps! – Kayson Sep 4 '18 at 23:28

Maybe try an extension for proxy in Chrome. I use FoxyProxy Standard in Chrome with ssh tunneled socks5 proxy.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.