Skip to content
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

[Bug]: xhttp mode: auto not working in v25.3.6 #4533

Closed
Pouryjoon opened this issue Mar 22, 2025 · 7 comments
Closed

[Bug]: xhttp mode: auto not working in v25.3.6 #4533

Pouryjoon opened this issue Mar 22, 2025 · 7 comments

Comments

@Pouryjoon
Copy link

Pouryjoon commented Mar 22, 2025

when i updated to latest v2rayng and v2rayN with latest xray ( v25.3.6 ) xhttp mode : auto doesnt work any more and should select manualy to what it is ( for exmaple packet-up ).
it was working fine in xray V25.1.1

2dust/v2rayN#6897

@RPRX
Copy link
Member

RPRX commented Mar 23, 2025

#4518 (comment)

@RPRX RPRX closed this as not planned Won't fix, can't repro, duplicate, stale Mar 23, 2025
@RPRX
Copy link
Member

RPRX commented Mar 23, 2025

不对,又看了一眼,你的问题应该是整个链路不兼容 stream-one 导致不兼容 auto 的 stream-up

@RPRX
Copy link
Member

RPRX commented Mar 23, 2025

比如说新版 stream-up 要求 Nginx 必须用 grpc_pass,不能是 proxy_pass

@Pouryjoon
Copy link
Author

No, I took another look and your problem should be that the entire link is incompatible with stream-one, which leads to incompatibility with auto's stream-up.

do you mean it may not work after upgrade server side ?
i forgot to say my server side is v25.1.30 , my mistake , before update clients it was working with packet-up and stream-up only (and of course auto) with alpn h2 h3 ( xhttp-tls-bunnyCDN ) now just works with packet-up , i thought auto selects between 3 modes now i know when the client mode is set to "auto", it will select between "stream-one" and "stream-up", i will test with upgraded server side.

@RPRX
Copy link
Member

RPRX commented Mar 23, 2025

@Pouryjoon "auto" 会选择最广泛适用的模式,详见 #4113 中的解释

我不确定你提到的 bunnyCDN 是否有设置能兼容 stream-one,但是如果你只需要恢复 stream-up 到以前的状态,可以在服务端设置 "scStreamUpServerSecs": -1,详见 #4113 中的解释

@RPRX RPRX pinned this issue Mar 23, 2025
@RPRX
Copy link
Member

RPRX commented Mar 23, 2025

In addition,packet-up 的表现经我几轮优化后已经不输 stream-up 了,没什么不好的,只是会自动切换上行连接,主要防请求数超限

@Pouryjoon
Copy link
Author

In addition, after several rounds of optimization, the performance of packet-up is no longer inferior to stream-up. There is nothing wrong with it. It just automatically switches to the upstream connection to prevent the number of requests from exceeding the limit.

yes i noticed that packet-up is fast as enough, thanks for fast reply 💯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants