v2ray-plugin icon indicating copy to clipboard operation
v2ray-plugin copied to clipboard

Can't make this work, need help

Open birdie-github opened this issue 8 months ago • 1 comments

Software used:

  • Shadowsocks-rust: 1.23.4
  • v2ray-plugin 1.3.2

Here's my server part:

{
    "servers": [
        {
            "server": "0.0.0.0",
            "server_port": 443,
            "password": "strongpassword",
            "timeout": 300,
            "method": "aes-256-gcm",
            "fast_open": true,
            "reuse_port": true,
            "mode": "tcp_and_udp",
            "udp_max_associations": 512,
            "plugin": "/opt/shadowsocks-rust/v2ray-plugin_linux_amd64",
            "plugin_opts": "server;tls;host=server.com;cert=/opt/shadowsocks-rust/server.crt;key=/opt/shadowsocks-rust/server.key",
        }
    ]
}

I can open server.com with my web browser and I get "Bad Request", i.e. looks like the certificate and key files work just fine. I generated them using acme-tiny.

Here's my client part:

{
    "server": "1.2.3.4",
    "server_port": 443,
    "password": "strongpassword",
    "timeout": 300,
    "method": "aes-256-gcm",
    "fast_open": true,
    "reuse_port": true,
    "mode": "tcp_and_udp",
    "udp_max_associations": 512,
    "local_address": "0.0.0.0",
    "local_port": 1080,
    "plugin": "/opt/shadowsocks-rust/v2ray-plugin_linux_amd64",
    "plugin_opts": "tls;host=server.com;loglevel=info;insecure"
}

Without the v2ray-plugin everything works. With it:

Jun 13 09:42:24 localhost systemd[1]: Started sslocal.service - shadowsocks-rust sslocal socks5 proxy.
Jun 13 09:42:24 localhost sslocal[2165526]: 2025-06-13T14:42:24.659810213+05:00  INFO shadowsocks local 1.23.4 build 2025-05-12T15:54:13.448182254+00:00
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 V2Ray 4.38.3 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.16.15 linux/amd64)
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 A unified platform for anti-censorship.
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Debug] app/log: Logger started
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Debug] app/proxyman/inbound: creating stream worker on 127.0.0.1:34819
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Info] transport/internet/tcp: listening TCP on 127.0.0.1:34819
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Warning] V2Ray 4.38.3 started
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Debug] [1868742730] proxy/dokodemo: processing connection from: 127.0.0.1:47498
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Info] [1868742730] proxy/dokodemo: received request for 127.0.0.1:47498
Jun 13 09:42:24 localhost sslocal[2165526]: 2025-06-13T14:42:24.662850066+05:00  INFO shadowsocks socks TCP listening on 0.0.0.0:1080
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Info] [1868742730] app/dispatcher: default route for tcp:127.0.0.1:0
Jun 13 09:42:24 localhost sslocal[2165526]: 2025-06-13T14:42:24.662858361+05:00  INFO shadowsocks socks5 UDP listening on 0.0.0.0:1080
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Info] [1868742730] common/mux: dispatching request to tcp:127.0.0.1:0
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Info] [1868742730] common/mux: failed to write first payload > EOF
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 127.0.0.1:47498 accepted tcp:127.0.0.1:0
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Info] proxy/freedom: opening connection to tcp:1.2.3.4:443
Jun 13 09:42:24 localhost sslocal[2165545]: 2025/06/13 14:42:24 [Info] transport/internet/websocket: creating connection to tcp:1.2.3.4:443
Jun 13 09:42:40 localhost sslocal[2165545]: 2025/06/13 14:42:40 [Info] common/mux: failed to read metadata > io: read/write on closed pipe
Jun 13 09:42:40 localhost sslocal[2165545]: 2025/06/13 14:42:40 [Info] transport/internet/websocket: creating connection to tcp:1.2.3.4:443
Jun 13 09:44:40 localhost sslocal[2165526]: 2025-06-13T14:44:40.224217638+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:40 localhost sslocal[2165526]: 2025-06-13T14:44:40.224259515+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:40 localhost sslocal[2165526]: 2025-06-13T14:44:40.2243004+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:40 localhost sslocal[2165526]: 2025-06-13T14:44:40.224326328+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:44 localhost sslocal[2165526]: 2025-06-13T14:44:44.319988149+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:44 localhost sslocal[2165526]: 2025-06-13T14:44:44.320052267+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:44 localhost sslocal[2165526]: 2025-06-13T14:44:44.320082051+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:44 localhost sslocal[2165526]: 2025-06-13T14:44:44.320137814+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:48 localhost sslocal[2165526]: 2025-06-13T14:44:48.415616129+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:48 localhost sslocal[2165526]: 2025-06-13T14:44:48.415656864+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:48 localhost sslocal[2165526]: 2025-06-13T14:44:48.415656704+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
Jun 13 09:44:48 localhost sslocal[2165526]: 2025-06-13T14:44:48.415668325+05:00 ERROR socks5 tcp client handler error: Broken pipe (os error 32)
...

What am I doing wrong?

( This is a copy of https://github.com/shadowsocks/shadowsocks-rust/issues/1970 )

birdie-github avatar Jun 13 '25 09:06 birdie-github