Xray-core
Xray-core copied to clipboard
1.6.3版本xtls-rprx-vision,google play 下载与更新不可用
我可以确定并不是ip的问题,其余部分不变去掉xtls-rprx-vision流控即可下载
客户端日志
app/dispatcher: sniffed domain: play-fe.googleapis.com
app/dispatcher: taking detour [proxy] for [tcp:play-fe.googleapis.com:443]
transport/internet/tcp: dialing TCP to tcp:my_vps_ip:443
proxy/vless/outbound: tunneling request to tcp:216.58.220.110:443 via my_vps_ip:443
proxy/vless/encoding: XtlsFilterTls13 found tls client hello! 728
proxy/vless/encoding: XtlsPadding 728 474 0
proxy/vless/encoding: Xtls Unpadding new block0 16 content 333 padding 760 0
proxy/vless/encoding: XtlsFilterTls13 found tls 1.3! 333
proxy/vless/encoding: XtlsPadding 74 828 0
proxy/vless/encoding: XtlsPadding 98 952 2
proxy/vless/encoding: XtlsWrite writeV 0 1055 0
proxy/vless/encoding: Xtls Unpadding new block0 0 content 866 padding 36 2
proxy/vless/encoding: XtlsRead splice
app/dispatcher: sniffed domain: rr1---sn-oguesn6r.gvt1.com
app/dispatcher: taking detour [proxy] for [tcp:rr1---sn-oguesn6r.gvt1.com:443]
transport/internet/tcp: dialing TCP to tcp:my_vps_ip:443
proxy/vless/outbound: tunneling request to tcp:209.85.229.70:443 via my_vps_ip:443
proxy/vless/encoding: XtlsFilterTls13 found tls client hello! 517
proxy/vless/encoding: XtlsPadding 517 848 0
proxy/vless/encoding: Xtls Unpadding new block0 16 content 5179 padding 0 0
proxy/vless/encoding: XtlsFilterTls13 found tls 1.3! 1163
proxy/vless/encoding: XtlsPadding 64 1219 0
proxy/vless/encoding: XtlsPadding 868 160 2
proxy/vless/encoding: XtlsWrite writeV 0 1033 0
proxy/vless/encoding: Xtls Unpadding new block0 0 content 8192 padding 0 2
app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: connection ends > proxy/vless/outbound: failed to transfer response payload > tls: oversized record received with length 30468
服务端日志
app/dispatcher: sniffed domain: play-fe.googleapis.com
app/dispatcher: default route for tcp:play-fe.googleapis.com:443
proxy/freedom: opening connection to tcp:play-fe.googleapis.com:443
transport/internet/tcp: dialing TCP to tcp:play-fe.googleapis.com:443
accepted tcp:216.58.220.110:443 [direct]
proxy/vless/encoding: XtlsFilterTls13 found tls 1.3! 333
proxy/vless/encoding: XtlsPadding 333 760 0
proxy/vless/encoding: Xtls Unpadding new block0 0 content 74 padding 828 0
proxy/vless/encoding: Xtls Unpadding new block0 0 content 98 padding 952 2
proxy/vless/encoding: XtlsRead readV
proxy/vless/encoding: XtlsPadding 866 36 2
proxy/vless/encoding: XtlsWrite writeV 0 907 0
proxy/vless/inbound: firstLen = 66
proxy/vless/inbound: received request for udp:8.8.8.8:53
app/dispatcher: default route for udp:8.8.8.8:53
proxy/freedom: opening connection to udp:8.8.8.8:53
accepted udp:8.8.8.8:53 [direct]
proxy/vless/inbound: firstLen = 1186
proxy/vless/inbound: received request for tcp:142.250.199.106:443
proxy/vless/encoding: Xtls Unpadding new block0 16 content 517 padding 746 0
proxy/vless/encoding: XtlsFilterTls13 found tls client hello! 517
端传媒app不可用
客户端日志
app/dispatcher: sniffed domain: api.theinitium.com
app/dispatcher: taking detour [proxy] for [tcp:api.theinitium.com:443]
transport/internet/tcp: dialing TCP to tcp:my_vps_ip:443
proxy/vless/outbound: tunneling request to tcp:52.221.46.214:443 via my_vps_ip:443
proxy/vless/encoding: XtlsFilterTls13 found tls client hello! 517
proxy/vless/encoding: XtlsPadding 517 426 0
proxy/vless/encoding: Xtls Unpadding new block0 16 content 137 padding 829 0
proxy/vless/encoding: XtlsFilterTls13 found tls 1.2! 137
proxy/vless/encoding: XtlsPadding 51 1040 0
proxy/vless/encoding: XtlsPadding 429 788 1
proxy/vless/encoding: Xtls Unpadding new block0 0 content 8192 padding 0 1
服务端日志
app/dispatcher: sniffed domain: api.theinitium.com
app/dispatcher: default route for tcp:api.theinitium.com:443
proxy/freedom: opening connection to tcp:api.theinitium.com:443
transport/internet/tcp: dialing TCP to tcp:api.theinitium.com:443
accepted tcp:52.221.46.214:443 [direct]
proxy/vless/encoding: XtlsFilterTls13 found tls 1.2! 137
proxy/vless/encoding: XtlsPadding 137 829 0
proxy/vless/encoding: Xtls Unpadding new block0 0 content 51 padding 1040 0
proxy/vless/encoding: Xtls Unpadding new block0 0 content 429 padding 788 1
proxy/vless/encoding: XtlsPadding 8192 0 1
proxy/vless/inbound: firstLen = 1186
proxy/vless/inbound: received request for tcp:185.199.108.133:443
proxy/vless/encoding: Xtls Unpadding new block0 16 content 190 padding 1106 0
proxy/vless/encoding: XtlsFilterTls13 found tls client hello! 190
感谢报告 你截取的日志非常有用 定位问题的是当 buffer 达到 8192 的时候打包逻辑有问题 下个版本会修复
感谢报告 你截取的日志非常有用 定位问题的是当 buffer 达到 8192 的时候打包逻辑有问题 下个版本会修复
大佬,等你发力啊。期待稳定版
@yuhan6665 תודה אתה
感谢报告 你截取的日志非常有用 定位问题的是当 buffer 达到 8192 的时候打包逻辑有问题 下个版本会修复
请utls开始就考虑一下支持动态端口
https://github.com/XTLS/Xray-core/issues/630
感谢报告 你截取的日志非常有用 定位问题的是当 buffer 达到 8192 的时候打包逻辑有问题 下个版本会修复
请utls开始就考虑一下支持动态端口
#630
实际上被封端口就是gfw的警告了,动态端口只会导致ip被ban,要是开utls还是被封端口,我觉得你得考虑换配置了
@kireiyume 不如考虑一下换机器
感谢报告 你截取的日志非常有用 定位问题的是当 buffer 达到 8192 的时候打包逻辑有问题 下个版本会修复
请utls开始就考虑一下支持动态端口 #630
实际上被封端口就是gfw的警告了,动态端口只会导致ip被ban,要是开utls还是被封端口,我觉得你得考虑换配置了
你根本不明白动态端口的作用,围墙对单端口通过流量大小特别关注,目前使用vmess动态端口,几乎没被封过端口,要是固定端口用不多久就被关注,你可以不用,但不要以自己环境为中心
8192 这个问题应该在 v1.6.4 修好了 如果遇到其它问题导致 TLS 握手失败 欢迎大家再发详细 issue 我们会继续改进
@yuhan6665 我提出的这两个问题,新版本1.6.4都已完美解决
感谢报告 你截取的日志非常有用 定位问题的是当 buffer 达到 8192 的时候打包逻辑有问题 下个版本会修复
请utls开始就考虑一下支持动态端口 #630
实际上被封端口就是gfw的警告了,动态端口只会导致ip被ban,要是开utls还是被封端口,我觉得你得考虑换配置了
你根本不明白动态端口的作用,围墙对单端口通过流量大小特别关注,目前使用vmess动态端口,几乎没被封过端口,要是固定端口用不多久就被关注,你可以不用,但不要以自己环境为中心
@yuhan6665 我也建议加入动态端口。今天又一个1001端口被封
@yuhan6665 我提出的这两个问题,新版本1.6.4都已完美解决
请问你用的是v2rayng吗?我1.7.34目前还是不行,有什么特殊配置吗?
@yuhan6665 我提出的这两个问题,新版本1.6.4都已完美解决
请问你用的是v2rayng吗?我1.7.34目前还是不行,有什么特殊配置吗?
是,没有特殊配置
@yuhan6665 我提出的这两个问题,新版本1.6.4都已完美解决
请问你用的是v2rayng吗?我1.7.34目前还是不行,有什么特殊配置吗?
是不是分流/阻止了cn流量,在那条规则之前给geosite:google打tag放行就行
@yuhan6665 我提出的这两个问题,新版本1.6.4都已完美解决
请问你用的是v2rayng吗?我1.7.34目前还是不行,有什么特殊配置吗?
是,没有特殊配置
你要发你vps端配置,ng里怎么设置的,就清楚,其它人没遇到了,不是程序app的bug,要说清楚才能帮你分析,不然全靠猜,帮不上。
@yuhan6665 我提出的这两个问题,新版本1.6.4都已完美解决
请问你用的是v2rayng吗?我1.7.34目前还是不行,有什么特殊配置吗?
是,没有特殊配置
你要发你vps端配置,ng里怎么设置的,就清楚,其它人没遇到了,不是程序app的bug,要说清楚才能帮你分析,不然全靠猜,帮不上。
好的,我server上基于x-ui创建了2个协议,一个vless+tls+ws,一个vision。在ng同样配置的情况下,前者能下载更新play store,vision就一直卡在等待中。
服务端配置如下。
{
"log": null,
"routing": {
"domainStrategy": "IPIfNonMatch",
"domainMatcher": "hybrid",
"rules": [
{
"inboundTag": ["api"],
"outboundTag": "api",
"type": "field"
},
{
"ip": ["geoip:cn", "geoip:private"],
"outboundTag": "blockedByIp",
"type": "field"
},
{
"type": "field",
"domain": ["geosite:category-ads-all", "geosite:cn"],
"outboundTag": "blockedByDomain"
},
{
"outboundTag": "blocked",
"protocol": ["bittorrent"],
"type": "field"
}
]
},
"dns": {
"hosts": {
"dns.google": ["8.8.8.8", "8.8.4.4"],
"dns.pub": "119.29.29.29",
"dns.alidns.com": "223.5.5.5"
},
"servers": [
{
"address": "https://1.1.1.1/dns-query",
"domains": ["geosite:geolocation-!cn", "geosite:google@cn"],
"expectIPs": ["geoip:!cn"]
},
"1.1.1.1",
{
"address": "localhost",
"skipFallback": true
}
],
"queryStrategy": "UseIP"
},
"inbounds": [
{
"listen": "127.0.0.1",
"port": 62789,
"protocol": "dokodemo-door",
"settings": {
"address": "127.0.0.1"
},
"streamSettings": null,
"tag": "api",
"sniffing": null
},
{
"listen": null,
"port": 21452,
"protocol": "vless",
"settings": {
"clients": [
{
"id": "e674c982-8fd7-4e24-90a9-96ed5f6160d8",
"email": "[email protected]",
"flow": ""
}
],
"decryption": "none",
"fallbacks": []
},
"streamSettings": {
"network": "ws",
"security": "tls",
"tlsSettings": {
"serverName": "xxxxxxxxxxxx",
"minVersion": "1.2",
"maxVersion": "1.3",
"cipherSuites": "",
"certificates": [
{
"certificateFile": "/root/cert/fullchain.cer",
"keyFile": "/root/cert/xxxxxxxxxxxx.key"
}
],
"alpn": ["h2", "http/1.1"]
},
"wsSettings": {
"path": "/bwg-jp",
"headers": {},
"acceptProxyProtocol": false
}
},
"tag": "inbound-21452",
"sniffing": {
"enabled": true,
"destOverride": ["http", "tls"]
}
},
{
"listen": null,
"port": 11331,
"protocol": "vless",
"settings": {
"clients": [
{
"id": "728b9199-8c9a-46c3-d5b5-621270a5bdc1",
"email": "[email protected]",
"flow": "xtls-rprx-vision"
}
],
"decryption": "none",
"fallbacks": []
},
"streamSettings": {
"network": "tcp",
"security": "tls",
"tlsSettings": {
"serverName": "xxxxxxxxxxxx",
"certificates": [
{
"certificateFile": "/root/cert/fullchain.cer",
"keyFile": "/root/cert/xxxxxxxxxxxx.key"
}
],
"alpn": ["h2", "http/1.1"]
},
"tcpSettings": {
"header": {
"type": "none"
},
"acceptProxyProtocol": false
}
},
"tag": "inbound-11331",
"sniffing": {
"enabled": true,
"destOverride": ["http", "tls"]
}
}
],
"outbounds": [
{
"protocol": "freedom",
"settings": {}
},
{
"protocol": "blackhole",
"settings": {
"response": {
"type": "http"
}
},
"tag": "blocked"
},
{
"protocol": "blackhole",
"settings": {
"response": {
"type": "http"
}
},
"tag": "blockedByIp"
},
{
"protocol": "blackhole",
"settings": {
"response": {
"type": "http"
}
},
"tag": "blockedByDomain"
}
],
"transport": null,
"policy": {
"levels": {
"0": {
"handshake": 4,
"connIdle": 300,
"uplinkOnly": 2,
"downlinkOnly": 5,
"statsUserUplink": false,
"statsUserDownlink": false,
"bufferSize": 4
}
},
"system": {
"statsInboundDownlink": true,
"statsInboundUplink": true
}
},
"api": {
"services": ["HandlerService", "LoggerService", "StatsService"],
"tag": "api"
},
"stats": {},
"reverse": null,
"fakeDns": null
}
ng里也都是默认配置,没做自定义规则,预定义规则是绕过局域网及大陆地址。也没做分流,请帮忙看看
谢谢~