Skip to content
New issue

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

Jump to bottom

連線時在客戶端會出現錯誤訊息：[Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound #1843

Closed
mars33 opened this issue Aug 14, 2019 · 11 comments
Closed

連線時在客戶端會出現錯誤訊息：[Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound #1843

mars33 opened this issue Aug 14, 2019 · 11 comments

Comments

@mars33
Copy link

mars33 commented Aug 14, 2019

提交 Issue 之前请先阅读 Issue 指引，然后回答下面的问题，谢谢。
除非特殊情况，请完整填写所有问题。不按模板发的 issue 将直接被关闭。
如果你遇到的问题不是 V2Ray 的 bug，比如你不清楚要如何配置，请使用Discussion进行讨论。

  1. 你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明）
    v4.20.0
    使用https://233blog.com/ 一鍵安裝腳本
    並且使用V2Ray+Websocket+TLS+Cloudflare

  2. 你的使用场景是什么？比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。
    使用Chrome通過VMess上網、google

  3. 你看到的不正常的现象是什么？（请描述具体现象，比如访问超时，TLS 证书错误等）
    網頁無法開啟
    無法連上這個網站 blogspot.com 的回應時間過長。

  4. 你期待看到的正确表现是怎样的？
    可以正常開啟網站

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

服务器端配置:
/etc/v2ray/config.json

   {
	"log": {
		"access": "/var/log/v2ray/access.log",
		"error": "/var/log/v2ray/error.log",
		"loglevel": "warning"
	},
	"inbounds": [
		{
			"port": 25818,
			"protocol": "vmess",
			"settings": {
				"clients": [
					{
						"id": "XXXXXXX-de14-4fa2-a657-6f5ad9e61e6e",
						"level": 1,
						"alterId": 233
					}
				]
			},
			"streamSettings": {
				"network": "ws"
			},
			"sniffing": {
				"enabled": true,
				"destOverride": [
					"http",
					"tls"
				]
			}
		}
		//include_ss
		//include_socks
		//include_mtproto
		//include_in_config
		//
	],
	"outbounds": [
		{
			"protocol": "freedom",
			"settings": {}
		},
		{
			"protocol": "blackhole",
			"settings": {},
			"tag": "blocked"
		},
		{
			"protocol": "freedom",
			"settings": {},
			"tag": "direct"
		},
		{
			"protocol": "mtproto",
			"settings": {},
			"tag": "tg-out"
		}
		//include_out_config
		//
	],
	"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",
				"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"
			},
			{
				"type": "field",
				"inboundTag": ["tg-in"],
				"outboundTag": "tg-out"
			}
			,
			{
				"type": "field",
				"domain": [
					"domain:epochtimes.com",
					"domain:epochtimes.com.tw",
					"domain:epochtimes.fr",
					"domain:epochtimes.de",
					"domain:epochtimes.jp",
					"domain:epochtimes.ru",
					"domain:epochtimes.co.il",
					"domain:epochtimes.co.kr",
					"domain:epochtimes-romania.com",
					"domain:erabaru.net",
					"domain:lagranepoca.com",
					"domain:theepochtimes.com",
					"domain:ntdtv.com",
					"domain:ntd.tv",
					"domain:ntdtv-dc.com",
					"domain:ntdtv.com.tw",
					"domain:minghui.org",
					"domain:renminbao.com",
					"domain:dafahao.com",
					"domain:dongtaiwang.com",
					"domain:falundafa.org",
					"domain:wujieliulan.com",
					"domain:ninecommentaries.com",
					"domain:shenyun.com"
				],
				"outboundTag": "blocked"
			}			,
                {
                    "type": "field",
                    "protocol": [
                        "bittorrent"
                    ],
                    "outboundTag": "blocked"
                }
			//include_ban_ad
			//include_rules
			//
		]
	},
	"transport": {
		"kcpSettings": {
            "uplinkCapacity": 100,
            "downlinkCapacity": 100,
            "congestion": true
        },
		"sockopt": {
			"tcpFastOpen": true
		}
	}
}
 // 在这里附上服务器端配置文件

