We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
2.51开始,一直无法打开网页,除非把gui上的自定义DNS数值删除 用的是WS协议,TCP协议的倒是正常,WS的就出问题 但是就算删除,重开软件也会被设置一个自定义DNS,就算写成8.8.8.8,报错也是一个毛病。
报错如下 2019/11/30 00:50:16 tcp:127.0.0.1:6789 accepted tcp:www.youtube.com:443 [proxy] 2019/11/30 00:50:16 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal) 2019/11/30 00:50:20 tcp:127.0.0.1:6793 accepted tcp:www.youtube.com:443 [proxy] 2019/11/30 00:50:20 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal) 2019/11/30 00:50:22 tcp:127.0.0.1:6798 accepted tcp:www.youtube.com:443 [proxy] 2019/11/30 00:50:22 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
The text was updated successfully, but these errors were encountered:
下一版去掉这个强制dns
Sorry, something went wrong.
https://github.com/2dust/v2rayN/releases/tag/2.53
No branches or pull requests
2.51开始,一直无法打开网页,除非把gui上的自定义DNS数值删除
用的是WS协议,TCP协议的倒是正常,WS的就出问题
但是就算删除,重开软件也会被设置一个自定义DNS,就算写成8.8.8.8,报错也是一个毛病。
报错如下
2019/11/30 00:50:16 tcp:127.0.0.1:6789 accepted tcp:www.youtube.com:443 [proxy]
2019/11/30 00:50:16 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
2019/11/30 00:50:20 tcp:127.0.0.1:6793 accepted tcp:www.youtube.com:443 [proxy]
2019/11/30 00:50:20 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
2019/11/30 00:50:22 tcp:127.0.0.1:6798 accepted tcp:www.youtube.com:443 [proxy]
2019/11/30 00:50:22 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
The text was updated successfully, but these errors were encountered: