mac系统使用v2ray v3.13 ws+ssl+header分流断流现象严重 #957

man2018 · 2018-03-13T03:33:34Z

中文：
提交 Issue 之前请先阅读 Issue 指引，然后回答下面的问题，谢谢。
除非特殊情况，请完整填写所有问题。不按模板发的 issue 将直接被关闭。

你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明）
服务器端：v2ray v3.13
mac端：v2ray-core-masos v3.13
你的使用场景是什么？比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。
我主要是用来socks5代理使用mail客户端收发邮件，配合proxifier，也通过浏览器翻墙，看视频等日常行为
你看到的不正常的现象是什么？（请描述具体现象，比如访问超时，TLS 证书错误等）
mac系统是osx 10.13.3 64位，目前我是前台网站+后台v2ray隐藏+ssl证书+header分流。现在是使用一段时间后会出现无法ping现象，此时也无法上网（有时候我是直接把mac电脑合盖休眠，过几个小时再打开也会出现此问题），我重启mac电脑一般就能解决问题。同样的vps里面也装了ss刚没有此问题。
你期待看到的正确表现是怎样的？
希望24小时持续不间断
请附上你的配置（提交 Issue 前请隐藏服务器端IP地址）。

服务器端配置:

    // 在这里附上服务器端配置文件
```{
    "log": {
        "access": "/var/log/v2ray/access.log",
        "error": "/var/log/v2ray/error.log",
        "loglevel": "warning"
    },
    "inbound": {
	"listen": "127.0.0.1",
        "port": 419,
        "protocol": "vmess",
        "settings": {
            "udp": true,
            "clients": [
                {
                    "id": "19e23d80-3a4d-4277-b37b-79d5d8456f95",
                    "level": 1,
                    "alterId": 64
                }
            ]
        },
        "streamSettings": {
            "network": "ws",
            "security": "auto",
            "wsSettings": {
            "connectionReuse": true,
            "path": "/",
            "headers": {
            "Host": "www.dkldfdj.com"
            }
            }
            }
    },
    "outbound": {
        "protocol": "freedom",
        "settings": {}
    },
    "outboundDetour": [
        {
            "protocol": "blackhole",
            "settings": {},
            "tag": "blocked"
        }
    ],
    "routing": {
        "strategy": "rules",
        "settings": {
            "rules": [
                {
                    "type": "field",
                    "ip": [
                        "0.0.0.0/8",
                        "10.0.0.0/8",
                        "100.64.0.0/10",
                        "127.0.0.0/8",
                        "169.254.0.0/16",
                        "172.16.0.0/12",
                        "192.0.0.0/24",
                        "192.0.2.0/24",
                        "192.168.0.0/16",
                        "198.18.0.0/15",
                        "198.51.100.0/24",
                        "203.0.113.0/24",
                        "::1/128",
                        "fc00::/7",
                        "fe80::/10"
                    ],
                    "outboundTag": "blocked"
                }
            ]
        }
    }
}


    客户端配置:
```javascript
    // 在这里附上客户端配置