/etc/v2ray/233blog_v2ray_config.json

   {
    "outbounds": [
        {
            "protocol": "vmess",
            "settings": {
                "vnext": [
                    {
                        "address": "www.xxxxxxx.ml",
                        "port": 443,
                        "users": [
                            {
                                "id": "xxxxxxx-de14-4fa2-a657-6f5ad9e61e6e",
                                "alterId": 233,
                                "security": "auto"
                            }
                        ]
                    }
                ]
            },
            "streamSettings": {
                "network": "ws",
                "security": "tls",
                "tlsSettings": {
                    "serverName": "www.xxxxxxx.ml"
                },
                "wsSettings": {
                    "path": "/233blog",
                    "headers": {
                        "Host": "www.xxxxxxx.ml"
                    }
                }
            },
            "mux": {
                "enabled": true
            }
        },
        {
            "protocol": "freedom",
            "settings": {},
            "tag": "direct"
        },
        {
			"protocol": "blackhole",
			"settings": {},
			"tag": "blocked"
        },
        {
            "protocol": "dns",
            "tag": "dns-out"
        }
    ],
    "inbounds": [
        {
            "port": "1099",
            "protocol": "dokodemo-door",
            "settings": {
              "network": "tcp,udp",
              "timeout": 0,
              "followRedirect": true
            }
        },
        {
            "port": 2133,
            "tag": "dns-in",
            "protocol": "dokodemo-door",
            "settings": {
                "address": "127.0.0.1",
                "port": 80,
                "timeout": 0,
                "network": "tcp,udp"
            }
        },
        {
            "port": 2333,
            "protocol": "socks",
            "settings": {
                "auth": "noauth",
                "udp": true
            }
        },
        {
            "port": 6666,
            "protocol": "http",
            "settings": {
                "auth": "noauth",
                "udp": true
            }
        }
    ],
    "dns": {
        "servers": [
            "1.1.1.1",
            "1.0.0.1",
            {
                "address": "119.29.29.29",
                "port": 53,
                "domains": [
                    "geosite:cn"
                ]
            },
            "8.8.8.8",
            "8.8.4.4",
            "localhost"
        ]
    },
    "routing": {
        "domainStrategy": "IPOnDemand",	
        "rules": [
            {
                "type": "field",
                "inboundTag": [
                    "dns-in"
                ],
                "outboundTag": "dns-out"
            },
            {
				"type": "field",
				"ip": [
					"geoip:private"
				],
				"outboundTag": "blocked"
			},
            {
                "type": "field",
                "ip": [
                    "geoip:cn"
                ],
                "outboundTag": "direct"
            },
            {
                "type": "field",
                "domain": [
                    "geosite:cn"
                ],
                "outboundTag": "direct"
            }
        ]
    }
}
 // 在这里附上客户端配置

客户端配置:

{
  "log": {
    "access": "",
    "error": "",
    "loglevel": "warning"
  },
  "inbounds": [
    {
      "port": 10808,
      "listen": "127.0.0.1",
      "protocol": "socks",
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls"
        ]
      },
      "settings": {
        "auth": "noauth",
        "udp": true,
        "ip": null,
        "clients": null
      },
      "streamSettings": null
    }
  ],
  "outbounds": [
    {
      "tag": "proxy",
      "protocol": "vmess",
      "settings": {
        "vnext": [
          {
            "address": "www.xxxxxxx.ml",
            "port": 25818,
            "users": [
              {
                "id": "XXXXXXXX-de14-4fa2-a657-6f5ad9e61e6e",
                "alterId": 233,
                "email": "t@t.tt",
                "security": "auto"
              }
            ]
          }
        ],
        "servers": null,
        "response": null
      },
      "streamSettings": {
        "network": "ws",
        "security": "tls",
        "tlsSettings": {
          "allowInsecure": true,
          "serverName": "www.xxxxxxx.ml"
        },
        "tcpSettings": null,
        "kcpSettings": null,
        "wsSettings": {
          "connectionReuse": true,
          "path": "/233blog",
          "headers": {
            "Host": "www.xxxxxxx.ml"
          }
        },
        "httpSettings": null,
        "quicSettings": null
      },
      "mux": {
        "enabled": true
      }
    },
    {
      "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
    }
  ],
  "dns": null,
  "routing": {
    "domainStrategy": "IPIfNonMatch",
    "rules": []
  }
}
    // 在这里附上客户端配置
  1. 请附上出错时软件输出的错误日志。在 Linux 中，日志通常在 /var/log/v2ray/error.log 文件中。

服务器端错误日志:

