-
Greetings! I use In this simplest configuration, everything works perfectly for my local network. The problems begin when I try to connect any other Reality client to the same 3X-UI server, either just bypassing v2rayA or even from another network (e.g. cellular). In this case, thе added client (no matter xray or sing-box) always returns In other words, v2rayA somehow suppresses all other Reality clients, and the number itself is not the issue (since I've tested simultaneous connection from more than one device, and everything goes fine until v2rayA appears among them). Perhaps the problem is specific to v2rayA |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 12 replies
-
And I'm not the first person to run into this! |
Beta Was this translation helpful? Give feedback.
-
Since you already noticed that you are running into a very rare issue, I suggest that you put this to the test. Eliminate everything you think is not necessary for the problem from your testing setup (panels, weird outbounds on the server, routing rules), and see where you end up. |
Beta Was this translation helpful? Give feedback.
-
If anyone of the developers would like to investigate this case, I can connect to his/her xtls-reality server at arranged hour to demonstrate how things works. |
Beta Was this translation helpful? Give feedback.
-
REALITY 请求被导向了它的 SNI 解析出的 IP,而不是你的服务器 |
Beta Was this translation helpful? Give feedback.
I mean that Xray has the ability to sniff SNI in TLS Client Hello (and REALITY) then override the IP of the destination, which will block REALITY, and you enabled this ability on v2rayA / 3X-UI. As for "even from another network", it seems impossible.