V2ray-core: windows平台下经常性的断联

Created on 22 Nov 2019  ·  15Comments  ·  Source: v2ray/v2ray-core

1) 你正在使用哪个版本的 V2Ray?(如果服务器和客户端使用了不同版本,请注明)
4.21.3

2) 你的使用场景是什么?比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。
chrome上google,github等。vmess普通tcp方式

3) 你看到的不正常的现象是什么?(请描述具体现象,比如访问超时,TLS 证书错误等)
windows平台下经常的断联,大约等待几秒,十几秒,几十毫秒不等,网络恢复正常。打开或者关闭mux都这样。安卓和mac平台正常

4) 你期待看到的正确表现是怎样的?
网络正常

5) 请附上你的配置(提交 Issue 前请隐藏服务器端IP地址)。

服务器端配置:

    // 在这里附上服务器端配置文件

客户端配置:

    // 在这里附上客户端配置

6) 请附上出错时软件输出的错误日志。在 Linux 中,日志通常在 /var/log/v2ray/error.log 文件中。

服务器端错误日志:

2019/11/22 14:27:48 [Info] [676483714] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:clients4.google.com:443
2019/11/22 14:27:50 [Info] v2ray.com/core/transport/internet/udp: failed to read UDP msg > read udp [::]:15881: use of closed network connection
2019/11/22 14:27:50 [Info] v2ray.com/core/transport/internet/udp: failed to read UDP msg > read udp [::]:17762: use of closed network connection
2019/11/22 14:27:50 [Info] v2ray.com/core/transport/internet/udp: listening UDP on 0.0.0.0:17154
2019/11/22 14:27:50 [Info] v2ray.com/core/transport/internet/kcp: listening on 0.0.0.0:17154
2019/11/22 14:27:50 [Info] v2ray.com/core/transport/internet/udp: listening UDP on 0.0.0.0:16758
2019/11/22 14:27:50 [Info] v2ray.com/core/transport/internet/kcp: listening on 0.0.0.0:16758
2019/11/22 14:27:59 [Info] [676483714] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/11/22 14:27:59 [Info] [676483714] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > context canceled
2019/11/22 14:29:19 [Info] [1112767519] v2ray.com/core/proxy/vmess/inbound: received request for tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [1112767519] v2ray.com/core/app/dispatcher: sniffed domain: proxy.duckduckgo.com
2019/11/22 14:29:19 [Info] [1112767519] v2ray.com/core/app/dispatcher: default route for tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [1112767519] v2ray.com/core/proxy/freedom: opening connection to tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [1112767519] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [942624993] v2ray.com/core/proxy/vmess/inbound: received request for tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [942624993] v2ray.com/core/app/dispatcher: sniffed domain: proxy.duckduckgo.com
2019/11/22 14:29:19 [Info] [942624993] v2ray.com/core/app/dispatcher: default route for tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [942624993] v2ray.com/core/proxy/freedom: opening connection to tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [942624993] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [3062979958] v2ray.com/core/proxy/vmess/inbound: received request for tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [3062979958] v2ray.com/core/app/dispatcher: sniffed domain: proxy.duckduckgo.com
2019/11/22 14:29:19 [Info] [3062979958] v2ray.com/core/app/dispatcher: default route for tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [3062979958] v2ray.com/core/proxy/freedom: opening connection to tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [3062979958] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [3588651303] v2ray.com/core/proxy/vmess/inbound: received request for tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [3588651303] v2ray.com/core/app/dispatcher: sniffed domain: proxy.duckduckgo.com
2019/11/22 14:29:19 [Info] [3588651303] v2ray.com/core/app/dispatcher: default route for tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [3588651303] v2ray.com/core/proxy/freedom: opening connection to tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [3588651303] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [511469490] v2ray.com/core/proxy/vmess/inbound: received request for tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [511469490] v2ray.com/core/app/dispatcher: sniffed domain: proxy.duckduckgo.com
2019/11/22 14:29:19 [Info] [511469490] v2ray.com/core/app/dispatcher: default route for tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [511469490] v2ray.com/core/proxy/freedom: opening connection to tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:19 [Info] [511469490] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:proxy.duckduckgo.com:443
2019/11/22 14:29:21 [Info] [1112767519] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/11/22 14:29:21 [Info] [1112767519] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > context canceled
2019/11/22 14:29:38 [Info] [2018084566] v2ray.com/core/proxy/vmess/inbound: received request for tcp:clients2.google.com:443
2019/11/22 14:29:38 [Info] [2018084566] v2ray.com/core/app/dispatcher: sniffed domain: clients2.google.com
2019/11/22 14:29:38 [Info] [2018084566] v2ray.com/core/app/dispatcher: default route for tcp:clients2.google.com:443
2019/11/22 14:29:38 [Info] [2018084566] v2ray.com/core/proxy/freedom: opening connection to tcp:clients2.google.com:443
2019/11/22 14:29:38 [Info] [2018084566] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:clients2.google.com:443
2019/11/22 14:30:16 [Info] [319876396] v2ray.com/core/proxy/vmess/inbound: received request for tcp:github.com:443
2019/11/22 14:30:16 [Info] [319876396] v2ray.com/core/app/dispatcher: sniffed domain: github.com
2019/11/22 14:30:16 [Info] [319876396] v2ray.com/core/app/dispatcher: default route for tcp:github.com:443
2019/11/22 14:30:16 [Info] [319876396] v2ray.com/core/proxy/freedom: opening connection to tcp:github.com:443
2019/11/22 14:30:16 [Info] [319876396] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:github.com:443
2019/11/22 14:30:17 [Info] [3588651303] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/11/22 14:30:17 [Info] [3588651303] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > io: read/write on closed pipe
2019/11/22 14:30:17 [Info] [511469490] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/11/22 14:30:17 [Info] [511469490] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > io: read/write on closed pipe
2019/11/22 14:30:17 [Info] [3062979958] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/11/22 14:30:17 [Info] [3062979958] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > io: read/write on closed pipe
2019/11/22 14:30:17 [Info] [2042610542] v2ray.com/core/proxy/vmess/inbound: received request for tcp:raw.githubusercontent.com:443
2019/11/22 14:30:17 [Info] [2042610542] v2ray.com/core/app/dispatcher: sniffed domain: raw.githubusercontent.com
2019/11/22 14:30:17 [Info] [2042610542] v2ray.com/core/app/dispatcher: default route for tcp:raw.githubusercontent.com:443
2019/11/22 14:30:17 [Info] [2042610542] v2ray.com/core/proxy/freedom: opening connection to tcp:raw.githubusercontent.com:443
2019/11/22 14:30:17 [Info] [2042610542] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:raw.githubusercontent.com:443
2019/11/22 14:30:18 [Info] [2927995269] v2ray.com/core/proxy/vmess/inbound: received request for tcp:github.com:443
2019/11/22 14:30:18 [Info] [2927995269] v2ray.com/core/app/dispatcher: sniffed domain: github.com
2019/11/22 14:30:18 [Info] [2927995269] v2ray.com/core/app/dispatcher: default route for tcp:github.com:443
2019/11/22 14:30:18 [Info] [2927995269] v2ray.com/core/proxy/freedom: opening connection to tcp:github.com:443
2019/11/22 14:30:18 [Info] [2927995269] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:github.com:443
2019/11/22 14:30:18 [Info] [1914065185] v2ray.com/core/proxy/vmess/inbound: received request for tcp:github.com:443
2019/11/22 14:30:18 [Info] [1914065185] v2ray.com/core/app/dispatcher: sniffed domain: github.com
2019/11/22 14:30:18 [Info] [1914065185] v2ray.com/core/app/dispatcher: default route for tcp:github.com:443
2019/11/22 14:30:18 [Info] [1914065185] v2ray.com/core/proxy/freedom: opening connection to tcp:github.com:443
2019/11/22 14:30:18 [Info] [1914065185] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:github.com:443
2019/11/22 14:30:18 [Info] [3036190727] v2ray.com/core/proxy/vmess/inbound: received request for tcp:live.github.com:443
2019/11/22 14:30:18 [Info] [3036190727] v2ray.com/core/app/dispatcher: sniffed domain: live.github.com
2019/11/22 14:30:18 [Info] [3036190727] v2ray.com/core/app/dispatcher: default route for tcp:live.github.com:443
2019/11/22 14:30:18 [Info] [3036190727] v2ray.com/core/proxy/freedom: opening connection to tcp:live.github.com:443
2019/11/22 14:30:18 [Info] [3036190727] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:live.github.com:443
2019/11/22 14:30:18 [Info] [533845205] v2ray.com/core/proxy/vmess/inbound: received request for tcp:github.com:443
2019/11/22 14:30:18 [Info] [533845205] v2ray.com/core/app/dispatcher: sniffed domain: github.com
2019/11/22 14:30:18 [Info] [533845205] v2ray.com/core/app/dispatcher: default route for tcp:github.com:443
2019/11/22 14:30:18 [Info] [533845205] v2ray.com/core/proxy/freedom: opening connection to tcp:github.com:443
2019/11/22 14:30:18 [Info] [533845205] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:github.com:443
2019/11/22 14:30:18 [Info] [3830798745] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/11/22 14:30:18 [Info] [3830798745] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > context canceled
2019/11/22 14:30:20 [Info] [2927995269] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/11/22 14:30:20 [Info] [2927995269] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > io: read/write on closed pipe
2019/11/22 14:30:30 [Info] [533845205] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/11/22 14:30:30 [Info] [533845205] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > io: read/write on closed pipe

客户端错误日志:
日志级别为warn时无错误输出,info级别时每次断联就会有如下输出

  2019/11/22 13:31:49 [Info] [3105456332] v2ray.com/core/app/dispatcher: default route for tcp:github.com:443
2019/11/22 13:31:49 [Info] [3105456332] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:xxx.xxx.xxx
2019/11/22 13:31:50 [Info] [3105456332] v2ray.com/core/proxy/vmess/outbound: tunneling request to tcp:github.com:443 via xxx.xx:xxx
2019/11/22 13:31:57 [Info] [3644259039] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > read tcp 192.168.1.230:14824->xxxx:3333: 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.
2019/11/22 13:31:57 [Info] [3644259039] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > v2ray.com/core/proxy/socks: failed to transport all TCP response > io: read/write on closed pipe

7) 请附上访问日志。在 Linux 中,日志通常在 /var/log/v2ray/access.log 文件中。
服务端访问日志偶尔会有这种invalid user的情况。

 2019/11/22 14:46:27 220.191.186.194:56843 accepted tcp:adservice.google.com:443 
2019/11/22 14:46:40 220.191.186.194:56846 accepted tcp:adservice.google.com:443 
2019/11/22 14:46:51 220.191.186.194:56854 accepted tcp:clients2.google.com:443 
2019/11/22 14:46:52 220.191.186.194:56857 accepted tcp:adservice.google.com:443 
2019/11/22 14:47:01 222.94.212.93:56436 rejected  v2ray.com/core/proxy/vmess/encoding: invalid user
2019/11/22 14:47:03 180.95.238.48:57326 rejected  v2ray.com/core/proxy/vmess/encoding: invalid user
2019/11/22 14:47:03 180.95.238.48:57424 rejected  v2ray.com/core/proxy/vmess/encoding: invalid user
2019/11/22 14:47:03 180.95.238.48:57814 rejected  v2ray.com/core/proxy/vmess/encoding: invalid user
2019/11/22 14:47:04 220.191.186.194:56861 accepted tcp:adservice.google.com:443 
2019/11/22 14:47:11 220.191.186.194:56863 accepted tcp:mtalk.google.com:5228 
2019/11/22 14:47:15 220.191.186.194:56866 accepted tcp:adservice.google.com:443 
2019/11/22 14:47:27 220.191.186.194:56868 accepted tcp:adservice.google.com:443 
Need Config

Most helpful comment

这几天同样出现类似问题,不稳定,且流量一大就断,过一会又可以Ping通。我把传输协议换成kcp后,好像就正常了

All 15 comments

以前一直十分稳定,且没有做过任何配置改动,最近2天遇到同样的问题。主机ip有时可以ping的通,有时不行;SSH也一样经常断。如果传输大流量(如视频),似乎断的更快。我在想是不是墙升级了。。。现在正申请个CDN试试。

以前一直十分稳定,且没有做过任何配置改动,最近2天遇到同样的问题。主机ip有时可以ping的通,有时不行;SSH也一样经常断。如果传输大流量(如视频),似乎断的更快。我在想是不是墙升级了。。。现在正申请个CDN试试。

我的可以ping通,ssh上

这几天同样出现类似问题,不稳定,且流量一大就断,过一会又可以Ping通。我把传输协议换成kcp后,好像就正常了

这几天同样出现类似问题,不稳定,且流量一大就断,过一会又可以Ping通。我把传输协议换成kcp后,好像就正常了

请问是如何设置呀? 我这里也是同样问题

这几天同样出现类似问题,不稳定,且流量一大就断,过一会又可以Ping通。我把传输协议换成kcp后,好像就正常了

感谢。我仔细琢磨了一下技术文档,也改了一下配置,确实可以上了,效果真是立竿见影(目前尝试了半个钟头尚未断开,之前不到5分钟就断),而且速度还提高不少,看720p视频无压力。唉,早知道能提速这么多,我也不等到今天才改了,白白浪费了之前每个月几百GB的主机流量。人呐,就是死到临头才有动力做出改变。。。

不过实在感觉有点奇怪,该不会是mkcp的伪装功能起作用了吧?也不知道这种能撑多久。。。看来还是要储备点CDN的技术才行,这墙我估计是真的升级了。

这几天同样出现类似问题,不稳定,且流量一大就断,过一会又可以Ping通。我把传输协议换成kcp后,好像就正常了

请问是如何设置呀? 我这里也是同样问题

参照这个教程配置即可:
https://guide.v2fly.org/advanced/mkcp.html#%E5%AE%A2%E6%88%B7%E7%AB%AF%E9%85%8D%E7%BD%AE

(streamSettings里的type改成utp;downlinkCapacity固定填100;uplinkCapacity按需填写,填的越大网速越快,但消耗宽带越猛,一般填网速*2~3,注意这里单位是MB而不是Mb;其他的配置就保持你之前的就可以了)

这几天同样出现类似问题,不稳定,且流量一大就断,过一会又可以Ping通。我把传输协议换成kcp后,好像就正常了

请问是如何设置呀? 我这里也是同样问题

参照这个教程配置即可:
https://guide.v2fly.org/advanced/mkcp.html#%E5%AE%A2%E6%88%B7%E7%AB%AF%E9%85%8D%E7%BD%AE
(streamSettings里的type改成utp;downlinkCapacity固定填100;uplinkCapacity按需填写,填的越大网速越快,但消耗宽带越猛,一般填网速*2~3,注意这里单位是MB而不是Mb;其他的配置就保持你之前的就可以了)

感谢分享!!!谢谢

应该是运营商QOS的结果,尝试进行伪装,用kcp确实是个不错的办法

这几天同样出现类似问题,不稳定,且流量一大就断,过一会又可以Ping通。我把传输协议换成kcp后,好像就正常了

那应该是你被运营商tcp阻断了,运营商qos,换了kcp用的是udp协议,你们当地暂时udp没有被阻断

@kslr
客户端配置

{
  "policy": null,
  "log": {
    "access": "",
    "error": "",
    "loglevel": "warning"
  },
  "inbounds": [
    {
      "tag": "proxy",
      "port": 1080,
      "listen": "0.0.0.0",
      "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": "domain.com",
            "port": 888,
            "users": [
              {
                "id": "uuid",
                "alterId": 88,
                "email": "[email protected]",
                "security": "aes-128-gcm"
              }
            ]
          }
        ],
        "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": {
    "servers": [
      "223.5.5.5",
      "8.8.8.8",
      "1.1.1.1"
    ]
  },
  "routing": {
    "domainStrategy": "IPIfNonMatch",
    "rules": [
      {
        "type": "field",
        "port": null,
        "inboundTag": [
          "api"
        ],
        "outboundTag": "api",
        "ip": null,
        "domain": null
      }
    ]
  }
}

服务端配置

{
    "log": {
        "access": "/var/log/v2ray/access.log",
        "error": "/var/log/v2ray/error.log",
        "loglevel": "warn"
    },
    "inbounds": [
        {
            "port": 888,
            "protocol": "vmess",
            "settings": {
                "clients": [
                    {
                        "id": "uuid",
                        "alterId": 88
                    }
                ]
            },
            "streamSettings": {
                "network": "tcp"
            },
            "sniffing": {
                "enabled": true,
                "destOverride": [
                    "http",
                    "tls"
                ]
            }
        }
    ],
    "outbounds": [
        {
            "protocol": "freedom",
            "settings": {}
        },
        {
            "protocol": "blackhole",
            "settings": {},
            "tag": "blocked"
        },
        {
            "protocol": "freedom",
            "settings": {},
            "tag": "direct"
        },
        {
            "protocol": "mtproto",
            "settings": {},
            "tag": "tg-out"
        }
    ],
    "dns": {
        "server": [
            "1.1.1.1",
            "1.0.0.1",
            "8.8.8.8",
            "8.8.4.4",
            "localhost"
        ]
    },
    "routing": {
        "domainStrategy": "IPOnDemand",
        "rules": [
            {
                "type": "field",
                "inboundTag": [
                    "tg-in"
                ],
                "outboundTag": "tg-out"
            },
            {
                "type": "field",
                "protocol": [
                    "bittorrent"
                ],
                "outboundTag": "blocked"
            }
        ]
    },
    "transport": {
        "kcpSettings": {
            "uplinkCapacity": 100,
            "downlinkCapacity": 100,
            "congestion": true
        },
        "sockopt": {
            "tcpFastOpen": true
        }
    }
}

升级方案吧

升级方案吧

@kslr 请问有推荐的配置方案吗

升级方案吧
同问推荐方案

持续期待中,

Was this page helpful?
0 / 5 - 0 ratings