-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VLESS+Reality and intermediate server configuration #4033
Comments
尝试在服务器上设置环境变量 |
I added |
Error log from XRay_Server2
|
等 @yuhan6665 有空时研究下吧 |
|
REALITY requires tls key exchange must be X25519.
|
|
我想了下客户端实现 XHTTP 挺简单的,packet-up 不难,其它两个 stream 更简单,只有 XMUX 复杂一点点 |
but why does it work well in single XRay server configuration? |
唯一的办法是supported groups里不要带X25519Kyber768Draft00 这样对端自然也不会用这个回复 Xray用的utls压根没更新这个算法所以没问题 以后如果有还得pin住指纹版本 |
感觉上下行分离比 XMUX 简单很多,还有我今天才发现 stream-one 实际用的 path 是 |
To 群里:
ae62a0f#commitcomment-150004845 意思是你写 |
是的。我测试就 RPRX 大神所说一样。 |
Integrity requirements
Description
When using VLESS+Reality and a configuration with an intermediate server (XRay_Client <- VLESS+Reality -> XRay_Server1 <- VLESS+Reality -> XRay_Server2), some services work very inconsistently.
For example, https://console.firebase.google.com/ refuses to load, or parts of its functionality become unavailable.
Enabling or disabling sniffing, does not change the situation.
However, if the classic configuration with a single XRay server is used (XRay_Client <- VLESS+Reality -> XRay_Server2), such issues do not occur.
Reproduction Method
Create configuration: XRay_Client <- VLESS+Reality -> XRay_Server1 <- VLESS+Reality -> XRay_Server2
and go to https://console.firebase.google.com/
Client config
N/A
Server config
XRay_server1 conf
XRay_server2 conf
Client log
N/A
Server log
N/A
The text was updated successfully, but these errors were encountered: