能访问YouTube但无法播放视频

[C-Entropy]

除非特殊情况，请完整填写所有问题。不按模板发的 issue 将直接被关闭。
如果你遇到的问题不是 V2Ray 的 bug，比如你不清楚要如何配置，请使用Discussion进行讨论。

1. 你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明）

V2Ray 4.44.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.17.3 linux/amd64)
A unified platform for anti-censorship.

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

使用Firefox在Linux下通过VMess代理看YouTube视频等

3. 你看到的不正常的现象是什么？（请描述具体现象，比如访问超时，TLS 证书错误等）

1.可以访问youtube主页、视频页，但无法播放视频，无法登录google
2.可以使用google搜索，但无法登录，且跳转搜索结果超时
3.能使用github，但Preview issue的时候超时
4.手机使用相同server可以访问，firefox使用vpn插件（hoxx）可以正常访问

4. 你期待看到的正确表现是怎样的？

正常播放视频，可以登录google等

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

服务器端配置:

    // 在这里附上服务器端配置文件
{
    "log": {
	"loglevel": "warning",
	"access": "/var/log/v2ray/access.log",
	"error": "/var/log/v2ray/error.log"
    },
    "dns": {
	"servers": [
	    {
	    "address": "119.29.29.29",
	    "port": 53,
	    "domains": [
	  	"geosite:cn"
	    ],
	    "expectIPs": [
	  	"geoip:cn"
	    ]
	}
	    ,
	    {
		"address": "8.8.8.8",
		"port": 53,
		"domains": [
	 	    "geosite:geolocation-!cn",
	 	    "geosite:speedtest"
		]
	    },
	    "1.1.1.1",
	    "localhost"
	]
    },
    "inbounds": [
	{
	"listen": "127.0.0.1",
	"port": 20170, // 监听端口
	"protocol": "socks", // 入口协议为 SOCKS 5
	"sniffing": {
            "enabled": true,
            "destOverride": ["http", "tls"]
	},
	"settings": {
            "auth": "noauth"  //socks的认证设置，noauth 代表不认证，由于 socks 通常在客户端使用，所以这里不认证
	}
    },
	{
	"listen": "127.0.0.1",
	"port": 20172,
	"protocol": "http",
	"sniffing": {
            "enabled": true,
            "destOverride": ["http", "tls"]
	},
	"settings": {
            "userLevel": 8
	},
	"tag": "http"
    }
    ],
    "outbounds": [
	{
	"mux": {
	    "concurrency": 8,
	    "enabled": false
        },
        "protocol": "vmess",
        "sendThrough": "0.0.0.0",
        "settings": {
            "vnext": [
                {
                "address": "",
                "port": 443,
                "users": [
                    {
		    "alterId": 0,
                    "id": "a9a076f3-2cd9-48c4-e7ae-6e207cc4a6f3",
		    "level": 8,
                    "security": "auto"
                }
                ]
            }
            ]
        },
        "streamSettings":
	{
	    "network": "tcp",
            "security": "tls",
            "tlsSettings": {
                "disableSystemRoot": false
            },
            "xtlsSettings": {
                "disableSystemRoot": false
            }
        }
	,
        "tag": "PROXY"
    },
	{
	"protocol": "freedom",
	"settings": {},
	"tag": "DIRECT"
    }
    ],
    "routing": {
	"domainStrategy": "IPOnDemand",
	"rules": [
	    {
	    "type": "field",
	    "outboundTag": "DIRECT",
	    "domain": ["geosite:cn"]
	},
	    {
	    "type": "field",
	    "outboundTag": "DIRECT",
	    "ip": [
		"geoip:cn",
		"geoip:private"
	    ]
	}
	]
    }
}

客户端配置:

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

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

服务器端错误日志:

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

客户端错误日志:

    // 在这里附上客户端日志
    2022/02/21 18:33:05 [Warning] V2Ray 4.44.0 started
2022/02/21 18:34:19 [Warning] V2Ray 4.44.0 started
2022/02/21 18:34:24 [Warning] V2Ray 4.44.0 started

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

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

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

  //客户端访问日志
2022/02/21 17:54:12 tcp:127.0.0.1:37454 accepted tcp:[2001::6ca0:a509]:443 [PROXY]
2022/02/21 17:54:12 tcp:127.0.0.1:37452 accepted tcp:[2001::6ca0:a509]:443 [PROXY]
2022/02/21 17:54:12 tcp:127.0.0.1:37456 accepted tcp:31.13.96.192:443 [PROXY]
2022/02/21 17:54:17 tcp:127.0.0.1:37458 accepted tcp:108.160.165.139:443 [PROXY]
2022/02/21 17:54:18 tcp:127.0.0.1:37460 accepted tcp:140.82.114.25:443 [PROXY]
2022/02/21 17:54:18 tcp:127.0.0.1:37462 accepted tcp:203.208.40.34:443 [DIRECT]
2022/02/21 17:54:19 tcp:127.0.0.1:37464 accepted tcp:104.244.43.229:443 [PROXY]
2022/02/21 17:54:19 tcp:127.0.0.1:37468 accepted tcp:120.232.181.166:443 [DIRECT]
2022/02/21 17:54:20 tcp:127.0.0.1:37470 accepted tcp:120.241.147.166:443 [DIRECT]
2022/02/21 17:54:21 tcp:127.0.0.1:37472 accepted tcp:172.217.31.13:443 [PROXY]
2022/02/21 17:54:22 tcp:127.0.0.1:37474 accepted tcp:172.217.24.110:443 [PROXY]
2022/02/21 17:54:59 tcp:127.0.0.1:37476 accepted tcp:[2001::6ca0:a509]:443 [PROXY]
2022/02/21 17:55:00 tcp:127.0.0.1:37478 accepted tcp:[2001::6ca0:a509]:443 [PROXY]
2022/02/21 17:55:01 tcp:127.0.0.1:37480 accepted tcp:173.236.212.42:443 [PROXY]
2022/02/21 17:55:02 tcp:127.0.0.1:37482 accepted tcp:142.250.207.86:443 [PROXY]
2022/02/21 17:55:02 tcp:127.0.0.1:37484 accepted tcp:34.120.208.123:443 [PROXY]
2022/02/21 17:55:02 tcp:127.0.0.1:37486 accepted tcp:203.208.40.98:443 [DIRECT]
2022/02/21 17:55:03 tcp:127.0.0.1:37488 accepted tcp:203.208.40.98:443 [DIRECT]
2022/02/21 17:55:03 tcp:127.0.0.1:37492 rejected  proxy/socks: insufficient header > EOF
2022/02/21 17:55:03 tcp:127.0.0.1:37494 accepted tcp:120.232.181.162:443 [DIRECT]
2022/02/21 17:55:04 tcp:127.0.0.1:37496 accepted tcp:172.217.24.225:443 [PROXY]
2022/02/21 17:55:14 tcp:127.0.0.1:37498 accepted tcp:[2001::6ca0:a509]:443 [PROXY]
2022/02/21 17:55:14 tcp:127.0.0.1:37500 accepted tcp:[2001::6ca0:a509]:443 [PROXY]
2022/02/21 17:55:21 tcp:127.0.0.1:37502 accepted tcp:34.117.237.239:443 [PROXY]
2022/02/21 17:55:24 tcp:127.0.0.1:37504 accepted tcp:[2001::6ca0:a509]:443 [PROXY]
2022/02/21 17:55:24 tcp:127.0.0.1:37506 accepted tcp:[2001::6ca0:a509]:443 [PROXY]
2022/02/21 17:55:33 tcp:127.0.0.1:37508 accepted tcp:[2001::6ca0:a509]:443 [PROXY]
2022/02/21 17:55:34 tcp:127.0.0.1:37510 accepted tcp:[2001::6ca0:a509]:443 [PROXY]
2022/02/21 17:55:34 tcp:127.0.0.1:37512 accepted tcp:20.205.243.166:443 [PROXY]
2022/02/21 17:55:35 tcp:127.0.0.1:37514 accepted tcp:185.199.109.154:443 [PROXY]
2022/02/21 17:55:35 tcp:127.0.0.1:37516 rejected  proxy/socks: insufficient header > EOF
2022/02/21 17:55:35 tcp:127.0.0.1:37532 rejected  proxy/socks: insufficient header > EOF
2022/02/21 17:55:35 tcp:127.0.0.1:37518 accepted tcp:185.199.111.133:443 [PROXY]
2022/02/21 17:55:35 tcp:127.0.0.1:37520 accepted tcp:185.199.111.154:443 [PROXY]
2022/02/21 17:55:35 tcp:127.0.0.1:37536 accepted tcp:185.199.109.154:443 [PROXY]
2022/02/21 17:55:35 tcp:127.0.0.1:37522 accepted tcp:185.199.111.154:443 [PROXY]
2022/02/21 17:55:35 tcp:127.0.0.1:37538 accepted tcp:185.199.109.154:443 [PROXY]
2022/02/21 17:55:35 tcp:127.0.0.1:37528 accepted tcp:185.199.111.154:443 [PROXY]
2022/02/21 17:55:35 tcp:127.0.0.1:37534 accepted tcp:185.199.109.154:443 [PROXY]
2022/02/21 17:55:35 tcp:127.0.0.1:37526 accepted tcp:185.199.111.154:443 [PROXY]
2022/02/21 17:55:36 tcp:127.0.0.1:37540 accepted tcp:140.82.112.22:443 [PROXY]
2022/02/21 17:55:36 tcp:127.0.0.1:37542 rejected  proxy/socks: failed to read request > read tcp 127.0.0.1:20170->127.0.0.1:37542: read: connection reset by peer
2022/02/21 17:55:36 tcp:127.0.0.1:37544 rejected  proxy/socks: failed to read request > read tcp 127.0.0.1:20170->127.0.0.1:37544: read: connection reset by peer
2022/02/21 17:55:36 tcp:127.0.0.1:37546 accepted tcp:185.199.111.154:443 [PROXY]
2022/02/21 17:55:36 tcp:127.0.0.1:37548 rejected  proxy/socks: insufficient header > EOF
2022/02/21 17:55:36 tcp:127.0.0.1:37550 accepted tcp:185.199.109.154:443 [PROXY]
2022/02/21 17:56:08 tcp:127.0.0.1:37552 accepted tcp:35.163.208.27:443 [PROXY]


9) 如果 V2Ray 无法启动，请附上 `--test` 输出。

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

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

通常的命令为 `journalctl -u v2ray`。

请预览一下你填的内容再提交。