Why "mux" does not work with Xray+REALITY+TCP?

[Blabter]

I have following client config outbounds:

{
      "protocol": "vless",
      "tag": "tcp_balancer_v4@balancer_outbound:",
      "settings": {
        "vnext": [
          {
            "address": "*IP HERE*",
            "port": 443,
            "users": [
              {
                "email": null,
                "id": "*USER ID HERE*",
                "flow": "xtls-rprx-vision",
                "encryption": "none"
              }
            ]
          }
        ]
      },
      "streamSettings": {
        "network": "tcp",
        "sockopt": {
          "domainStrategy": "UseIP",
          "dialerProxy": null,
          "mark": 253
        },
        "security": "reality",
        "tlsSettings": null,
        "realitySettings": {
          "show": false,
          "fingerprint": "random",
          "serverName": "*MY SNI HERE*",
          "publicKey": "MY PUBLIC KEY HERE",
          "shortId": null,
          "spiderX": null
        },
        "quicSettings": null,
        "tcpSettings": {
          "header": {
            "type": "none",
            "request": null,
            "response": null
          }
        },
        "kcpSettings": null,
        "wsSettings": null,
        "grpcSettings": null,
        "httpSettings": null,
        "splithttpSettings": null,
        "httpupgradeSettings": null
      },
      "mux": {
        "enabled": true,
        "concurrency": 4
      }
    },
    {
      "protocol": "vless",
      "tag": "udp_balancer_v4@balancer_outbound:",
      "settings": {
        "vnext": [
          {
            "address": "MY IP HERE",
            "port": 443,
            "users": [
              {
                "email": null,
                "id": "MY USER ID HERE",
                "flow": "xtls-rprx-vision",
                "encryption": "none"
              }
            ]
          }
        ]
      },
      "streamSettings": {
        "network": "tcp",
        "sockopt": {
          "domainStrategy": "UseIP",
          "dialerProxy": null,
          "mark": 253
        },
        "security": "reality",
        "tlsSettings": null,
        "realitySettings": {
          "show": false,
          "fingerprint": "random",
          "serverName": "MY SNI HERE",
          "publicKey": "MY PUBLIC KEY HERE",
          "shortId": null,
          "spiderX": null
        },
        "quicSettings": null,
        "tcpSettings": {
          "header": {
            "type": "none",
            "request": null,
            "response": null
          }
        },
        "kcpSettings": null,
        "wsSettings": null,
        "grpcSettings": null,
        "httpSettings": null,
        "splithttpSettings": null,
        "httpupgradeSettings": null
      },
      "mux": {
        "enabled": true,
        "concurrency": 4
      }
    }

When I connect to the server and try to make any requests I get error curl: (52) Empty reply from server.

In server logs I see following errors:

common/mux: unexpected EOF > common/mux: failed to process data > common/mux: unexpected network TCP
app/proxyman/inbound: connection ends > proxy/vless/inbound: connection ends > proxy/vless/inbound: failed to transfer request payload > io: read/write on closed pipe

Note that if I remove "mux" object everything works fine.

Why I can't use MUX? Does it work with "tcp" transport?

[CyrusTheG]

its becuase of vision,does not work with mux

[Blabter]

Thanks for reply.

1. There is any way to simultaneously use MUX and avoid TLS-in-TLS?
2. Would just removing "flow": "xtls-rprx-vision", lead to any bad consequences besides TLS-in-TLS?

[CyrusTheG]

1-when u use mux,it will send multiple requests in one tcp connection,which usually obfuscates a lot of those tls in tls characteristics,but vision takes a diffrent aproach to getting rid of those characteristic by applying some padding,which one is more effective at avoiding detection and blocking depends on ur country firewall,if u really want multiplexing consider xhttp with reality
2-not really,vision applies some padding to remove some characteristic and will bypass encryption for tls1.3 data to avoid double encryption overhead so removing it does nothing,but i recommend either use vision or mux(do not use vless tcp reality without one of these as it can get blocked) or just use xhttp reality