Shadowsocks multiple clients and/or ports

[mmazila]

Hello!
The situation is as follows. I am configuring a Shadowsocks connection to a single port. As a result, the service works fine, and clients establish a connection with the server. Here's the config.json:

config.json

{
  "log": {
    "loglevel": "info"
  },
  "inbounds": [
    {
      "listen": "172.11.11.11",
      "port": 12345,
      "tag": "ss-in",
      "protocol": "shadowsocks",
      "settings": {
        "method": "2022-blake3-aes-128-gcm",
        "password": "some_password",
        "network": "tcp,udp"
      },
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls",
          "quic"
        ]
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "freedom",
      "tag": "direct"
    },
    {
      "protocol": "blackhole",
      "tag": "block"
    }
  ],
  "routing": {
    "rules": [
      {
        "type": "field",
        "protocol": "bittorrent",
        "outboundTag": "block"
      }
    ],
    "domainStrategy": "IPIfNonMatch"
  }
}

However, when I add multiple ports and/or multiple clients, the xray service does not start, giving the following error:

Aug 21 09:45:37 ip-172-11-11-11 xray[1234]: Failed to start: main: failed to create server > proxy/shadowsocks_2022: missing key

Here's the config.json:

config.json

{
  "log": {
    "loglevel": "info"
  },
  "inbounds": [
    {
      "listen": "172.11.11.11",
      "port": "12345-12346",
      "tag": "ss-in",
      "protocol": "shadowsocks",
      "settings": {
        "clients": [
          {
            "password": "client1_password",
            "email": "client1"
          },
          {
            "password": "client2_password",
            "email": "client2"
          }
        ],
        "method": "2022-blake3-aes-128-gcm",
        "network": "tcp,udp"
      },
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls",
          "quic"
        ]
      },
      "allocate": {
        "strategy": "always",
        "refresh": 5,
        "concurrency": 1
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "freedom",
      "tag": "direct"
    },
    {
      "protocol": "blackhole",
      "tag": "block"
    }
  ],
  "routing": {
    "rules": [
      {
        "type": "field",
        "protocol": "bittorrent",
        "outboundTag": "block"
      }
    ],
    "domainStrategy": "IPIfNonMatch"
  }
}

If I leave one port and several clients, the xray service does not start with the following error:

Aug 21 10:13:14 ip-172-11-11-11 xray[1234]: Failed to start: main: failed to load config files: [/opt/xray/config.json] > infra/conf: failed to build inbound config with tag ss-in > infra/conf: failed to build inbound handler for protocol shadowsocks > infra/conf: unsupported cipher method: 2022-blake3-aes-128-gcm

config.json

{
  "log": {
    "loglevel": "info"
  },
  "inbounds": [
    {
      "listen": "172.11.11.11",
      "port": "12345-12346",
      "tag": "ss-in",
      "protocol": "shadowsocks",
      "settings": {
        "clients": [
          {
            "password": "client1_password",
            "method": "2022-blake3-aes-128-gcm",
            "email": "client1"
          },
          {
            "password": "client2_password",
            "method": "2022-blake3-aes-128-gcm",
            "email": "client2"
          }
        ],
        "network": "tcp,udp"
      },
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls",
          "quic"
        ]
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "freedom",
      "tag": "direct"
    },
    {
      "protocol": "blackhole",
      "tag": "block"
    }
  ],
  "routing": {
    "rules": [
      {
        "type": "field",
        "protocol": "bittorrent",
        "outboundTag": "block"
      }
    ],
    "domainStrategy": "IPIfNonMatch"
  }
}

I would appreciate your help in figuring out which key (or keys) is being referred to and where I can find details about this in the documentation.

[RPRX]

建议换用 VLESS 加密 #4952 (comment)

[mmazila]

Yes, VLESS has been selected as the primary encryption method, and I have not encountered any issues with the VLESS settings thus far - everything is functioning properly. However, I would like to retain Shadowsocks as a backup option, and there are some nuances associated with it.

[RPRX]

VLESS 加密可以选全随机数外观、像以前用 SS 那样直接用，这两天就会发版