```{
  "inbound": {
    "port": 1080,
    "listen": "0.0.0.0",
    "protocol": "socks",
    "settings": {
      "auth": "noauth",
      "udp": true,
      "ip": "127.0.0.1",
      "clients": null
    },
    "streamSettings": null
  },
  "outbound": {
    "tag": "agentout",
    "protocol": "vmess",
    "settings": {
      "vnext": [
        {
          "address": "www.xxxx.com",
          "port": 443,
          "users": [
            {
              "id": "19e23d80-3a4d-4277-b37b-xxxxxxxxxx",
              "alterId": 64,
              "security": "chacha20-poly1305"
            }
          ]
        }
      ]
    },
    "streamSettings": {
      "network": "ws",
      "security": "tls",
      "tcpSettings": null,
      "kcpSettings": null,
      "wsSettings": {
        "connectionReuse": true,
        "path": "/",
        "headers": {
          "Host": "www.dkldfdj.com"
        }
      }
    },
    "mux": {
      "enabled": true
    }
  },
  "inboundDetour": null,
  "outboundDetour": [
    {
      "protocol": "freedom",
      "settings": {
        "response": null
      },
      "tag": "direct"
    },
    {
      "protocol": "blackhole",
      "settings": {
        "response": {
          "type": "http"
        }
      },
      "tag": "blockout"
    }
  ],
  "dns": {
    "servers": [
      "8.8.8.8",
      "8.8.4.4",
      "localhost"
    ]
  },
  "routing": {
    "strategy": "rules",
    "settings": {
      "domainStrategy": "IPIfNonMatch",
      "rules": [
        {
          "type": "field",
          "port": null,
          "outboundTag": "direct",
          "ip": [
            "0.0.0.0/8",
            "10.0.0.0/8",
            "100.64.0.0/10",
            "127.0.0.0/8",
            "169.254.0.0/16",
            "172.16.0.0/12",
            "192.0.0.0/24",
            "192.0.2.0/24",
            "192.168.0.0/16",
            "198.18.0.0/15",
            "198.51.100.0/24",
            "203.0.113.0/24",
            "::1/128",
            "fc00::/7",
            "fe80::/10"
          ],
          "domain": null
        },
        {
          "type": "field",
          "port": null,
          "outboundTag": "direct",
          "ip": null,
          "domain": [
            "geosite:cn"
          ]
        },
        {
          "type": "field",
          "port": null,
          "outboundTag": "direct",
          "ip": [
            "geoip:cn"
          ],
          "domain": null
        }
      ]
    }
  }
}

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

    服务器端错误日志:

// 在这里附上服务器端日志

2018/03/10 19:39:49 [Warning] Core: V2Ray v3.13 started
2018/03/10 19:40:30 [Warning] Transport|Internet|WebSocket: failed to serve http for WebSocket > accept tcp 127.0.0.1:419: use of closed network connection
2018/03/10 19:40:30 [Warning] Core: V2Ray v3.13 started

    客户端错误日志:
```客户端我没有设置日志
    // 在这里附上客户端日志

请附上访问日志。在 Linux 中，日志通常在 /var/log/v2ray/access.log 文件中。

    // 在这里附上服务器端日志
