XHTTP + REALITY stops working after upgrading v26.6.27 → v26.7.11

[alikoleini]

VLESS + XHTTP + REALITY inbound works fine on v26.6.27. After upgrading to v26.7.11 with the exact same config, clients can no longer connect. Downgrading back to v26.6.27 immediately fixes it.

[Fangliding]

af7eb68
happy days
不过限制到三点几有点太狠了 上次utls出漏洞的版本几来着？

[naico-wang]

same issue here.

[naico-wang]

@Fangliding 这个能告知一下是哪里配置的问题么？就是连不上，感谢

[Fangliding]

https://xtls.github.io/config/transports/reality.html
minClientVer 改成1.0.0啥的

[EuraGoods]

same problem.

[naico-wang]

https://xtls.github.io/config/transports/reality.html minClientVer 改成1.0.0啥的

解决了，还得是你啊，优秀

[EuraGoods]

https://xtls.github.io/config/transports/reality.html minClientVer 改成1.0.0啥的

解决了，还得是你啊，优秀

  "privateKey": "脱敏处理",
  "minClientVer": "1.0.0",  //这里这样改？
  "maxClientVer": "",
  "maxTimediff": 0,
  "shortIds": [
    "脱敏处理"

[papka1974]

https://xtls.github.io/config/transports/reality.html minClientVer 改成1.0.0啥的

解决了，还得是你啊，优秀

Not solved problem for me.

[Raymond520888]

@UbiVPN Set the min client version to 1.0.0

[z1911399337-collab]

Additional confirmation from Shadowrocket clients:

• Reproduced on three independent VPS instances in different regions/providers after upgrading to 3x-ui 3.5.0 / Xray-core 26.7.11.
• Existing inbounds use VLESS + REALITY + xtls-rprx-vision; the tested transports include TCP and XHTTP.
• Shadowrocket 2.2.90 on iOS and macOS could still sometimes show a latency value, but real proxy traffic failed. The client log showed: backend vless <redacted>: read error => -4
• The exact same unchanged nodes continued to work with v2rayN on Windows and macOS.
• UUID, REALITY keys, short ID, SNI, ports, subscription links, panel database, and generated config were not changed.
• Keeping 3x-ui 3.5.0 and replacing only the server-side Xray binary with official 26.6.27 immediately restored Shadowrocket on all three servers.

This confirms that the 26.7.11 behavior also affects Shadowrocket and is not limited to one VPS, provider, platform, or XHTTP-only setups.

Please consider either preserving the previous behavior when minClientVer is unset, or prominently documenting this as a breaking compatibility change. A silent fallback/timeout makes it look like a network, REALITY key, or client configuration failure.

[Raymond520888]

@z1911399337-collab

[lipenghui]

[Raymond520888]

Edit inbound, find security-reality, and set the min client version to 1.0.0 ---- Replied Message ---- ***@***.***>Date07/15/2026 03:50 ***@***.***> ***@***.***>, ***@***.***>SubjectRe: [XTLS/Xray-core] XHTTP + REALITY stops working after upgrading v26.6.27 → v26.7.11 (Issue #6482) SeFeRus left a comment (XTLS/Xray-core#6482) Same VPS, same client v2raytun, same VLESS REALITY TCP config. Xray 26.6.27 works. Xray 26.7.11 fails. New clean REALITY inbound also fails. TCP handshake reaches server — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you commented.Message ID: ***@***.***>