2019/08/02 01:17:19 [Warning] v2ray.com/core: V2Ray 4.20.0 started
2019/08/10 23:47:42 [Warning] v2ray.com/core/transport/internet/websocket: failed to serve http for WebSocket > accept tcp [::]:25818: use of closed network connection
2019/08/10 23:48:16 [Warning] v2ray.com/core: V2Ray 4.20.0 started
2019/08/11 00:04:55 [Warning] v2ray.com/core/transport/internet/websocket: failed to serve http for WebSocket > accept tcp [::]:25818: use of closed network connection
2019/08/11 00:04:55 [Warning] v2ray.com/core: V2Ray 4.20.0 started
2019/08/11 00:40:36 [Warning] v2ray.com/core: V2Ray 4.20.0 started
2019/08/14 18:58:27 [Warning] v2ray.com/core/transport/internet/websocket: failed to serve http for WebSocket > accept tcp [::]:25818: use of closed network connection
2019/08/14 18:58:27 [Warning] v2ray.com/core: V2Ray 4.20.0 started
   
 // 在这里附上服务器端日志

客户端错误日志:

  2019/08/15 01:10:11 tcp:127.0.0.1:9349 accepted tcp:mtalk.google.com:5228 
2019/08/15 01:10:12 tcp:127.0.0.1:9351 accepted tcp:gf.line.naver.jp:443 
2019/08/15 01:10:12 tcp:127.0.0.1:9355 accepted tcp:f-log-extension.grammarly.io:443 
2019/08/15 01:10:12 tcp:127.0.0.1:9357 accepted tcp:cello.client-channel.google.com:443 
2019/08/15 01:10:13 tcp:127.0.0.1:9359 accepted tcp:cello.client-channel.google.com:443 
2019/08/15 01:10:13 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://www.keymaker.ml:25818/233blog):  > dial tcp 104.28.10.133:25818: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://www.keymaker.ml:25818/233blog):  > dial tcp 104.28.11.133:25818: i/o timeout] > v2ray.com/core/common/retry: all retry attempts failed
2019/08/15 01:10:15 tcp:127.0.0.1:9369 accepted tcp:ssl.gstatic.com:443 
2019/08/15 01:10:15 tcp:127.0.0.1:9371 accepted tcp:capi.grammarly.com:443 
2019/08/15 01:10:15 tcp:127.0.0.1:9374 accepted tcp:ssl.gstatic.com:443 
2019/08/15 01:10:17 tcp:127.0.0.1:9380 accepted tcp:f-log-extension.grammarly.io:443 
2019/08/15 01:10:18 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://www.keymaker.ml:25818/233blog):  > dial tcp 104.28.10.133:25818: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://www.keymaker.ml:25818/233blog):  > dial tcp 104.28.11.133:25818: i/o timeout] > v2ray.com/core/common/retry: all retry attempts failed
2019/08/15 01:10:19 tcp:127.0.0.1:9387 accepted tcp:d.dropbox.com:443 
2019/08/15 01:10:22 tcp:127.0.0.1:9395 accepted tcp:capi.grammarly.com:443 
2019/08/15 01:10:22 tcp:127.0.0.1:9397 accepted tcp:gf.line.naver.jp:443 
2019/08/15 01:10:23 tcp:127.0.0.1:9402 accepted tcp:cello.client-channel.google.com:443 
2019/08/15 01:10:24 tcp:127.0.0.1:9405 accepted tcp:cello.client-channel.google.com:443 
2019/08/15 01:10:25 tcp:127.0.0.1:9412 accepted tcp:ssl.gstatic.com:443 
2019/08/15 01:10:25 tcp:127.0.0.1:9414 accepted tcp:edge-chat.facebook.com:443 
2019/08/15 01:10:27 tcp:127.0.0.1:9420 accepted tcp:github.com:443 
2019/08/15 01:10:31 tcp:127.0.0.1:9428 accepted tcp:cello.client-channel.google.com:443 
2019/08/15 01:10:31 tcp:127.0.0.1:9432 accepted tcp:cello.client-channel.google.com:443 
2019/08/15 01:10:32 tcp:127.0.0.1:9436 accepted tcp:play.google.com:443 
2019/08/15 01:10:34 tcp:127.0.0.1:9446 accepted tcp:ssl.gstatic.com:443 
2019/08/15 01:10:35 tcp:127.0.0.1:9451 accepted tcp:ssl.gstatic.com:443 
2019/08/15 01:10:36 tcp:127.0.0.1:9456 accepted tcp:facebook.com:443 
2019/08/15 01:10:36 tcp:127.0.0.1:9458 accepted tcp:www.facebook.com:443 
2019/08/15 01:10:36 tcp:127.0.0.1:9465 accepted tcp:static.xx.fbcdn.net:443 
2019/08/15 01:10:36 tcp:127.0.0.1:9462 accepted tcp:stats.g.doubleclick.net:443 
2019/08/15 01:10:36 tcp:127.0.0.1:9464 accepted tcp:www.google-analytics.com:443 
2019/08/15 01:10:36 tcp:127.0.0.1:9466 accepted tcp:scontent-hkg3-2.xx.fbcdn.net:443 
2019/08/15 01:10:36 tcp:127.0.0.1:9467 accepted tcp:scontent.xx.fbcdn.net:443 
2019/08/15 01:10:38 tcp:127.0.0.1:9474 accepted tcp:clients4.google.com:443 
2019/08/15 01:10:40 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://www.keymaker.ml:25818/233blog):  > dial tcp 104.28.10.133:25818: i/o timeout v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://www.keymaker.ml:25818/233blog):  > dial tcp 104.28.11.133:25818: i/o timeout] > v2ray.com/core/common/retry: all retry attempts failed
2019/08/15 01:10:42 tcp:127.0.0.1:9487 accepted tcp:cello.client-channel.google.com:443 
2019/08/15 01:10:43 tcp:127.0.0.1:9489 accepted tcp:cello.client-channel.google.com:443 
2019/08/15 01:10:44 tcp:127.0.0.1:9495 accepted tcp:gf.line.naver.jp:443 
2019/08/15 01:10:45 tcp:127.0.0.1:9500 accepted tcp:ssl.gstatic.com:443 
2019/08/15 01:10:45 tcp:127.0.0.1:9502 accepted tcp:f-log-extension.grammarly.io:443 
2019/08/15 01:10:46 tcp:127.0.0.1:9504 accepted tcp:ssl.gstatic.com:443 

  // 在这里附上客户端日志
  1. 请附上访问日志。在 Linux 中，日志通常在 /var/log/v2ray/access.log 文件中。
