cbeuw / Cloak

A censorship circumvention tool to evade detection by authoritarian state adversaries
GNU General Public License v3.0
3.32k stars 297 forks source link

Failed to connect to shadowsocks #128

Open ghost opened 4 years ago

ghost commented 4 years ago

This is error I get on my VPS that is running shadowsocks-libev and ck-server image

This is screenshot of ckserver.json - on my VPS image

And this is my /etc/shadowsocks-libev/confi.json - also on my VPS image


ck-client.json - on my Windows machine image

ghost commented 4 years ago

Should I apply in Firefox 127.0.0.1:1080 or 127.0.0.1:1984 ?

cbeuw commented 4 years ago

In /etc/shadowsocks-libev/confi.json, try to set server as 127.0.0.1.

In firefox the proxy address should be 127.0.0.1:1984 unless you specified the port with -l flag when starting up ck-client

malikshi commented 4 years ago

Try set 0.0.0.0 on shadowsocks config or 127.0.0.1 restart all services

ghost commented 4 years ago

In /etc/shadowsocks-libev/confi.json, try to set server as 127.0.0.1.

In firefox the proxy address should be 127.0.0.1:1984 unless you specified the port with -l flag when starting up ck-client

I am not getting anything now. No internet connection. What about shadowsocks client on Windows? Do I need it set up liket this? image

cbeuw commented 4 years ago

Sorry I got the port part wrong.

Here in shadowsocks client, your Server IP and port needs to point to ck-client. That should be 127.0.0.1:1984. In your browser the SOCKS5 proxy should point to 127.0.0.1:Proxy Port, which is 127.0.0.1:1080

malikshi commented 4 years ago

Hello the windows client setting are completely wrong. First you can browse or try see video how it work on windows. or you can try Netch app find it on github it's more easy-to-use.

ghost commented 4 years ago

I think everything works now... image image image

And this is /etc/shadowsocks-libev/config.json image

ghost commented 4 years ago

I have also set up System proxy, so I don't need to change proxy settings in Firefox..

ghost commented 4 years ago

@malikshi @cbeuw Guys, would be great If you are willing to help me with this error: transport TLS in correct format but not Cloak: cipher: message authentication failed image