-
-
Notifications
You must be signed in to change notification settings - Fork 410
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
shadowsocks: cannot obtain target address: unexpected EOF #233
Comments
Can you please send your Shadowsocks client configuration (or screenshot)? What's your SS client also? I just tested shadowsocks (for windows) yesterday and it worked for me, but it might be a bug on my side happening for your particular client. Thanks! |
It should be a socks5 proxy indeed. Did you set the encryption method and password somewhere? I'll try with your chrome extension to see as well. |
According to your proposal I changed the configuration. Unfortunately, it did not work. I still have the same error. |
I tried also using "private internet access" vpn account. Same error. This leads me to thinking that it is not vpn provider specific. |
No, I did not set encryption method or password. |
Ok so actually (sorry I should had known that!), Shadowsocks uses the open source SOCKS5 proxy protocol to communicate, but it adds some encryption on top. So you won't be able to use it as a SOCKS5 proxy server only, you will need some Shadowsocks client. However, considering we mostly use it in our LAN I'll work on adding a SOCKS5 non-encrypted proxy server too, please subscribe to issue #234 for that. For now, you can alternatively use Tinyproxy as an HTTP proxy. |
Oh, I did not know that. Thank you. I will subscribe to issue you mentioned. For now I will use HTTP Proxy. |
Hi, I am using docker-compose version and been trying to use socks service. Unfortunately everytime I try to use socks5 connection I get in logs this error
shadowsocks: cannot obtain target address: unexpected EOF
.In browser proxy configuration I enter ip adress of docker host (from pool 192.168.1.0/24) and shadowsocks port.
Here's my docker-compose.yml
Here's output log
The text was updated successfully, but these errors were encountered: