xhttp+nginx正常工作一段时间后断联，手动重启xray或nginx其中一方即恢复正常，回退2024.12.31版本一切正常

[emiyalee1005]

完整性要求

• 我保证阅读了文档，了解所有我编写的配置文件项的含义，而不是大量堆砌看似有用的选项或默认值。
• 我提供了完整的配置文件和日志，而不是出于自己的判断只给出截取的部分。
• 我搜索了 issues, 没有发现已提出的类似问题。
• 问题在 Release 最新的版本上可以成功复现

描述

如题，实验了有半个月，配置是基于https://github.com/XTLS/Xray-examples/tree/main/VLESS-XHTTP3-Nginx
100%排除客户端到服务端的网络问题，切回2024.12.31版本可以一直正常使用，2025.01.30和2025.1.1版本在断联时在服务端日志会看到大量version invalid之类的信息，但是只要重启xray或nginx任意一方立刻恢复正常。
个人推测是新版本某个改动导致nginx和xray之间的socket通信出了问题？

服务器：oracle arm64
系统:ubuntu 24
nginx:1.26.3

重现方式

2025.1.1及以后的版本，使用一段时间后，最短的十几分钟后就出现断联，随后只要重启xray亦或nginx立刻恢复正常

客户端配置

{
  "log": {
    "loglevel": "debug"
  },
  "inbounds": [
    {
      "listen": "127.0.0.1",
      "port": 10814,
      "protocol": "socks",
      "settings": {
        "udp": true
      },
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "fakedns+others"
        ],
        "routeOnly": true
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "vless",
      "settings": {
        "vnext": [
          {
            "address": "**********",
            "port": 443,
            "users": [
              {
                "encryption": "none",
                "id": "********************"
              }
            ]
          }
        ]
      },
      "streamSettings": {
        "network": "xhttp",
        "xhttpSettings": {
          "path": "/abc",
          "mode": "stream-one"
        },
        "security": "tls",
        "tlsSettings": {
          "serverName": "***************",
          "alpn": [
            "h3",
            "h2",
            "h1"
          ]
        }
      }
    },
    {
      "protocol": "socks",
      "settings": {
        "servers": [
          {
            "address": "********************",
            "port": 34218,
            "users": [
              {
                "user": "**************",
                "pass": "********************"
              }
            ]
          }
        ]
      },
      "streamSettings": {
        "network": "tcp",
        "security": "none"
      },
      "tag": "gn"
    },
    {
      "protocol": "freedom",
      "tag": "Direct",
      "settings": {
        "domainStrategy": "UseIP"
      }
    },
    {
      "protocol": "dns",
      "tag": "Dns-Out",
      "settings": {
        "nonIPQuery": "skip"
      }
    }
  ],
  "dns": {
    "servers": [
      "https://8.8.8.8/dns-query",
      "https://1.1.1.1/dns-query",
      {
        "address": "https+local://223.6.6.6/dns-query",
        "domains": [
          "geosite:cn"
        ]
      },
      {
        "address": "https+local://120.53.53.53/dns-query",
        "domains": [
          "geosite:cn"
        ]
      },
      "localhost"
    ]
  },
  "routing": {
    "domainStrategy": "IPIfNonMatch",
    "rules": [
      {
        "ip": [
          "***************"
        ],
        "outboundTag": "gn"
      },
      {
        "domain": [
          "***************"
        ],
        "outboundTag": "gn"
      },
      {
        "domain": [
          "geosite:cn"
        ],
        "outboundTag": "Direct"
      },
      {
        "ip": [
          "geoip:cn",
          "geoip:private"
        ],
        "outboundTag": "Direct"
      },
      {
        "outboundTag": "Dns-Out",
        "network": "tcp,udp",
        "port": "53"
      }
    ]
  }
}

服务端配置

//nginx
server {
  listen [::]:443 ssl ipv6only=off reuseport;
  listen [::]:443 quic reuseport ipv6only=off;
  server_name *************;
location  / {

proxy_pass http://localhost:8002/;

}
http2 on;

ssl_certificate            /home/ssl/fullchain.cer;

ssl_certificate_key        /home/ssl/private.key;

ssl_protocols TLSv1.2 TLSv1.3;

ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
client_header_timeout 5m;

keepalive_timeout 5m;

# 在 location 后填写 /你的 path/

location /abc/ {

client_max_body_size 0;

grpc_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

client_body_timeout 5m;

grpc_read_timeout 315;

grpc_send_timeout 5m;

grpc_pass unix:/dev/shm/xrxh.socket;

}

}
//xray

{

"log": {

"loglevel": "debug"

},

"inbounds": [

{

"listen": "/dev/shm/xrxh.socket,0666",

"protocol": "vless",

"settings": {

"clients": [

{

"id": "" //我是以这个帐户连入

},

{

"id": "", //未使用

"email": "abc@aaa.com"

}

],

"decryption": "none"

},

"streamSettings": {

"network": "xhttp",

"xhttpSettings": {

"mode": "auto",

"path": "/abc"

}

},

"sniffing": {

"enabled": true,

"destOverride": [

"fakedns+others"

],

"routeOnly": true

}

}

],

"outbounds": [

{

"protocol": "freedom",

"tag": "direct"

},

{

"protocol": "blackhole",

"tag": "block"

},

{

"protocol": "wireguard",

"settings": {

"secretKey": "",

"address": [

"",

"********"

],

"peers": [

{

"publicKey": "",

"endpoint": "***"

}

]

},

"tag": "wireguard-1"

}

],

"routing": {

"rules": [

{

"type": "field",

"user": [

"abc@aaa.com"

],

"ip": [

"geoip:private"

],

"outboundTag": "block"

},

{

"type": "field",

"user": [

"abc@aaa.com"

],

"outboundTag": "wireguard-1"

}

]

}

}

客户端日志

2025/02/09 05:26:01.250493 [Info] [2271167988] transport/internet/splithttp: XHTTP is dialing to tcp:*.*.*.*:443, mode stream-one, HTTP version 2, host abc.com
2025/02/09 05:26:01.250604 [Info] [2271167988] proxy/vless/outbound: tunneling request to tcp:www.google.com:443 via *.*.*.*:443
2025/02/09 05:26:01.832433 [Info] [2219275785] app/proxyman/inbound: connection ends > proxy/socks: connection ends > context canceled
2025/02/09 05:26:01.838597 [Info] [2485557641] proxy/socks: TCP Connect request to tcp:www.google.com:443
2025/02/09 05:26:01.839443 [Debug] app/dns: domain www.google.com will use DNS in order: [DOH//8.8.8.8 DOH//1.1.1.1 DOHL//223.6.6.6 DOHL//120.53.53.53 localhost]
  2025/02/09 05:26:01.839504 [Debug] app/dns: DOH//8.8.8.8 cache HIT www.google.com -> [142.250.197.164 2404:6800:4005:823::2004]
2025/02/09 05:26:01.839515 [Info] [2485557641] app/dispatcher: default route for tcp:www.google.com:443
2025/02/09 05:26:01.839520 [Info] [2485557641] transport/internet/splithttp: XHTTP is dialing to tcp:*.*.*.*:443, mode stream-one, HTTP version 2, host abc.com
2025/02/09 05:26:01.839562 from tcp:127.0.0.1:64882 accepted tcp:www.google.com:443
2025/02/09 05:26:01.839670 [Info] [2485557641] proxy/vless/outbound: tunneling request to tcp:www.google.com:443 via *.*.*.*:443
2025/02/09 05:26:02.157268 [Info] [1080914123] app/proxyman/inbound: connection ends > proxy/socks: connection ends > context canceled
2025/02/09 05:26:02.165125 [Info] [2731262781] proxy/socks: TCP Connect request to tcp:www.google.com:443
2025/02/09 05:26:02.166138 [Debug] app/dns: domain www.google.com will use DNS in order: [DOH//8.8.8.8 DOH//1.1.1.1 DOHL//223.6.6.6 DOHL//120.53.53.53 localhost]
  2025/02/09 05:26:02.166177 [Debug] app/dns: DOH//8.8.8.8 cache HIT www.google.com -> [142.250.197.164 2404:6800:4005:823::2004]
2025/02/09 05:26:02.166190 [Info] [2731262781] app/dispatcher: default route for tcp:www.google.com:443
2025/02/09 05:26:02.166224 from tcp:127.0.0.1:64883 accepted tcp:www.google.com:443
2025/02/09 05:26:02.166320 [Info] [2731262781] transport/internet/splithttp: XHTTP is dialing to tcp:*.*.*.*:443, mode stream-one, HTTP version 2, host abc.com
2025/02/09 05:26:02.166447 [Info] [2731262781] proxy/vless/outbound: tunneling request to tcp:www.google.com:443 via *.*.*.*:443
2025/02/09 05:26:02.430282 [Info] [3350235458] app/proxyman/inbound: connection ends > proxy/socks: connection ends > context canceled
2025/02/09 05:26:02.470432 [Info] [2271167988] app/proxyman/inbound: connection ends > proxy/socks: connection ends > context canceled
2025/02/09 05:26:03.060507 [Info] [2485557641] app/proxyman/inbound: connection ends > proxy/socks: connection ends > context canceled
2025/02/09 05:26:03.386826 [Info] [2731262781] app/proxyman/inbound: connection ends > proxy/socks: connection ends > context canceled

服务端日志

//xray
Feb 08 21:19:08 instance-20250106-0509 xray[931]: 2025/02/08 21:19:08.199679 [Info] [4115563481] app/proxyman/inbound: connection ends > proxy/vless/inbound: connection ends > proxy/vless/inbound: failed to transfer request payload > body>
Feb 08 21:19:11 instance-20250106-0509 xray[931]: 2025/02/08 21:19:11.981683 [Info] [1288055270] app/proxyman/inbound: connection ends > proxy/vless/inbound: connection ends > proxy/vless/inbound: failed to transfer request payload > body>
Feb 08 21:19:14 instance-20250106-0509 xray[931]: 2025/02/08 21:19:14.150042 [Info] [868563740] proxy/vless/inbound: firstLen = 0
Feb 08 21:19:14 instance-20250106-0509 xray[931]: 2025/02/08 21:19:14.150523 [Info] [868563740] app/proxyman/inbound: connection ends > proxy/vless/encoding: failed to read request version > EOF
Feb 08 21:19:19 instance-20250106-0509 xray[931]: 2025/02/08 21:19:19.033295 [Info] [1637337060] proxy/vless/inbound: firstLen = 0
Feb 08 21:19:19 instance-20250106-0509 xray[931]: 2025/02/08 21:19:19.033651 [Info] [1637337060] app/proxyman/inbound: connection ends > proxy/vless/encoding: failed to read request version > EOF
Feb 08 21:19:41 instance-20250106-0509 xray[931]: 2025/02/08 21:19:41.991675 [Info] [3950893679] proxy/vless/inbound: firstLen = 0
Feb 08 21:19:41 instance-20250106-0509 xray[931]: 2025/02/08 21:19:41.992538 [Info] [3950893679] app/proxyman/inbound: connection ends > proxy/vless/encoding: failed to read request version > EOF
Feb 08 21:19:50 instance-20250106-0509 xray[931]: 2025/02/08 21:19:50.826198 [Info] [959533932] proxy/vless/inbound: firstLen = 0
Feb 08 21:19:50 instance-20250106-0509 xray[931]: 2025/02/08 21:19:50.826604 [Info] [959533932] app/proxyman/inbound: connection ends > proxy/vless/encoding: failed to read request version > EOF
//nginx

2025/02/08 21:31:35 [crit] 994#994: accept4() failed (24: Too many open files)

2025/02/08 21:31:35 [alert] 994#994: 2866 socket() failed (24: Too many open files) while connecting to upstream, client: ::ffff:..., server: abc.com, request: "GET /abc/************************ HTTP/2.0", upstream: "grpc://unix:/dev/shm/xrxh.socket:", host: "abc.com", referrer: "https://abc.com/abc/*************************?x_padding=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

2025/02/08 21:31:35 [alert] 994#994: 2867 socket() failed (24: Too many open files) while connecting to upstream, client: ::ffff:..., server: abc.com, request: "POST /abc/************************ HTTP/2.0", upstream: "grpc://unix:/dev/shm/xrxh.socket:", host: "abc.com", referrer: "https://abc.com/abc/*************************?x_padding=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

2025/02/08 21:31:36 [crit] 994#994: accept4() failed (24: Too many open files)

2025/02/08 21:31:36 [alert] 994#994: 2866 socket() failed (24: Too many open files) while connecting to upstream, client: ::ffff:..., server: abc.com, request: "GET /abc/************************ HTTP/2.0", upstream: "grpc://unix:/dev/shm/xrxh.socket:", host: "abc.com", referrer: "https://abc.com/abc/*************************?x_padding=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

2025/02/08 21:31:36 [alert] 994#994: 2867 socket() failed (24: Too many open files) while connecting to upstream, client: ::ffff:..., server: abc.com, request: "POST /abc/************************ HTTP/2.0", upstream: "grpc://unix:/dev/shm/xrxh.socket:", host: "abc.com", referrer: "https://abc.com/abc/*************************?x_padding=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

2025/02/08 21:31:36 [crit] 994#994: accept4() failed (24: Too many open files)

2025/02/08 21:31:36 [alert] 994#994: 1714 socket() failed (24: Too many open files) while connecting to upstream, client: ::ffff:..., server: abc.com, request: "GET /abc/************************ HTTP/2.0", upstream: "grpc://unix:/dev/shm/xrxh.socket:", host: "abc.com", referrer: "https://abc.com/abc/*************************?x_padding=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

2025/02/08 21:31:36 [alert] 994#994: 1717 socket() failed (24: Too many open files) while connecting to upstream, client: ::ffff:..., server: abc.com, request: "POST /abc/************************ HTTP/2.0", upstream: "grpc://unix:/dev/shm/xrxh.socket:", host: "abc.com", referrer: "https://abc.com/abc/*************************?x_padding=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

2025/02/08 21:31:36 [alert] 994#994: 2444 socket() failed (24: Too many open files) while connecting to upstream, client: ::ffff:..., server: abc.com, request: "GET /abc/************************ HTTP/2.0", upstream: "grpc://unix:/dev/shm/xrxh.socket:", host: "abc.com", referrer: "https://abc.com/abc/*************************?x_padding=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

2025/02/08 21:31:36 [alert] 994#994: 2445 socket() failed (24: Too many open files) while connecting to upstream, client: ::ffff:..., server: abc.com, request: "POST /abc/************************ HTTP/2.0", upstream: "grpc://unix:/dev/shm/xrxh.socket:", host: "abc.com", referrer: "https://abc.com/abc/*************************?x_padding=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

2025/02/08 21:31:37 [crit] 994#994: accept4() failed (24: Too many open files)

2025/02/08 21:31:37 [alert] 994#994: 2446 socket() failed (24: Too many open files) while connecting to upstream, client: ::ffff:..., server: abc.com, request: "GET /abc/************************ HTTP/2.0", upstream: "grpc://unix:/dev/shm/xrxh.socket:", host: "abc.com", referrer: "https://abc.com/abc/*************************?x_padding=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

2025/02/08 21:31:37 [alert] 994#994: 2447 socket() failed (24: Too many open files) while connecting to upstream, client: ::ffff:..., server: abc.com, request: "POST /abc/************************ HTTP/2.0", upstream: "grpc://unix:/dev/shm/xrxh.socket:", host: "abc.com", referrer: "https://abc.com/abc/*************************?x_padding=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

[emiyalee1005]

已补上日志

[RPRX]

1. v25.1.1 几乎没有代码层面的改动，最相关的就是升级了 quic-go
2. 但是你客户端 alpn 同时写三个，此时用到的是 h2 而非 h3
3. 服务端 domain socket 还能 too many open files，不太清楚是怎么回事，可能有巨量连接开了没关？内存或磁盘满了？
4. 因为这个一般常见于 TCP，对于 DS 我还是第一次见，你搜一下
5. 重启服务端 Xray / Nginx 会导致 socket 全部被释放，所以能恢复正常

[emiyalee1005]

On Sun, Feb 9, 2025 at 08:48 RPRX ***@***.***> wrote: 1. v25.1.1 几乎没有代码层面的改动，最相关的就是升级了 quic-go 2. 但是你客户端 alpn 同时写三个，*此时用到的是 h2 而非 h3* 3. 服务端 domain socket 还能 *too many open files* ，不太清楚是怎么回事，可能有巨量连接开了没关？内存或磁盘满了？ 4. 因为这个一般常见于 TCP，*对于 DS 我还是第一次见*，你搜一下 5. 重启服务端 Xray / Nginx 会导致 socket 全部被释放，所以能恢复正常 — Reply to this email directly, view it on GitHub <#4373 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHSMRD2BPGSAX74D43CAF32O2QV3AVCNFSM6AAAAABWYB3XBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBWGAYDGOJVGE> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

最主要之前版本都用得好好 升级了新版本就不行了 比较郁闷 只能回退了

[RPRX]

我的看法是有很多人在用 Nginx+XHTTP 的组合，如果新版有问题早就有很多人说了

应该是你哪里配置比较奇怪，你应该把 Nginx 配置发出来让别人看看，在群里问问

[emiyalee1005]

服务端配置那里我已经把nginx贴出来了 我目前是加大了nginx侧的nofile再试下

…

On Sun, Feb 9, 2025 at 09:42 RPRX ***@***.***> wrote: 我的看法是有很多人在用 Nginx+XHTTP 的组合，如果新版有问题早就有很多人说了 应该是你哪里配置比较奇怪，你应该把 Nginx 配置发出来让别人看看，在群里问问 — Reply to this email directly, view it on GitHub <#4373 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHSMRFDQ2HCP33MVQXOFTL2O2W7JAVCNFSM6AAAAABWYB3XBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBWGAYTMOJRGE> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[xxxsen]

有碰到类似的问题，版本2025.01.30，但是mode填的是auto，后面看了下是ng的连接数被打满(4进程，单进程2048连接数)，然后ng的错误日志里面刷了一堆的worker_connections are not enough错误，正常是不可能把连接数打满的(之前的版本一直正常)，然后把模式改成packet-up就没再出现问题了。

====

使用auto的场景下，重启ng后，发现连接数会缓慢增长(中间也有减少的情况,但是整体上是一直增长的)，怀疑是部分异常case下连接用完后没有正常关闭

[wtfr-dot]

我升级到2025.1.30也出现了这个问题：[crit] 741#741: accept4() failed (24: Too many open files)，重启xray就恢复正常，然后过一阵又出现，再重启又正常

[RPRX]

猜想可能是 stream-up 服务端的新行为（保活）导致连接没断开？不过按理说 POST 应该和 GET 同步断开才对

但 @emiyalee1005 提供的信息可能有误，因为 v25.1.1 服务端还没这个行为，你要说明 Xray 服务端、客户端分别是什么版本

你们试试双端均为 v25.1.30 时：

1. 只用 packet-up（应该没问题）
2. 只用 stream-one（应该也没问题）
3. 只用 stream-up（应该有问题）
4. 服务端设置 "scStreamUpServerSecs": -1 以关闭新行为，然后只用 stream-up

既然可能存在 bug，v25.2.9 也要 nightly 了，解决完这个再正式发版，也可能是 Nginx 哪里需要特殊设置

[xxxsen]

4. scStreamUpServerSecs

双端 v25.1.30

测试了下stream-up, 一秒一次curl, 隔一段时间后, nginx侧出现很多ESTABLISH状态的链接(client->ng, ng->server), 同时这些链接隔很长一段时间后还继续保持着, 在服务端重启后, ng->server链接立即被关闭, 但是client->ng方向的链接隔了一段时间才关闭。

服务端增加参数: "scStreamUpServerSecs": -1 重新按上面的步骤测试, 在经过一段时间后, nginx侧还是会出现很多无法关闭的链接, 然后隔了一段时间后才逐个关闭。

相关的配置

客户端配置:

{
  "outbounds": [
    {
      "protocol": "vless",
      "settings": {
        "vnext": [
          {
            ...
          }
        ]
      },
      "streamSettings": {
        "network": "xhttp",
        "xhttpSettings": {
          "mode": "stream-up",
          "host": "abc.test.com",
          "path": "/path"
        },
        "security": "tls",
        "tlsSettings": {
          "serverName": "abc.test.com",
          "fingerprint": "chrome"
        }
      },
      "tag": "out-default"
    }
  ]
}

服务端配置:

{
  "log": {
    "loglevel": "debug",
    "access": "/tmp/xray-server/xray_access.log",
    "error": "/tmp/xray-server/xray_error.log"
  },
  "inbounds": [
    {
      "listen": "0.0.0.0",
      "port": 10086,
      "protocol": "vless",
      "settings": {
        "clients": [
          {
               ...
          }
        ],
        "decryption": "none"
      },
      "streamSettings": {
        "network": "xhttp",
        "xhttpSettings": {
          "path": "/path",
          "scStreamUpServerSecs": -1
        }
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "freedom",
      "tag": "direct"
    }
  ],
  "routing": {}
}

ng配置:

server
{
    include nginx_svr_bind;
    server_name  abc.test.com;

    client_header_timeout 2m;
    keepalive_timeout 2m;

    location /path {
        set $upstream "grpc://xray-server:10086";
        client_max_body_size 0;
        client_body_timeout 2m;
        grpc_pass $upstream;
        grpc_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        grpc_read_timeout 10m;
        grpc_send_timeout 10m;
    }
}

[RPRX]

@xxxsen packet-up 和 stream-one 呢？双端 v25.1.1 和 v24.12.31 呢？