同时同一个VPS，手机安卓客户端v2rayNG正常上网，而windows 客户端不能

[jedysword]

在提出问题前请先自行排除服务器端问题，同时也请通过搜索确认是否有人提出过相同问题。

### 预期行为 手机客户端和windows客户端版本都是最新的，VPS使用的是GCP VPS，稳定性一直没的说，服务器端配置了两种协议vmess和shadowsocks，windows和手机客户端都应该能正常科学上网才对，

### 实际行为 从开通以来一直存在手机客户端正常上网而windows客户端不行的情况，今天把core版本和客户端版本都更新到V4.21.0还是一样的问题，同时发现手机客户端vmess和shadowsocks都能上，但是windows客户端vmess还是不能用，但是使用shadowssocks协议可以，

### 复现方法### 1.升级V2ray版本 2.重启V2RAY服务器端和客户端 3.修改windows客户端的配置 以上方法都试过了，都是同样的结果。

### 服务器端的日志如下### 以下地址61.150.104.83是windows客户端的外网地址，从日志来看访问已经到达服务器端，但是有如下的错误发生 root@instance-group-1-k702:/var/log/v2ray# tail -10 access.log 2019/10/27 04:30:48 61.150.104.83:56050 rejected v2ray.com/core/proxy/vmess/encoding: failed to read request header > read tcp 10.170.0.12:25->61.150.104.83:56050: i/o timeout 2019/10/27 04:30:52 61.150.104.83:56057 rejected v2ray.com/core/proxy/vmess/encoding: failed to read request header > read tcp 10.170.0.12:25->61.150.104.83:56057: i/o timeout 2019/10/27 04:30:58 61.150.104.83:56066 rejected v2ray.com/core/proxy/vmess/encoding: failed to read request header > read tcp 10.170.0.12:25->61.150.104.83:56066: i/o timeout 2019/10/27 04:31:04 61.150.104.83:56074 rejected v2ray.com/core/proxy/vmess/encoding: failed to read request header > read tcp 10.170.0.12:25->61.150.104.83:56074: i/o timeout 2019/10/27 04:31:09 61.150.104.83:56084 rejected v2ray.com/core/proxy/vmess/encoding: failed to read request header > read tcp 10.170.0.12:25->61.150.104.83:56084: i/o timeout 2019/10/27 04:31:14 61.150.104.83:56097 rejected v2ray.com/core/proxy/vmess/encoding: failed to read request header > read tcp 10.170.0.12:25->61.150.104.83:56097: i/o timeout 2019/10/27 04:31:20 61.150.104.83:56110 rejected v2ray.com/core/proxy/vmess/encoding: failed to read request header > read tcp 10.170.0.12:25->61.150.104.83:56110: i/o timeout 2019/10/27 04:31:25 61.150.104.83:56118 rejected v2ray.com/core/proxy/vmess/encoding: failed to read request header > read tcp 10.170.0.12:25->61.150.104.83:56118: i/o timeout 2019/10/27 04:31:30 61.150.104.83:56129 rejected v2ray.com/core/proxy/vmess/encoding: failed to read request header > read tcp 10.170.0.12:25->61.150.104.83:56129: i/o timeout 2019/10/27 04:31:35 61.150.104.83:56137 rejected v2ray.com/core/proxy/vmess/encoding: failed to read request header > read tcp 10.170.0.12:25->61.150.104.83:56137: i/o timeout

