Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't connect while using the proxy server #15

Open
marybirds opened this issue Mar 26, 2023 · 10 comments
Open

can't connect while using the proxy server #15

marybirds opened this issue Mar 26, 2023 · 10 comments

Comments

@marybirds
Copy link

i tried to configure in internet options the proxy as socks proxy and leave others empty but it didn't resolve it

Error

Error: 
   0: An error occurred during the proxy handshake procedure
   1: invalid SOCKS version 01, expected 04

Metadata

key value
Version 0.1.0
OS Windows 10 Home
Command dispatch --debug start 192.168.42.242

SpanTrace

SpanTrace:
   0: dispatch::socks::handle_request_v4
           with self=SocksHandshake { reader: ReadHalf(PollEvented { io: Some(TcpStream { addr: 127.0.0.1:1080, peer: 127.0.0.1:63083, socket: 1268 }) }), writer: WriteHalf(PollEvented { io: Some(TcpStream { addr: 127.0.0.1:1080, peer: 127.0.0.1:63083, socket: 1268 }) }), dispatcher: WeightedRoundRobinDispatcher(Mutex { data: WeightedRoundRobinDispatcherInner { ipv4: State { addresses: [WeightedAddress { ip: 192.168.42.242, weight: 1 }], address_idx: 0, count: 0 }, ipv6: State { addresses: [], address_idx: 0, count: 0 } } }) }
             at C:\Users\Madjid\.cargo\registry\src\github.com-1ecc6299db9ec823\dispatch-proxy-0.1.0\src\socks.rs:259
   1: dispatch::socks::handle_handshake_with_version
           with self=SocksHandshake { reader: ReadHalf(PollEvented { io: Some(TcpStream { addr: 127.0.0.1:1080, peer: 127.0.0.1:63083, socket: 1268 }) }), writer: WriteHalf(PollEvented { io: Some(TcpStream { addr: 127.0.0.1:1080, peer: 127.0.0.1:63083, socket: 1268 }) }), dispatcher: WeightedRoundRobinDispatcher(Mutex { data: WeightedRoundRobinDispatcherInner { ipv4: State { addresses: [WeightedAddress { ip: 192.168.42.242, weight: 1 }], address_idx: 0, count: 0 }, ipv6: State { addresses: [], address_idx: 0, count: 0 } } }) } version=V4
             at C:\Users\Madjid\.cargo\registry\src\github.com-1ecc6299db9ec823\dispatch-proxy-0.1.0\src\socks.rs:121
   2: dispatch::server::handle_socket
           with socket=PollEvented { io: Some(TcpStream { addr: 127.0.0.1:1080, peer: 127.0.0.1:63083, socket: 1268 }) } dispatcher=WeightedRoundRobinDispatcher(Mutex { data: WeightedRoundRobinDispatcherInner { ipv4: State { addresses: [WeightedAddress { ip: 192.168.42.242, weight: 1 }], address_idx: 0, count: 0 }, ipv6: State { addresses: [], address_idx: 0, count: 0 } } })
             at C:\Users\Madjid\.cargo\registry\src\github.com-1ecc6299db9ec823\dispatch-proxy-0.1.0\src\server.rs:19

Backtrace

Backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: BaseThreadInitThunk
  22: RtlUserThreadStart

@alexkirsz
Copy link
Owner

Can you share a screenshot of your proxy settings?

@marybirds
Copy link
Author

image
i had to use Proxifier to get application to use the proxy as socks5 proxy
that solves the problem but i don't know why windows despite putting the address in internet options in socks field and leaving others empty defaulted to using socks1
weird stuff

@alexkirsz
Copy link
Owner

What about your windows proxy settings screen?

@marybirds
Copy link
Author

image

@marybirds
Copy link
Author

image

@alexkirsz
Copy link
Owner

The latter one should probably read 127.0.0.1 instead of http://socks=127.0.0.1. Otherwise, the rest of the settings look correct.

@marybirds
Copy link
Author

I did that first didn't work at all I saw the logs it was using the server as an HTTP server
doing it through internet properties window solves it

@VictorGarciaOrtega
Copy link

I had the same problem, but when I set it correctly it end up giving me the following error: invalid SOCKS version 01, expected 04

@Nucito
Copy link

Nucito commented Jun 3, 2023

Same error here

@csmuthukuda
Copy link

same error..any solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants