Can't get WARP to work on Marzban Node

[PanoSeiza]

Hello!

WARP works correctly on the main marzban server, but doesn't work when connecting through the node. Websites routed through WARP simply do not open.
WARP was set up through Xray Core (not the Wireguard method), so I didn't do anything specific for warp on the node itself.

Here's my xray config:

{
  "log": {
    "loglevel": "debug"
  },
  "routing": {
    "rules": [
      {
        "ip": [
          "geoip:private"
        ],
        "outboundTag": "BLOCK",
        "type": "field"
      },
      {
        "type": "field",
        "outboundTag": "BLOCK",
        "protocol": [
          "bittorrent"
        ]
      },
      {
        "outboundTag": "WARP",
        "domain": [
          "geosite:google"],
        "type": "field"
      }
    ]
  },
  "inbounds": [
    {
      "tag": "VLESS TCP REALITY 8443",
      "listen": "0.0.0.0",
      "port": 8443,
      "protocol": "vless",
      "settings": {
        "clients": [],
        "decryption": "none"
      },
      "streamSettings": {
        "network": "tcp",
        "tcpSettings": {},
        "security": "reality",
        "realitySettings": {
          "show": false,
          "dest": "www.samsung.com:443",
          "xver": 0,
          "serverNames": [
            "www.samsung.com"
          ],
          "privateKey": "...",
          "shortIds": [
            "",
            "..."
          ]
        }
      },
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls",
          "quic"
        ]
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "freedom",
      "tag": "DIRECT"
    },
    {
      "protocol": "blackhole",
      "tag": "BLOCK"
    },
    {
      "tag": "WARP",
      "protocol": "wireguard",
      "settings": {
        "secretKey": "...=",
        "DNS": "1.1.1.1",
        "address": [
          "172.16.0.2/32"
        ],
        "peers": [
          {
            "publicKey": "...",
            "endpoint": "engage.cloudflareclient.com:2408"
          }
        ],
        "kernelMode": false
      }
    }
  ]
}

Here are some logs when I try to open translate.google.com through warp, for example:

logs

2024/12/26 19:54:32 [Info] [1219288151] proxy/vless/inbound: firstLen = 1186
2024/12/26 19:54:32 [Info] [1219288151] proxy/vless/inbound: received request for tcp:216.58.211.238:443
2024/12/26 19:54:32 [Info] [1219288151] proxy: Xtls Unpadding new block, content 1826 padding 245 command 0
2024/12/26 19:54:32 [Info] [1219288151] proxy: XtlsFilterTls found tls client hello! 1121
2024/12/26 19:54:32 [Info] [1219288151] app/dispatcher: sniffed domain: translate.google.com
2024/12/26 19:54:32 [Info] [1219288151] app/dispatcher: taking detour [WARP] for [tcp:translate.google.com:443]
2024/12/26 19:54:32 from 5.144.120.38:6382 accepted tcp:216.58.211.238:443 [VLESS TCP REALITY 8443 -> WARP] email: 1.justrandom

2024/12/26 19:54:33 [Info] [251955989] proxy: Xtls Unpadding new block, content 1266 padding 19 command 0
2024/12/26 19:54:33 [Info] [660838307] proxy: XtlsFilterTls stop filtering48
2024/12/26 19:54:33 [Info] [660838307] proxy: XtlsFilterTls stop filtering48
2024/12/26 19:54:33 [Info] [660838307] proxy: XtlsPadding 8 27 1
2024/12/26 19:54:33 [Info] [251955989] proxy: XtlsPadding 8 62 1
2024/12/26 19:54:33 [Info] [251955989] proxy: XtlsFilterTls stop filtering2516
2024/12/26 19:54:33 [Info] [251955989] proxy: XtlsFilterTls stop filtering2516
2024/12/26 19:54:33 [Info] [251955989] proxy: XtlsFilterTls stop filtering2516
2024/12/26 19:54:33 [Info] [251955989] proxy: XtlsFilterTls stop filtering2516
2024/12/26 19:54:33 [Info] [251955989] proxy: Xtls Unpadding new block, content 1266 padding 182 command 1

2024/12/26 19:54:34 [Info] [1085008115] proxy: XtlsFilterTls inconclusive server hello 1024 191

2024/12/26 19:54:34 [Info] [1085008115] proxy: XtlsPadding 1024 242 0
2024/12/26 19:54:34 [Info] [1085008115] proxy: XtlsFilterTls found tls 1.3! 1024 TLS_AES_128_GCM_SHA256
2024/12/26 19:54:34 [Info] [1085008115] proxy: XtlsPadding 1024 63 0
2024/12/26 19:54:34 [Info] [1085008115] proxy: XtlsPadding 3072 46 0
2024/12/26 19:54:34 [Info] [1085008115] proxy: XtlsPadding 2048 243 0
2024/12/26 19:54:34 [Info] [1085008115] proxy: XtlsPadding 672 422 0
2024/12/26 19:54:34 [Info] [1085008115] proxy: Xtls Unpadding new block, content 74 padding 891 command 0
2024/12/26 19:54:34 [Info] [1085008115] proxy: Xtls Unpadding new block, content 92 padding 1167 command 2
2024/12/26 19:54:34 [Info] [1085008115] proxy: CopyRawConn readv
2024/12/26 19:54:34 [Info] [1085008115] proxy: XtlsPadding 970 58 2

2024/12/26 19:54:36 [Info] [1219288151] proxy: XtlsFilterTls inconclusive server hello 1024 191
2024/12/26 19:54:36 [Info] [1219288151] proxy: XtlsPadding 1024 80 0
2024/12/26 19:54:36 [Info] [1219288151] proxy: XtlsFilterTls found tls 1.3! 344 TLS_AES_128_GCM_SHA256
2024/12/26 19:54:36 [Info] [1219288151] proxy: XtlsPadding 344 714 0
2024/12/26 19:54:36 [Info] [1219288151] proxy: XtlsPadding 2736 63 0
2024/12/26 19:54:36 [Info] [1219288151] proxy: XtlsPadding 2048 36 0
2024/12/26 19:54:36 [Info] [1219288151] proxy: XtlsPadding 1687 154 0
2024/12/26 19:54:36 [Info] [1219288151] proxy: Xtls Unpadding new block, content 74 padding 1077 command 0
2024/12/26 19:54:36 [Info] [1219288151] proxy: XtlsPadding 970 207 2

I see the XtlsFilterTls inconclusive server hello 1024 191 errors in the node logs.
Those errors are not present when connecting through the main server and warp works correctly there.