Unsupported SOCKS version: 67

[myexpertiseforyou]

Hello, I am using node v4.2.4 and latest dispatch proxy. But when i setup proxy i am getting this error

Thanks in advance

[natinusala]

I had the same issue, it's because you try to use a HTTP proxy using the SOCKS dispatcher. Put socks=localhost in Windows instead of just localhost :)

[Raybo58]

I tried natinusala's suggestion and it doesn't work. After many hours of experimentation, I finally figured out how to configure Dispatch for use on the system level. You can't use the Network & Internet settings page from Windows 8 through 10. Whatever you enter there will end up screwing up the configuration. You have to go to the Contol Panel and open Internet Options and go to the Connections tab. From there you want to go to the Proxy Server section and check Use a proxy server for your LAN and Bypass proxy server for local addresses. Then you want to click the Advanced button and on the page that opens you want to make sure every field is empty except the Socks: fields. There you want to enter socks for the Proxy address to use and 1080 for the Port. Also, make sure that the Use the same proxy server for all protocols box is unchecked. After using this method, every app on my system uses Disptach-Proxy.

[wblondel]

@Raybo58 this doesn't work for me. I'm using Windows 10 v1703 (15063.502)

[Raybo58]

@wblondel I think I need a little more info than that. Can you tell me what you've done and what results you're seeing? Did you install Dispatch? Have you started the process from the CLI? Are you seeing any output from the Dispatch window? I can see now that I forgot one step. After you go to the Connections tab, you need to click the LAN button, and then go to the Proxy Server section.

[wblondel]

@Raybo58 I followed this guide -> http://imgur.com/a/0snis But instead of launching Dispatch with dispatch start --http I launched it with dispatch start --debug so that it starts a SOCKS5 proxy.

In the Windows proxy settings, I tried localhost:1080 and socks:1080 in the Socks field. It doesn't work in both cases. For instance, pages doesn't load at all in Firefox (there is no error, it looks that it does not even try).

EDIT : Okay, it works if I manually enter the proxy settings in Firefox. But all the other apps either don't use the proxy and use the first connection available, or don't work at all (this is particularly true for the Windows Store apps like Maps or Groove Music)

[Raybo58]

Okay, I'll show you what I have. If you still have trouble getting it to work, I'll need to know a LOT more about the steps you've taken.

Here is my CLI command... dispatch start 192.168.0.103@4 192.168.19.2@6

I have it set up to give more weight to the second IP. This is optional.

These images will show you the rest...

[wblondel]

I don't know what more I can say. I said that I followed the guide, except that I started a SOCKS proxy instead of a HTTP proxy (I changed the settings accordingly). There are not 5000 steps.

I checked my proxy settings, I have the same.

[Raybo58]

Well, I'm stumped. So I need to know everything.

What is the nature, type, and configuration of your internet sources? How do they appear in your Network Connections list? What do you see when you check the Details of their Status properties? What do the IPv4 settings for your NICs look like? Have you ruled out firewall problems? Is localhost referenced in your HOSTS file? What, if any, output are you seeing in the Dispatch window? Have you tried manually adding the IP addresses to the Dispatch command line? Do you get internet access from both NICs when you only enable them one at a time with Dispatch turned off?

[ultrafunkamsterdam]

Stumbled upon this. Windows does not support socks5 (still not).

[Phaethon1]

same exact problem here. maybe ESET related?

[vernanng]

maybe a little bit late, replace "http://socks=socks" to "http://socks=localhost" works for me.