[Bug]: VLESS Reality fails with Xray core while the same profile works with sing-box core [RU region] #9567
OverKilL013
started this conversation in
General
Replies: 1 comment
|
使用问题我们不处理 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
操作系统和版本
Windows 11 x64 v2rayN: 7.22.7 Previous versions tested: 7.16.9 and 7.22.5 — same issue Core with issue: Xray core bundled with v2rayN / Xray v26+ Working core in v2rayN: sing-box Server panel: Marzban fork Server core: Xray v25.10.15 Protocol: VLESS + Reality Transports tested: TCP + Vision, XHTTP Flow for TCP: xtls-rprx-vision allowInsecure: not used
预期情况
VLESS + Reality nodes should connect and proxy traffic normally in v2rayN when using Xray core. When system proxy or manual browser proxy is enabled, websites should open through the selected proxy node. The same server and subscription should work consistently with supported cores and clients.
实际情况
v2rayN shows that the VLESS + Reality node is connected, but websites do not open through proxy mode when the core type for VLESS is set to Xray.
Direct mode works normally. The internet connection itself is fine.
The same server and subscription work in other clients, for example Hiddify / Karing. The same VLESS + Reality profile also works in v2rayN if I change the core type for VLESS from Xray to sing-box. After switching to sing-box, the connection is fully restored and websites open normally.
The issue started suddenly at June 5 2006 without changing server or client configuration. This suggests that the server, account, Reality keys, SNI, shortId and server-side routing are valid, and the problem may be related to Xray-core/uTLS/ClientHello behavior on the client side.
复现方法
Network environment: RU region / Russian ISP network.
Open v2rayN 7.22.7 on Windows 11 x64.
Import or use an existing VLESS + Reality subscription generated by Marzban fork.
Select a VLESS + Reality TCP Vision node.
Make sure the core type for VLESS is set to Xray.
Enable system proxy or configure browser manual proxy through v2rayN.
Open any website in the browser, for example https://www.google.com/ or https://1.1.1.1/.
v2rayN shows that the node is connected, but websites do not open.
Change the core type for VLESS from Xray to sing-box in v2rayN settings.
Use the same node again.
Websites start opening normally.
The issue appears only when VLESS uses Xray core. The same profile works when VLESS uses sing-box core inside v2rayN.
软件日志
Visible behavior:
2026-06-15.txt
v2rayN starts normally.
The subscription is imported normally.
The VLESS + Reality node appears available.
When Xray core is selected for VLESS, the node shows connected, but browser traffic does not open websites.
Direct mode works normally.
After switching VLESS core type from Xray to sing-box, the same node works normally.
内核日志
With Xray core selected for VLESS:
The VLESS + Reality node appears to connect.
Browser traffic does not open websites through the proxy.
Direct mode works normally.
With sing-box core selected for VLESS:
The same VLESS + Reality node works normally.
Websites open through proxy mode.
2026-06-15_info_panel_log.txt
额外信息
The server side was checked and appears to be working correctly.
Server panel: Marzban fork
Server core: Xray v25.10.15
Protocol: VLESS + Reality
TCP flow: xtls-rprx-vision
allowInsecure: not used
The same server and subscription work in other clients, for example Hiddify / Karing. The same profile also works inside v2rayN when the VLESS core type is switched from Xray to sing-box.
This may be related to Xray-core/uTLS/ClientHello behavior for VLESS + Reality on the client side.
Similar behavior is reported for another Xray-based client:
LXST-CODE/v2RayTun#4
The issue is observed from the RU region / Russian network environment. It may be related to regional traffic filtering, because the same profile works when VLESS core type is switched from Xray to sing-box.
Also it all works fine before June 5 2026
我确认已更新至最新版本
我确认已查询历史issues
我确认系统版本是受支持的
All reactions