2019/08/14 23:40:24 49.85.236.251:37612 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:40:24 49.85.236.251:37614 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:40:24 49.85.236.251:37616 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:40:48 49.85.236.251:37618 accepted udp:239.255.255.250:1900 
2019/08/14 23:41:04 49.85.236.251:37624 accepted udp:1.1.1.1:53 
2019/08/14 23:41:05 49.85.236.251:37626 accepted tcp:omt.garmin.com:443 
2019/08/14 23:41:05 49.85.236.251:37634 accepted tcp:www.linkedin.com:443 
2019/08/14 23:41:05 49.85.236.251:37628 accepted tcp:www.linkedin.com:443 
2019/08/14 23:41:05 49.85.236.251:37630 accepted tcp:www.linkedin.com:443 
2019/08/14 23:41:05 49.85.236.251:37632 accepted tcp:www.linkedin.com:443 
2019/08/14 23:41:05 49.85.236.251:37638 accepted tcp:www.linkedin.com:443 
2019/08/14 23:41:05 49.85.236.251:37636 accepted tcp:android.googleapis.com:443 
2019/08/14 23:41:06 49.85.236.251:37644 accepted tcp:datasaver.googleapis.com:443 
2019/08/14 23:41:06 49.85.236.251:37646 accepted tcp:datasaver.googleapis.com:443 
2019/08/14 23:41:06 49.85.236.251:37648 accepted tcp:check.googlezip.net:80 
2019/08/14 23:41:06 49.85.236.251:37652 accepted tcp:108.177.97.114:80 
2019/08/14 23:41:06 49.85.236.251:37654 accepted tcp:108.177.97.114:80 
2019/08/14 23:41:06 49.85.236.251:37662 accepted udp:172.217.27.140:443 
2019/08/14 23:41:06 49.85.236.251:37650 accepted tcp:proxy.googlezip.net:443 
2019/08/14 23:41:07 49.85.236.251:37674 accepted tcp:accounts.google.com:443 
2019/08/14 23:41:07 49.85.236.251:37684 accepted udp:172.217.27.140:443 
2019/08/14 23:41:09 49.85.236.251:37686 accepted tcp:proxy.googlezip.net:443 
2019/08/14 23:41:10 49.85.236.251:37692 accepted udp:172.217.160.78:443 
2019/08/14 23:41:10 49.85.236.251:37694 accepted tcp:check.googlezip.net:80 
2019/08/14 23:41:33 49.85.236.251:37698 accepted tcp:android.googleapis.com:443 
2019/08/14 23:41:38 49.85.236.251:37702 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:41:39 49.85.236.251:37704 accepted udp:239.255.255.250:1900 
2019/08/14 23:41:46 tcp:49.85.236.251:37544 accepted tcp:ssl.gstatic.com:443 
2019/08/14 23:41:47 49.85.236.251:37708 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:41:48 tcp:49.85.236.251:37544 accepted tcp:clients6.google.com:443 
2019/08/14 23:41:49 tcp:49.85.236.251:37544 accepted tcp:clients6.google.com:443 
2019/08/14 23:41:49 49.85.236.251:37710 accepted tcp:android.googleapis.com:443 
2019/08/14 23:41:50 tcp:49.85.236.251:37544 accepted tcp:clients6.google.com:443 
2019/08/14 23:42:02 49.85.236.251:37720 accepted tcp:check.googlezip.net:80 
2019/08/14 23:42:04 49.85.236.251:37724 accepted tcp:mtalk.google.com:5228 
2019/08/14 23:42:07 49.85.236.251:37728 accepted tcp:mobilenetworkscoring-pa.googleapis.com:443 
2019/08/14 23:42:08 tcp:49.85.236.251:37544 accepted tcp:gfp.line.naver.jp:443 
2019/08/14 23:42:11 49.85.236.251:37736 accepted udp:239.255.255.250:1900 
2019/08/14 23:42:13 49.85.236.251:37738 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2019/08/14 23:42:15 49.85.236.251:37740 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:42:15 49.85.236.251:37742 accepted udp:1.1.1.1:53 
2019/08/14 23:42:17 49.85.236.251:37744 accepted tcp:connectapi.garmin.com:443 
2019/08/14 23:42:24 tcp:49.85.236.251:37480 accepted tcp:d.dropbox.com:443 
2019/08/14 23:42:27 49.85.236.251:37754 accepted udp:239.255.255.250:1900 
2019/08/14 23:42:43 49.85.236.251:37756 accepted udp:239.255.255.250:1900 
2019/08/14 23:42:44 49.85.236.251:37758 accepted udp:1.1.1.1:53 
2019/08/14 23:42:46 49.85.236.251:37760 accepted tcp:connectivitycheck.gstatic.com:443 
2019/08/14 23:42:59 49.85.236.251:37764 accepted udp:239.255.255.250:1900 
2019/08/14 23:43:07 49.85.236.251:37766 accepted udp:239.255.255.250:1900 
2019/08/14 23:43:15 49.85.236.251:37770 accepted udp:239.255.255.250:1900 
2019/08/14 23:43:22 49.85.236.251:37772 accepted udp:1.1.1.1:53 
2019/08/14 23:43:30 49.85.236.251:37774 accepted udp:239.255.255.250:1900 
2019/08/14 23:43:46 49.85.236.251:37778 accepted udp:1.1.1.1:53 
2019/08/14 23:43:47 49.85.236.251:37780 accepted udp:239.255.255.250:1900 
2019/08/14 23:43:48 49.85.236.251:37782 accepted tcp:android.prod.ftl.netflix.com:443 
2019/08/14 23:43:50 tcp:49.85.236.251:37544 accepted tcp:docs.google.com:443 
2019/08/14 23:43:55 49.85.236.251:37788 accepted udp:1.1.1.1:53 
2019/08/14 23:43:57 49.85.236.251:37792 accepted tcp:mtalk.google.com:5228 
2019/08/14 23:44:01 49.85.236.251:37796 accepted udp:239.255.255.250:1900 
2019/08/14 23:44:06 49.85.236.251:37798 accepted udp:239.255.255.250:1900 
2019/08/14 23:44:17 49.85.236.251:37802 accepted udp:239.255.255.250:1900 
2019/08/14 23:44:33 49.85.236.251:37804 accepted udp:239.255.255.250:1900 
2019/08/14 23:44:49 49.85.236.251:37806 accepted udp:239.255.255.250:1900 
2019/08/14 23:49:20 49.85.236.251:37834 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:49:23 49.85.236.251:37836 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:49:25 49.85.236.251:37838 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:49:28 49.85.236.251:37840 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:49:29 49.85.236.251:37842 accepted udp:1.1.1.1:53 
2019/08/14 23:49:31 49.85.236.251:37844 accepted tcp:mtalk.google.com:5228 
2019/08/14 23:50:02 49.85.236.251:37850 accepted udp:1.1.1.1:53 
2019/08/14 23:50:05 49.85.236.251:37852 accepted tcp:mqtt-mini.facebook.com:443 
2019/08/14 23:50:07 49.85.236.251:37856 accepted udp:239.255.255.250:1900 
2019/08/14 23:50:08 49.85.236.251:37858 accepted tcp:graph.facebook.com:443 
2019/08/14 23:50:12 49.85.236.251:37864 accepted tcp:graph.facebook.com:443 
2019/08/14 23:50:31 49.85.236.251:37870 accepted udp:1.1.1.1:53 
2019/08/14 23:50:32 49.85.236.251:37872 accepted tcp:inbox.google.com:443 
2019/08/14 23:50:35 49.85.236.251:37876 accepted tcp:edge-mqtt.facebook.com:443 
2019/08/14 23:50:36 49.85.236.251:37880 accepted udp:239.255.255.250:1900 
2019/08/14 23:56:38 49.85.236.251:37910 accepted tcp:mtalk.google.com:5228 
2019/08/14 23:56:42 49.85.236.251:37914 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:56:42 49.85.236.251:37916 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:56:48 49.85.236.251:37918 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:56:51 49.85.236.251:37922 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:56:51 49.85.236.251:37920 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:56:54 49.85.236.251:37924 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > websocket: close 1000 (normal)
2019/08/14 23:58:37 49.85.236.251:37934 accepted udp:1.1.1.1:53 
2019/08/14 23:58:39 49.85.236.251:37938 accepted tcp:alt3-mtalk.google.com:443 
2019/08/15 00:00:23 49.85.236.251:37952 accepted udp:1.1.1.1:53 
2019/08/15 00:00:28 49.85.236.251:37954 accepted tcp:mtalk.google.com:5228 
2019/08/15 00:00:59 49.85.236.251:37958 accepted udp:1.1.1.1:53 
2019/08/15 00:02:02 49.85.236.251:37966 accepted udp:1.1.1.1:53 
2019/08/15 00:02:03 49.85.236.251:37968 accepted tcp:91.108.56.125:5222 
2019/08/15 00:02:03 49.85.236.251:37970 accepted tcp:91.108.56.125:5222 
2019/08/15 00:02:03 49.85.236.251:37972 accepted tcp:149.154.167.51:443 
2019/08/15 00:02:03 49.85.236.251:37974 accepted tcp:149.154.167.51:443 
2019/08/15 00:02:03 49.85.236.251:37982 accepted tcp:91.108.56.125:5222 
2019/08/15 00:02:03 49.85.236.251:37980 accepted tcp:91.108.56.125:5222 
2019/08/15 00:02:03 49.85.236.251:37988 accepted tcp:graph.facebook.com:443 
2019/08/15 00:02:03 49.85.236.251:37990 accepted tcp:graph.facebook.com:443 
2019/08/15 00:02:03 49.85.236.251:37992 accepted tcp:graph.facebook.com:443 
2019/08/15 00:02:03 49.85.236.251:37994 accepted tcp:firebaseremoteconfig.googleapis.com:443 
2019/08/15 00:02:04 49.85.236.251:38008 accepted tcp:mobilenetworkscoring-pa.googleapis.com:443 
2019/08/15 00:02:06 49.85.236.251:38012 accepted tcp:www.google.com:443 
2019/08/15 00:02:06 49.85.236.251:38014 accepted tcp:172.217.27.131:80 
2019/08/15 00:02:06 49.85.236.251:38016 accepted tcp:mail.google.com:443 
2019/08/15 00:02:06 49.85.236.251:38022 accepted udp:239.255.255.250:1900 
2019/08/15 00:02:07 49.85.236.251:38018 accepted tcp:update.googleapis.com:80 
2019/08/15 00:02:08 49.85.236.251:38030 accepted tcp:104.143.250.211:443 
2019/08/15 00:03:20 49.85.236.251:38042 accepted udp:1.1.1.1:53 
2019/08/15 00:03:22 49.85.236.251:38044 accepted tcp:mtalk.google.com:5228 
2019/08/15 00:03:37 49.85.236.251:38048 accepted udp:1.1.1.1:53 
2019/08/15 00:04:17 49.85.236.251:38054 accepted udp:1.1.1.1:53 
2019/08/15 00:04:29 49.85.236.251:38056 accepted udp:1.1.1.1:53 
    // 在这里附上服务器端日志

  1. 其它相关的配置文件（如 Nginx）和相关日志。

  2. 如果 V2Ray 无法启动，请附上 --test 输出。

通常的命令为 /usr/bin/v2ray/v2ray --test --config /etc/v2ray/config.json。请按实际情况修改。

  1. 如果 V2Ray 服务运行不正常，请附上 journal 日志。

通常的命令为 journalctl -u v2ray。

请预览一下你填的内容再提交。
@kslr
Copy link
Contributor

kslr commented Aug 14, 2019 •
edited

尝试一下关闭客户端中的MUX

@mars33
Copy link
Author

mars33 commented Aug 16, 2019

尝试一下关闭客户端中的MUX

关闭系统端的mux，无用
也试著要关闭客户端的mux～他会自己重load

@lyx32
Copy link

lyx32 commented Aug 29, 2019

我也遇到一样的问题。
你最后解决了吗？

@mars33
Copy link
Author

mars33 commented Aug 29, 2019

我也遇到一样的问题。
你最后解决了吗？

没有，问题依旧

@lyx32
Copy link

lyx32 commented Aug 29, 2019

我重新在freenoom上注册了个域名，然后重新部署了v2ray就可以了。
不过我在freenoom上看到我之前注册的免费域名好像被收回了。
我的问题估计是这个。你也看看呢？

@lyx32
Copy link

lyx32 commented Sep 10, 2019

我也遇到一样的问题。
你最后解决了吗？