###windows客户端的日志如下### 2019/10/27 12:30:47 [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 > read tcp 127.0.0.1:56049->0.0.0.0（地址马赛克处理）: wsarecv: An existing connection was forcibly closed by the remote host. 2019/10/27 12:30:48 tcp:127.0.0.1:56055 accepted tcp:beacons.gcp.gvt2.com:443 2019/10/27 12:30:49 tcp:127.0.0.1:56060 accepted tcp:beacons2.gvt2.com:443 2019/10/27 12:30:51 tcp:127.0.0.1:56062 accepted tcp:beacons.gcp.gvt2.com:443 2019/10/27 12:30:52 [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 > read tcp 127.0.0.1:56056->0.0.0.0（地址马赛克处理）: wsarecv: An existing connection was forcibly closed by the remote host. 2019/10/27 12:30:53 tcp:127.0.0.1:56064 accepted tcp:beacons.gvt2.com:443 2019/10/27 12:30:53 tcp:127.0.0.1:56068 accepted tcp:beacons.gcp.gvt2.com:443 2019/10/27 12:30:58 [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 > read tcp 127.0.0.1:56065->0.0.0.0（地址马赛克处理）: wsarecv: An existing connection was forcibly closed by the remote host. 2019/10/27 12:30:59 tcp:127.0.0.1:56071 accepted tcp:beacons2.gvt2.com:443 2019/10/27 12:30:59 tcp:127.0.0.1:56072 accepted tcp:beacons.gvt2.com:443 2019/10/27 12:31:00 tcp:127.0.0.1:56076 accepted tcp:beacons.gvt2.com:443 2019/10/27 12:31:01 tcp:127.0.0.1:56078 accepted tcp:beacons4.gvt2.com:443 2019/10/27 12:31:04 [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 > read tcp 127.0.0.1:56073->0.0.0.0（地址马赛克处理）: wsarecv: An existing connection was forcibly closed by the remote host. 2019/10/27 12:31:05 tcp:127.0.0.1:56080 accepted tcp:beacons3.gvt2.com:443 2019/10/27 12:31:05 tcp:127.0.0.1:56082 accepted tcp:beacons3.gvt2.com:443 2019/10/27 12:31:06 tcp:127.0.0.1:56086 accepted tcp:beacons2.gvt2.com:443 2019/10/27 12:31:08 tcp:127.0.0.1:56089 accepted tcp:beacons2.gvt2.com:443 2019/10/27 12:31:09 [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 > read tcp 127.0.0.1:56083->0.0.0.0（地址马赛克处理）: wsarecv: An existing connection was forcibly closed by the remote host. 2019/10/27 12:31:10 tcp:127.0.0.1:56091 accepted tcp:beacons4.gvt2.com:443 2019/10/27 12:31:10 tcp:127.0.0.1:56094 accepted tcp:beacons5.gvt2.com:443 2019/10/27 12:31:10 tcp:127.0.0.1:56095 accepted tcp:beacons3.gvt2.com:443 2019/10/27 12:31:13 tcp:127.0.0.1:56099 accepted tcp:beacons3.gvt2.com:443 2019/10/27 12:31:14 [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 > read tcp 127.0.0.1:56096->0.0.0.0（地址马赛克处理）: wsarecv: An existing connection was forcibly closed by the remote host. 2019/10/27 12:31:15 tcp:127.0.0.1:56102 accepted tcp:clients2.google.com:443 2019/10/27 12:31:15 tcp:127.0.0.1:56106 accepted tcp:beacons4.gvt2.com:443 2019/10/27 12:31:15 tcp:127.0.0.1:56107 accepted tcp:beacons5.gvt2.com:443 2019/10/27 12:31:15 tcp:127.0.0.1:56108 accepted tcp:beacons5.gvt2.com:443 2019/10/27 12:31:19 [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 > read tcp 127.0.0.1:56109->0.0.0.0（地址马赛克处理）: wsarecv: An existing connection was forcibly closed by the remote host. 2019/10/27 12:31:20 tcp:127.0.0.1:56113 accepted tcp:beacons5.gvt3.com:443 2019/10/27 12:31:20 tcp:127.0.0.1:56117 accepted tcp:beacons4.gvt2.com:443 2019/10/27 12:31:20 tcp:127.0.0.1:56119 accepted tcp:beacons5.gvt3.com:443 2019/10/27 12:31:23 tcp:127.0.0.1:56121 accepted tcp:beacons5.gvt2.com:443 2019/10/27 12:31:25 [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 > read tcp 127.0.0.1:56116->0.0.0.0（地址马赛克处理）: wsarecv: An existing connection was forcibly closed by the remote host. 2019/10/27 12:31:26 tcp:127.0.0.1:56125 accepted tcp:clients2.google.com:443 2019/10/27 12:31:26 tcp:127.0.0.1:56127 accepted tcp:beacons5.gvt3.com:443 2019/10/27 12:31:26 tcp:127.0.0.1:56131 accepted tcp:beacons5.gvt3.com:443 2019/10/27 12:31:30 [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 > read tcp 127.0.0.1:56128->0.0.0.0（地址马赛克处理）: wsarecv: An existing connection was forcibly closed by the remote host. 2019/10/27 12:31:31 tcp:127.0.0.1:56135 accepted tcp:clients2.google.com:443 2019/10/27 12:31:31 tcp:127.0.0.1:56139 accepted tcp:clients2.google.com:443 2019/10/27 12:31:35 [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 > read tcp 127.0.0.1:56136->0.0.0.0（地址马赛克处理）:25: wsarecv: An existing connection was forcibly closed by the remote host.

###服务器端的配置文件信息### { "log": { "loglevel": "warning", "access": "/var/log/v2ray/access.log", "error": "/var/log/v2ray/error.log" }, "inbounds": [ { "port": 25, "protocol": "vmess", "settings": { "clients": [ { "id": "decd2ce4-7f4a-49c9-a8df-9e20d604728", "level": 1, "alterId": 64 } ] } }, { "port": 64007, "protocol": "shadowsocks", "settings": { "method": "aes-256-cfb", "password": "mimamimamimamima" } } ], "outbounds": [{ "protocol": "freedom", "settings": {} },{ "protocol": "blackhole", "settings": {}, "tag": "blocked" }], "routing": { "rules": [ { "type": "field", "ip": ["geoip:private"], "outboundTag": "blocked" } ] } }