```2018/03/13 10:27:25 127.0.0.1:43894 accepted tcp:v1.mux.cool:0 
2018/03/13 10:30:53 127.0.0.1:44034 accepted tcp:v1.mux.cool:9527 
2018/03/13 10:30:57 127.0.0.1:44048 rejected  Proxy|VMess|Encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2018/03/13 10:30:58 127.0.0.1:44042 rejected  Proxy|VMess|Encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2018/03/13 10:30:58 127.0.0.1:44046 rejected  Proxy|VMess|Encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2018/03/13 10:30:58 127.0.0.1:44040 rejected  Proxy|VMess|Encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2018/03/13 10:30:58 127.0.0.1:44044 accepted tcp:v1.mux.cool:0 
2018/03/13 10:32:06 127.0.0.1:44116 accepted tcp:v1.mux.cool:0 
2018/03/13 10:32:06 127.0.0.1:44120 accepted tcp:v1.mux.cool:0 
2018/03/13 10:32:06 127.0.0.1:44112 accepted tcp:v1.mux.cool:0 
2018/03/13 10:32:06 127.0.0.1:44118 accepted tcp:v1.mux.cool:0 
2018/03/13 10:32:06 127.0.0.1:44114 accepted tcp:v1.mux.cool:0 
2018/03/13 10:32:15 127.0.0.1:44308 accepted tcp:v1.mux.cool:9527 
2018/03/13 10:32:33 127.0.0.1:44426 accepted tcp:v1.mux.cool:0 
2018/03/13 10:34:29 127.0.0.1:44634 accepted tcp:v1.mux.cool:0 
2018/03/13 10:34:47 127.0.0.1:44672 rejected  Proxy|VMess|Encoding: failed to read request header > read tcp 127.0.0.1:419->127.0.0.1:44672: i/o timeout
2018/03/13 10:35:36 127.0.0.1:44790 rejected  Proxy|VMess|Encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2018/03/13 10:35:36 127.0.0.1:44792 rejected  Proxy|VMess|Encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2018/03/13 10:35:37 127.0.0.1:44788 rejected  Proxy|VMess|Encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2018/03/13 10:35:44 127.0.0.1:44814 rejected  Proxy|VMess|Encoding: failed to read request header > read tcp 127.0.0.1:419->127.0.0.1:44814: i/o timeout
2018/03/13 10:35:44 127.0.0.1:44816 rejected  Proxy|VMess|Encoding: failed to read request header > read tcp 127.0.0.1:419->127.0.0.1:44816: i/o timeout
2018/03/13 10:35:44 127.0.0.1:44818 rejected  Proxy|VMess|Encoding: failed to read request header > read tcp 127.0.0.1:419->127.0.0.1:44818: i/o timeout
2018/03/13 10:35:44 127.0.0.1:44820 rejected  Proxy|VMess|Encoding: failed to read request header > read tcp 127.0.0.1:419->127.0.0.1:44820: i/o timeout
2018/03/13 10:35:48 127.0.0.1:44848 accepted tcp:v1.mux.cool:0 
2018/03/13 10:35:48 127.0.0.1:44846 accepted tcp:v1.mux.cool:0 

8) 其它相关的配置文件（如 Nginx）和相关日志。
2018/01/20 12:14:01 [notice] 3234#0: signal process started
2018/01/20 12:15:37 [notice] 4345#0: signal process started
2018/01/20 12:27:32 [emerg] 4783#0: "client_max_body_size" directive is duplicate in /usr/local/nginx/conf/vhost/www.xxxx.com.conf:45
2018/01/20 18:08:22 [notice] 7541#0: signal process started
2018/01/20 18:14:49 [notice] 8245#0: signal process started
2018/01/20 18:22:45 [notice] 9004#0: signal process started
2018/01/20 18:26:56 [notice] 9705#0: signal process started
2018/01/20 19:18:38 [notice] 10874#0: signal process started
2018/01/20 20:07:03 [notice] 11274#0: signal process started
2018/01/20 22:16:58 [emerg] 12485#0: "client_max_body_size" directive is duplicate in /usr/local/nginx/conf/vhost/www.xxxx.com.conf:67
2018/01/20 22:18:17 [notice] 12516#0: signal process started
2018/01/20 22:18:27 [notice] 12524#0: signal process started
2018/01/20 23:27:49 [notice] 15918#0: signal process started
2018/01/20 23:43:33 [notice] 16613#0: signal process started
2018/01/20 23:55:39 [notice] 16914#0: signal process started
2018/01/21 08:50:23 [notice] 22509#0: signal process started
2018/01/21 09:06:44 [notice] 22768#0: signal process started
2018/01/21 10:52:17 [emerg] 23996#0: invalid port in upstream "127.0.0.1:<10000>" in /usr/local/nginx/conf/vhost/www.xxxx.com.conf:8
2018/01/21 10:56:19 [emerg] 24017#0: invalid port in upstream "127.0.0.1:<10000>" in /usr/local/nginx/conf/vhost/www.xxxx.com.conf:8
2018/01/21 11:07:47 [notice] 24164#0: signal process started
2018/01/21 11:07:47 [error] 24164#0: invalid PID number "" in "/usr/local/nginx/logs/nginx.pid"
2018/01/21 11:08:48 [notice] 24183#0: signal process started
2018/01/21 11:08:48 [error] 24183#0: invalid PID number "" in "/usr/local/nginx/logs/nginx.pid"
2018/01/21 11:10:19 [notice] 2447#0: signal process started
2018/01/21 11:22:33 [emerg] 2690#0: "server" directive is not allowed here in /usr/local/nginx/conf/nginx.conf:62
2018/01/21 11:31:02 [notice] 2814#0: signal process started
2018/01/21 11:35:56 [notice] 2908#0: signal process started
2018/01/21 11:39:33 [notice] 3058#0: signal process started
2018/01/21 11:51:37 [notice] 3126#0: signal process started
2018/01/21 11:56:49 [notice] 3172#0: signal process started
2018/01/21 12:11:26 [emerg] 3263#0: "client_max_body_size" directive is duplicate in /usr/local/nginx/conf/vhost/www.xxxx.com.conf:46
2018/01/21 12:12:05 [notice] 3274#0: signal process started
2018/01/21 12:44:02 [notice] 3525#0: signal process started
2018/01/21 13:52:04 [notice] 4714#0: signal process started
2018/01/21 13:56:06 [notice] 4743#0: signal process started
2018/01/21 13:57:41 [notice] 4762#0: signal process started
2018/01/21 14:00:50 [notice] 4784#0: signal process started
2018/01/21 14:04:32 [notice] 4810#0: signal process started
2018/01/21 14:22:24 [notice] 4914#0: signal process started
2018/01/21 14:25:56 [notice] 4966#0: signal process started
2018/01/21 14:27:07 [notice] 5012#0: signal process started
2018/01/21 14:28:04 [emerg] 5080#0: invalid number of arguments in "proxy_set_header" directive in /usr/local/nginx/conf/vhost/www.xxxx.com.conf:35
2018/01/21 14:29:55 [emerg] 5119#0: invalid number of arguments in "proxy_set_header" directive in /usr/local/nginx/conf/vhost/www.xxxx.com.conf:35
2018/01/21 14:32:30 [emerg] 5154#0: invalid number of arguments in "proxy_set_header" directive in /usr/local/nginx/conf/vhost/www.xxxx.com.conf:35
2018/01/21 14:33:40 [emerg] 5164#0: invalid number of arguments in "proxy_set_header" directive in /usr/local/nginx/conf/vhost/www.xxxx.com.conf:35
2018/01/21 14:41:49 [notice] 5283#0: signal process started
2018/01/21 14:42:28 [notice] 5316#0: signal process started
2018/01/21 14:48:05 [notice] 5377#0: signal process started
2018/01/21 14:54:55 [notice] 5487#0: signal process started
2018/01/21 23:27:01 [notice] 8708#0: signal process started
2018/01/21 23:36:46 [notice] 8831#0: signal process started
2018/01/21 23:39:26 [notice] 8899#0: signal process started
2018/01/22 00:08:26 [notice] 9249#0: signal process started
请预览一下你填的内容再提交。

如果你已经填完上面的问卷，请把下面的英文部份删除，再提交 Issue。
Please remove the Chinese section above.

The text was updated successfully, but these errors were encountered:

android0276 · 2018-03-16T03:04:33Z

我的MacOS也有这个问题，我回退到了v3.12正常了

man2018 · 2018-03-16T04:02:49Z

@android0276 哥们，你也是用的header吗

kirbyzhu · 2018-03-16T05:13:08Z

@android0276 我是用 go.sh 文件安装的，请问服务器上如何回退版本啊？

wizarddewhite · 2018-03-19T08:37:30Z

我的今天突然用不了了，也不知道怎么debug

bymanaire · 2018-03-21T13:05:42Z

突然用不了了+1

anjia0532 · 2018-06-25T00:36:48Z

你试试把udp,mux去掉试试？

kslr · 2019-01-20T18:20:55Z

太久没有活动，关闭这个issue

* fix:observatory not supported by multi-json * Fix: observatory starts with empty config & fails to close (v2ray#957) * Update strategy_leastping.go (v2ray#1019) * add custom probe URL support for observatory * add custom probe interval for observer * apply coding style * Fix: observatory log & JSON config(v2ray#1211) Co-authored-by: ihotte <[email protected]> * Change default probe url from api.v2fly.org to www.google.com * Cherry-pick missing code from branch 'dev-advloadblancer-2' Co-authored-by: Shelikhoo <[email protected]> Co-authored-by: Loyalsoldier <[email protected]> Co-authored-by: fanyiguan <[email protected]> Co-authored-by: ihotte <[email protected]> Co-authored-by: ihotte <[email protected]>

kslr closed this as completed Jan 20, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

mac系统使用v2ray v3.13 ws+ssl+header分流断流现象严重 #957

mac系统使用v2ray v3.13 ws+ssl+header分流断流现象严重 #957

man2018 commented Mar 13, 2018 •

edited

Loading

android0276 commented Mar 16, 2018

man2018 commented Mar 16, 2018

kirbyzhu commented Mar 16, 2018

wizarddewhite commented Mar 19, 2018

bymanaire commented Mar 21, 2018

anjia0532 commented Jun 25, 2018

kslr commented Jan 20, 2019

mac系统使用v2ray v3.13 ws+ssl+header分流断流现象严重 #957

mac系统使用v2ray v3.13 ws+ssl+header分流断流现象严重 #957

Comments

man2018 commented Mar 13, 2018 • edited Loading

android0276 commented Mar 16, 2018

man2018 commented Mar 16, 2018

kirbyzhu commented Mar 16, 2018

wizarddewhite commented Mar 19, 2018

bymanaire commented Mar 21, 2018

anjia0532 commented Jun 25, 2018

kslr commented Jan 20, 2019

man2018 commented Mar 13, 2018 •

edited

Loading