starred/Cloak

Fork 0

mirror of https://github.com/cbeuw/Cloak.git synced 2026-04-25 20:45:59 +03:00

[GH-ISSUE #245] Still getting detected on a Shadowsocks + Cloak setup #198

New issue

Closed

opened 2026-02-26 12:34:14 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 12:34:14 +03:00

Owner

Originally created by @v1rtl on GitHub (Jan 23, 2024).
Original GitHub issue: https://github.com/cbeuw/Cloak/issues/245

Twitter and others are still detecting that I'm using a proxy. here's a detection score I have (it was the same without the plugin):

This is my server configs:

ss-server.json:

{
    "server": "my_ip",
    "mode":"tcp_and_udp",
    "server_port": 1337,
    "local_port": 1337,
    "password":"my_password",
    "timeout":60,
    "method":"chacha20-ietf-poly1305",
    "plugin": "/usr/bin/ck-server",
    "plugin_opts": "/home/v1rtl/ck/ck-config.json"
}

and ck-server.json:

{
        "PrivateKey": "private_key",
        "AdminUID": "admin_uid",
        "DatabasePath": "userinfo.db",
        "RedirAddr": "cloudflare.com",
        "BindAddr": [
                ":1234"
        ],
        "BypassUID": [
                "some_uid"
        ],
        "ProxyBook": {
                "shadowsocks": [
                        "tcp",
                        "127.0.0.1:1337"
                ]
        }
}

And my client setup is the following:

{
  "Transport": "direct",
  "ProxyMethod": "shadowsocks",
  "EncryptionMethod": "plain",
  "UID": "my_uid",
  "PublicKey": "pub_key",
  "ServerName": "www.bing.com",
  "NumConn": 4,
  "BrowserSig": "chrome",
  "StreamTimeout": 300
}

{
    "server": "ip",
    "mode":"tcp_and_udp",
    "server_port": 1337,
    "local_port": 1080,
    "password":"password",
    "timeout":60,
    "method":"chacha20-ietf-poly1305",
    "plugin": "/usr/bin/ck-client",
    "plugin_opts": "/home/v1rtl/ck-client.json"
}

Here are the logs for sslocal:

❯ sslocal -c ss-config.json
2024-01-23T19:29:57.189129210+02:00 INFO  shadowsocks local 1.17.1 build 2023-11-26T16:00:22.060213964+00:00
INFO[2024-01-23T19:29:57+02:00] Listening on TCP 127.0.0.1:43043 for shadowsocks client 
INFO[2024-01-23T19:29:57+02:00] Attempting to start a new session            
2024-01-23T19:29:57.193193823+02:00 INFO  shadowsocks socks TCP listening on 127.0.0.1:1080
2024-01-23T19:29:57.193246064+02:00 INFO  shadowsocks socks5 UDP listening on 127.0.0.1:1080
INFO[2024-01-23T19:29:57+02:00] Session 2746856081 established               
ERRO[2024-01-23T19:29:57+02:00] Failed to read first packet from proxy client: EOF

(despite the error it still works)

server log:

Jan 23 17:37:30 v1rtl ssserver[2715366]: 2024-01-23T17:37:30.545189907+00:00 INFO  shadowsocks server 1.15.4 build 2023-07-06T16:36:53.621088465+00:00
Jan 23 17:37:30 v1rtl ssserver[2715366]: 2024-01-23T17:37:30.554464257+00:00 INFO  shadowsocks tcp server listening on 127.0.0.1:33175, inbound address ...:1337
Jan 23 17:37:30 v1rtl ssserver[2715366]: 2024-01-23T17:37:30.554958214+00:00 INFO  shadowsocks udp server listening on ...:1337
Jan 23 17:37:30 v1rtl ssserver[2715369]: time="2024-01-23T17:37:30Z" level=info msg="Listening on ...1337"
Jan 23 17:37:30 v1rtl ssserver[2715369]: time="2024-01-23T17:37:30Z" level=info msg="Listening on :1234"
Jan 23 17:37:31 v1rtl ssserver[2715369]: time="2024-01-23T17:37:31Z" level=info msg="New session" UID="..." sessionID=3851467237
Jan 23 17:38:03 v1rtl ssserver[2715366]: 2024-01-23T17:38:03.413571746+00:00 ERROR tcp tunnel 127.0.0.1:43376 -> ....com:443 connect failed, error: dns resolve ...>

Originally created by @v1rtl on GitHub (Jan 23, 2024). Original GitHub issue: https://github.com/cbeuw/Cloak/issues/245 Twitter and others are still detecting that I'm using a proxy. here's a detection score I have (it was the same without the plugin): ![image](https://github.com/cbeuw/Cloak/assets/35937217/af5c841a-c649-4821-8469-cb3535d644d7) This is my server configs: `ss-server.json`: ```json { "server": "my_ip", "mode":"tcp_and_udp", "server_port": 1337, "local_port": 1337, "password":"my_password", "timeout":60, "method":"chacha20-ietf-poly1305", "plugin": "/usr/bin/ck-server", "plugin_opts": "/home/v1rtl/ck/ck-config.json" } ``` and `ck-server.json`: ```json { "PrivateKey": "private_key", "AdminUID": "admin_uid", "DatabasePath": "userinfo.db", "RedirAddr": "cloudflare.com", "BindAddr": [ ":1234" ], "BypassUID": [ "some_uid" ], "ProxyBook": { "shadowsocks": [ "tcp", "127.0.0.1:1337" ] } } ``` And my client setup is the following: ```json { "Transport": "direct", "ProxyMethod": "shadowsocks", "EncryptionMethod": "plain", "UID": "my_uid", "PublicKey": "pub_key", "ServerName": "www.bing.com", "NumConn": 4, "BrowserSig": "chrome", "StreamTimeout": 300 } ``` ```json { "server": "ip", "mode":"tcp_and_udp", "server_port": 1337, "local_port": 1080, "password":"password", "timeout":60, "method":"chacha20-ietf-poly1305", "plugin": "/usr/bin/ck-client", "plugin_opts": "/home/v1rtl/ck-client.json" } ``` Here are the logs for `sslocal`: ``` ❯ sslocal -c ss-config.json 2024-01-23T19:29:57.189129210+02:00 INFO shadowsocks local 1.17.1 build 2023-11-26T16:00:22.060213964+00:00 INFO[2024-01-23T19:29:57+02:00] Listening on TCP 127.0.0.1:43043 for shadowsocks client INFO[2024-01-23T19:29:57+02:00] Attempting to start a new session 2024-01-23T19:29:57.193193823+02:00 INFO shadowsocks socks TCP listening on 127.0.0.1:1080 2024-01-23T19:29:57.193246064+02:00 INFO shadowsocks socks5 UDP listening on 127.0.0.1:1080 INFO[2024-01-23T19:29:57+02:00] Session 2746856081 established ERRO[2024-01-23T19:29:57+02:00] Failed to read first packet from proxy client: EOF ``` (despite the error it still works) server log: ``` Jan 23 17:37:30 v1rtl ssserver[2715366]: 2024-01-23T17:37:30.545189907+00:00 INFO shadowsocks server 1.15.4 build 2023-07-06T16:36:53.621088465+00:00 Jan 23 17:37:30 v1rtl ssserver[2715366]: 2024-01-23T17:37:30.554464257+00:00 INFO shadowsocks tcp server listening on 127.0.0.1:33175, inbound address ...:1337 Jan 23 17:37:30 v1rtl ssserver[2715366]: 2024-01-23T17:37:30.554958214+00:00 INFO shadowsocks udp server listening on ...:1337 Jan 23 17:37:30 v1rtl ssserver[2715369]: time="2024-01-23T17:37:30Z" level=info msg="Listening on ...1337" Jan 23 17:37:30 v1rtl ssserver[2715369]: time="2024-01-23T17:37:30Z" level=info msg="Listening on :1234" Jan 23 17:37:31 v1rtl ssserver[2715369]: time="2024-01-23T17:37:31Z" level=info msg="New session" UID="..." sessionID=3851467237 Jan 23 17:38:03 v1rtl ssserver[2715366]: 2024-01-23T17:38:03.413571746+00:00 ERROR tcp tunnel 127.0.0.1:43376 -> ....com:443 connect failed, error: dns resolve ...> ```

kerem closed this issue

2026-02-26 12:34:14 +03:00

kerem commented

2026-02-26 12:34:15 +03:00

Author

Owner

@qwerttvv commented on GitHub (Feb 1, 2024):

it just depending on your ip and the location of the server, change to different vps provider is your good way

by the way, you should use 443 port, and RedirAddr ServerName must be sameone

@qwerttvv commented on GitHub (Feb 1, 2024): it just depending on your ip and the location of the server, change to different vps provider is your good way by the way, you should use 443 port, and RedirAddr ServerName must be sameone

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#198

No description provided.

Rows
Columns