[GH-ISSUE #128] Failed to connect to shadowsocks #108

Open
opened 2026-02-26 12:33:59 +03:00 by kerem · 9 comments
Owner

Originally created by @ghost on GitHub (Sep 7, 2020).
Original GitHub issue: https://github.com/cbeuw/Cloak/issues/128

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

Originally created by @ghost on GitHub (Sep 7, 2020). Original GitHub issue: https://github.com/cbeuw/Cloak/issues/128 This is error I get on my VPS that is running shadowsocks-libev and ck-server ![image](https://user-images.githubusercontent.com/12738743/92376228-8f9ed080-f102-11ea-9e3a-c8d69cd1d6bf.png) This is screenshot of ckserver.json - on my VPS ![image](https://user-images.githubusercontent.com/12738743/92377321-40f23600-f104-11ea-989f-08502bedf648.png) And this is my /etc/shadowsocks-libev/confi.json - also on my VPS ![image](https://user-images.githubusercontent.com/12738743/92377152-fc669a80-f103-11ea-9bdb-f4598f613499.png) ------------------------------------------------------------------ ck-client.json - on my Windows machine ![image](https://user-images.githubusercontent.com/12738743/92376671-397e5d00-f103-11ea-9c01-bccf254cfcc2.png)
Author
Owner

@ghost commented on GitHub (Sep 7, 2020):

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

<!-- gh-comment-id:688225100 --> @ghost commented on GitHub (Sep 7, 2020): Should I apply in Firefox 127.0.0.1:1080 or 127.0.0.1:1984 ?
Author
Owner

@cbeuw commented on GitHub (Sep 7, 2020):

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

<!-- gh-comment-id:688227290 --> @cbeuw commented on GitHub (Sep 7, 2020): 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~~
Author
Owner

@malikshi commented on GitHub (Sep 7, 2020):

Try set 0.0.0.0 on shadowsocks config or 127.0.0.1 restart all services

<!-- gh-comment-id:688227378 --> @malikshi commented on GitHub (Sep 7, 2020): Try set 0.0.0.0 on shadowsocks config or 127.0.0.1 restart all services
Author
Owner

@ghost commented on GitHub (Sep 7, 2020):

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

<!-- gh-comment-id:688230949 --> @ghost commented on GitHub (Sep 7, 2020): > 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](https://user-images.githubusercontent.com/12738743/92377952-3dab7a00-f105-11ea-8cd7-5ce0707aa063.png)
Author
Owner

@cbeuw commented on GitHub (Sep 7, 2020):

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

<!-- gh-comment-id:688232342 --> @cbeuw commented on GitHub (Sep 7, 2020): 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
Author
Owner

@malikshi commented on GitHub (Sep 7, 2020):

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.

<!-- gh-comment-id:688234778 --> @malikshi commented on GitHub (Sep 7, 2020): 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.
Author
Owner

@ghost commented on GitHub (Sep 7, 2020):

I think everything works now...
image
image
image

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

<!-- gh-comment-id:688237904 --> @ghost commented on GitHub (Sep 7, 2020): I think everything works now... ![image](https://user-images.githubusercontent.com/12738743/92378947-e6a6a480-f106-11ea-83c6-d90ad8926efc.png) ![image](https://user-images.githubusercontent.com/12738743/92378993-f8884780-f106-11ea-8306-2ee79f062589.png) ![image](https://user-images.githubusercontent.com/12738743/92379008-0047ec00-f107-11ea-8a2d-aa4fa702276e.png) And this is /etc/shadowsocks-libev/config.json ![image](https://user-images.githubusercontent.com/12738743/92379077-1d7cba80-f107-11ea-99a3-1c266201f21d.png)
Author
Owner

@ghost commented on GitHub (Sep 7, 2020):

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

<!-- gh-comment-id:688238381 --> @ghost commented on GitHub (Sep 7, 2020): I have also set up System proxy, so I don't need to change proxy settings in Firefox..
Author
Owner

@ghost commented on GitHub (Sep 10, 2020):

@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

<!-- gh-comment-id:690151617 --> @ghost commented on GitHub (Sep 10, 2020): @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](https://user-images.githubusercontent.com/12738743/92719922-2a4a1a00-f364-11ea-8a15-446d3fde4e46.png)
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Cloak#108
No description provided.