###客户端的配置文件信息### { "policy": null, "log": { "access": "", "error": "", "loglevel": "warning" }, "inbounds": [ { "tag": "proxy", "port": 10808, "listen": "127.0.0.1", "protocol": "socks", "sniffing": { "enabled": true, "destOverride": [ "http", "tls" ] }, "settings": { "auth": "noauth", "udp": true, "ip": null, "address": null, "clients": null }, "streamSettings": null } ], "outbounds": [ { "tag": "proxy", "protocol": "vmess", "settings": { "vnext": [ { "address": "0.0.0.0", //地址打马赛克 "port": 25, "users": [ { "id": "decd2ce4-7f4a-49c9-a8df-9e20d604728", "alterId": 4, "email": "t@t.tt", "security": "auto" } ] } ], "servers": null, "response": null }, "streamSettings": { "network": "tcp", "security": null, "tlsSettings": null, "tcpSettings": null, "kcpSettings": null, "wsSettings": null, "httpSettings": null, "quicSettings": null }, "mux": { "enabled": false } }, { "tag": "direct", "protocol": "freedom", "settings": { "vnext": null, "servers": null, "response": null }, "streamSettings": null, "mux": null }, { "tag": "block", "protocol": "blackhole", "settings": { "vnext": null, "servers": null, "response": { "type": "http" } }, "streamSettings": null, "mux": null } ], "stats": null, "api": null, "dns": null, "routing": { "domainStrategy": "IPIfNonMatch", "rules": [ { "type": "field", "port": null, "inboundTag": "api", "outboundTag": "api", "ip": null, "domain": null } ] } }

[mrWhiteBai]

同问。。。。。。

[jedysword]

问题已经自己解决了 今天又试验了n次，发现了问题所在，我在windows客户端设置的vmess outbound端口号25有问题，我估计是此端口和windows什么地方冲突造成的，我后来把端口改成30000以后的端口就好了。 但是确实，同样的25号端口，在安卓手机上没问题。

[jedysword]

同问。。。。。。

看我上面的解决方法，应该是端口号设置问题，端口和windows系统冲突等等。。。

[mrWhiteBai]

我的端口号是58315.。。。。。。 在另一个windows10里面能用，在当前win10中就不可用 这是客户端测试网速和真延迟时的日志 --------------------------------远程服务器返回错误: (503) 服务器不可用。[14:37:48]-------------------------------- System.Net.WebException: 远程服务器返回错误: (503) 服务器不可用。 在 v2rayN.Handler.DownloadHandle.ws_DownloadFileCompleted(Object sender, AsyncCompletedEventArgs e)

--------------------------------基础连接已经关闭: 发送时发生错误。[14:38:00]-------------------------------- System.Net.WebException: 基础连接已经关闭: 发送时发生错误。 ---> System.IO.IOException: 由于远程方已关闭传输流，身份验证失败。 在 System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) 在 System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) 在 System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) 在 System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) 在 System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) 在 System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) 在 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) 在 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) 在 System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) 在 System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) 在 System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) 在 System.Net.ConnectStream.WriteHeaders(Boolean async) --- 内部异常堆栈跟踪的结尾 --- 在 System.Net.HttpWebRequest.GetResponse() 在 v2rayN.Handler.SpeedtestHandler.GetRealPingTime(String url, WebProxy webProxy, Int32& responseTime)

[2dust]

N只是一个GUI

[mrWhiteBai]

N只是一个GUI

然后呢，应该怎么办呢，小白看不懂

[jedysword]

N只是一个GUI

然后呢，应该怎么办呢，小白看不懂

意思是到V2ray core提问题，是啊，说的没错，你把问题提到https://github.com/v2ray/v2ray-core这里吧

[ly-000]

问题已经自己解决了 今天又试验了n次，发现了问题所在，我在windows客户端设置的vmess outbound端口号25有问题，我估计是此端口和windows什么地方冲突造成的，我后来把端口改成30000以后的端口就好了。 但是确实，同样的25号端口，在安卓手机上没问题。

老哥请问这个windows客户端vmess outbound端口要在哪儿更改呢，我也是隔几天就出现一次这样的问题，之前是改电脑的代理设置能好，现在是怎么都不行了。VPS应该没问题，手机端可以用，别的windows机器也可以用。谢谢！

[Z-siwu]

我的原因是 之前开启过IPv6，导致无法连接成功

解决方案： 运行cmd（管理员权限），卸载当前 Teredo 适配器再重新启用

netsh interface Teredo set state disable netsh interface Teredo set state type=default

[Forest-Lee]

我的原因是 之前开启过IPv6，导致无法连接成功

解决方案： 运行cmd（管理员权限），卸载当前 Teredo 适配器再重新启用

netsh interface Teredo set state disable netsh interface Teredo set state type=default

试过了，依旧是503