v2rayN
v2rayN copied to clipboard
[Bug]: io: read/write on closed pipe on v2rayN V5.36
预期情况
Successful connection
实际情况
I have two PC on the same network with the same situation (same os (windows 10 same built), same destination server, same software (v2rayN latest version: V5.36, Xray core: 1.6)
One connects successfully (PC 1), and one has a problem (PC 2). I tried same settings, various settings, different user (created with different UUID and etc. ) but whatever I do, PC2 is not working
on PC2, test server ping is working but "Test server real delay" is not working a showing "the operation has timed out" on PC2, when I use a VPN, v2rayN works perfect ( the problem is v2rayN should work without any VPN or proxy! that's the goal...)
the V2rayN shows this log:
`Configuration successful [] [VLESS] XXXXXXXXXXX(XXXXX:443) Start service (10/8/2022 11:04:37 PM)... Xray 1.6.0 (Xray, Penetrates Everything.) Custom (go1.19.1 windows/amd64) A unified platform for anti-censorship. 2022/10/08 23:04:37 [Info] infra/conf/serial: Reading config: XXXX\v2rayN-Core\config.json 2022/10/08 23:04:37 [Warning] core: Xray 1.6.0 started 2022/10/08 23:04:54 127.0.0.1:58296 accepted http://detectportal.firefox.com/canonical.html [http -> proxy] 2022/10/08 23:04:54 127.0.0.1:58298 accepted //contile.services.mozilla.com:443 [http -> proxy] 2022/10/08 23:04:55 127.0.0.1:58300 accepted //normandy.cdn.mozilla.net:443 [http -> proxy] 2022/10/08 23:04:55 127.0.0.1:58302 accepted //content-signature-2.cdn.mozilla.net:443 [http -> proxy] 2022/10/08 23:04:55 127.0.0.1:58304 accepted //firefox.settings.services.mozilla.com:443 [http -> proxy] 2022/10/08 23:04:55 127.0.0.1:58306 accepted //push.services.mozilla.com:443 [http -> proxy] 2022/10/08 23:04:55 127.0.0.1:49936 accepted //safebrowsing.googleapis.com:443 [http -> proxy] 2022/10/08 23:04:55 127.0.0.1:49935 accepted //firefox.settings.services.mozilla.com:443 [http -> proxy] 2022/10/08 23:04:55 127.0.0.1:64283 accepted //firefox.settings.services.mozilla.com:443 [http -> proxy] 2022/10/08 23:04:56 127.0.0.1:64287 accepted //incoming.telemetry.mozilla.org:443 [http -> proxy] 2022/10/08 23:04:59 127.0.0.1:60340 accepted http://detectportal.firefox.com/canonical.html [http -> proxy] 2022/10/08 23:05:00 127.0.0.1:60342 accepted //XXXXXXXXX:443 [http -> proxy] 2022/10/08 23:05:02 127.0.0.1:60344 accepted //XXXXXXXXXXXXX:443 [http -> proxy] 2022/10/08 23:05:02 127.0.0.1:60345 accepted //XXXXXXXXXXXXX:443 [http -> proxy] 2022/10/08 23:05:02 127.0.0.1:60348 accepted //XXXXXXXXXXXXXXXXXX:443 [http -> proxy] 2022/10/08 23:05:03 127.0.0.1:59083 accepted //XXXXXXXXXXXXXXXXXX:443 [http -> proxy]
2022/10/08 23:05:14 [Warning] [3729037515] proxy/http: failed to read response from detectportal.firefox.com > io: read/write on closed pipe 2022/10/08 23:05:15 127.0.0.1:59110 accepted //content-signature-2.cdn.mozilla.net:443 [http -> proxy] 2022/10/08 23:05:15 127.0.0.1:59112 accepted //incoming.telemetry.mozilla.org:443 [http -> proxy] 2022/10/08 23:05:15 127.0.0.1:59113 accepted //incoming.telemetry.mozilla.org:443 [http -> proxy] 2022/10/08 23:05:16 127.0.0.1:59116 accepted //incoming.telemetry.mozilla.org:443 [http -> proxy] 2022/10/08 23:05:16 127.0.0.1:59117 accepted //incoming.telemetry.mozilla.org:443 [http -> proxy] 2022/10/08 23:05:16 127.0.0.1:59120 accepted //incoming.telemetry.mozilla.org:443 [http -> proxy] 2022/10/08 23:05:16 [Warning] [1777554928] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: connection ends > proxy/vless/outbound: failed to write A request payload > read tcp 192.168.1.9:49937->XXXXXXXXXXX:443: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 2022/10/08 23:05:16 127.0.0.1:59122 accepted //shavar.services.mozilla.com:443 [http -> proxy] 2022/10/08 23:05:17 127.0.0.1:59125 accepted //incoming.telemetry.mozilla.org:443 [http -> proxy] 2022/10/08 23:05:18 127.0.0.1:59127 accepted //incoming.telemetry.mozilla.org:443 [http -> proxy] 2022/10/08 23:05:19 [Warning] [349509844] proxy/http: failed to read response from detectportal.firefox.com > io: read/write on closed pipe 2022/10/08 23:05:19 127.0.0.1:59129 accepted //XXXXXXXXXXXX:443 [http -> proxy] 2022/10/08 23:05:19 127.0.0.1:59132 accepted //push.services.mozilla.com:443 [http -> proxy] 2022/10/08 23:05:19 127.0.0.1:59134 accepted http://detectportal.firefox.com/canonical.html [http -> proxy] 2022/10/08 23:05:26 [Warning] [3213547902] proxy/http: failed to read response from detectportal.firefox.com > io: read/write on closed pipe`
P.S : I replaced some IP with XXXXXX
here is the config file :
{ "log": { "access": "", "error": "", "loglevel": "warning" }, "inbounds": [ { "tag": "socks", "port": 10808, "listen": "127.0.0.1", "protocol": "socks", "sniffing": { "enabled": true, "destOverride": [ "http", "tls" ] }, "settings": { "auth": "noauth", "udp": true, "allowTransparent": false } }, { "tag": "http", "port": 10809, "listen": "127.0.0.1", "protocol": "http", "sniffing": { "enabled": true, "destOverride": [ "http", "tls" ] }, "settings": { "auth": "noauth", "udp": true, "allowTransparent": false } } ], "outbounds": [ { "tag": "proxy", "protocol": "vless", "settings": { "vnext": [ { "address": "XXXXXXXXXXXX", "port": 443, "users": [ { "id": "XXXXXXXXXXXXXXXX", "alterId": 0, "email": "[email protected]", "security": "auto", "encryption": "none", "flow": "xtls-rprx-direct" } ] } ] }, "streamSettings": { "network": "tcp", "security": "xtls", "xtlsSettings": { "allowInsecure": false, "serverName": "XXXXXXXXXX" } }, "mux": { "enabled": false, "concurrency": -1 } }, { "tag": "direct", "protocol": "freedom", "settings": {} }, { "tag": "block", "protocol": "blackhole", "settings": { "response": { "type": "http" } } } ], "routing": { "domainStrategy": "IPIfNonMatch", "domainMatcher": "linear", "rules": [ { "type": "field", "inboundTag": [ "api" ], "outboundTag": "api", "enabled": true }, { "type": "field", "outboundTag": "direct", "domain": [ "domain:example-example.com", "domain:example-example2.com" ], "enabled": true }, { "type": "field", "outboundTag": "block", "domain": [ "geosite:category-ads-all" ], "enabled": true }, { "type": "field", "outboundTag": "direct", "domain": [ "geosite:cn" ], "enabled": true }, { "type": "field", "outboundTag": "direct", "ip": [ "geoip:private", "geoip:cn" ], "enabled": true }, { "type": "field", "port": "0-65535", "outboundTag": "proxy", "enabled": true } ] } }
PC2 OS is : windows 10 version 21H2 OS build 19044.2075
复现方法
Opened V2rayN , imported servers by bulk URL, set as active server , System proxy > set system proxy
日志信息
attached the log
额外信息
No response
我确认已更新至最新版本
- [X] 是
我确认已查询历史issues
- [X] 是
@KourosZanbouri Chetori vasl shodi ? yad midi ? hamash chiniese neveshte to application
@KourosZanbouri Chetori vasl shodi ? yad midi ? hamash chiniese neveshte to application
You can change the language in the application ( windows software is called v2rayN) from the help option ( 3rd icon from right-first is close, second is promotion and the third is help, select help then the third option is language-english) for the server side, you need to config it yourself . I suggest you follow youtube tutorials and use shell-based ready scripts such as v2ray-agent from mack-a to configure the server
i have the same situation with 2 pc and producing exact problem with the same log. tested with my old netchx client and same xray build and no problem.
Ok i just used an older version of xray and its ok with it.
i have the same situation with 2 pc and producing exact problem with the same log. tested with my old netchx client and same xray build and no problem.
Thank you. Yep same problem; I tried various scenarios ( even changed the default port ) the v2rayN has the problem, However, I tested your mentioned client "netch" and it worked with the same config...
Ok i just used an older version of xray and its ok with it.
I tried several versions ( tested on 5.36, 5.34 ,5.26 and even 5.23 ) but none of them worked...
the problem still persist and i cant use v2rayn with xray core version above 1.3.1. my other machines can use v2rayn with any xray core, is there any config for that?
i have the same situation with 2 pc and producing exact problem with the same log. tested with my old netchx client and same xray build and no problem.
Thank you. Yep same problem; I tried various scenarios ( even changed the default port ) the v2rayN has the problem, However, I tested your mentioned client "netch" and it worked with the same config...
Ok i just used an older version of xray and its ok with it.
I tried several versions ( tested on 5.36, 5.34 ,5.26 and even 5.23 ) but none of them worked...
i had the same problem, you must disable any vpn extention on your browser (Chrome, Firefox, ...) and your system time must be same as your v2ray server time ...
my xray version is 1.6.0 and v2rayN version is 5.34
@KourosZanbouri Chetori vasl shodi ? yad midi ? hamash chiniese neveshte to application
You can change the language in the application ( windows software is called v2rayN) from the help option ( 3rd icon from right-first is close, second is promotion and the third is help, select help then the third option is language-english) for the server side, you need to config it yourself . I suggest you follow youtube tutorials and use shell-based ready scripts such as v2ray-agent from mack-a to configure the server 2024/02/02 18:48:42 127.0.0.1:8072 accepted //github.com:443 [http -> proxy] 2024/02/02 18:48:42 127.0.0.1:8073 accepted //github.com:443 [http -> proxy]
2024/02/02 18:48:42 127.0.0.1:8072 accepted //github.com:443 [http -> proxy] 2024/02/02 18:48:42 127.0.0.1:8073 accepted //github.com:443 [http -> proxy]
2024/02/02 18:48:42 127.0.0.1:8072 accepted //github.com:443 [http -> proxy] 2024/02/02 18:48:42 127.0.0.1:8073 accepted //github.com:443 [http -> proxy]
4روزه دارم دنبال حل این میگردم ولی نتونستن حل کنم.وقتی از توی کلادفلر میام dns zone رو میزارم رو حالت proxied دیگه هیچ سایتی باز نمیضشه و همین پیام ها رو تکرار میکنه
I have this problem when I request local server, and I solved the problem by configure RouteSetting and add localhost to whitelist.