没有，问题依旧

周天又遇到这个问题，我确认就是freenom的免费域名被回收了，我重新注册了那个域名，并重新绑定ns。然后就可以了。v2ray的服务端和客户端配置都没有动。
你试试ping一下你的域名，如果域名ping不通，我估计就是域名出了问题或者域名解析出了问题

@mars33
Copy link
Author

mars33 commented Oct 4, 2019

我也遇到一样的问题。
你最后解决了吗？

没有，问题依旧

周天又遇到这个问题，我确认就是freenom的免费域名被回收了，我重新注册了那个域名，并重新绑定ns。然后就可以了。v2ray的服务端和客户端配置都没有动。
你试试ping一下你的域名，如果域名ping不通，我估计就是域名出了问题或者域名解析出了问题

結果真的是域名的問題
我花錢買一個域名後重建V2Ray後就可以了！

@mars33
Copy link
Author

mars33 commented Oct 4, 2019

這個問題確認應該是域名被封鎖了
我花錢買一個域名後，重新建立V2Ray就沒發生過這個問題了！

@mars33 mars33 closed this as completed Oct 4, 2019
@lyx32
Copy link

lyx32 commented Feb 6, 2020

不能直接用 VPS 主机商的 ip ?

配置websocket+tls 也可以直接用ip链接，并且速度比域名快一些。
但是用websocket+ tls 的目的就是为了保护ip不被墙，所以这里不用ip。

@dreamyman
Copy link

我也遇到类似的问题，配置好ws+tls后又用233blog的脚本配置了shadowsocket，结果v2ray就连不上了，也是报这个错误，但是shadowsocket可以链接上网。

@lyx32
Copy link

lyx32 commented Feb 18, 2020

我也遇到类似的问题，配置好ws+tls后又用233blog的脚本配置了shadowsocket，结果v2ray就连不上了，也是报这个错误，但是shadowsocket可以链接上网。

你看下你链接的服务器地址是用的域名还是ip。
域名的话，检查下域名是否被回收，或者域名解析弄对没。
ip的话，那就只有你自己倒腾倒腾了。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mars33 @kslr @lyx32 @dreamyman