Xray-core
Xray-core copied to clipboard
Published
20 hours ago •
XTLS
XTLS
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 的时候打包逻辑有问题 下个版本会修复
请utls开始就考虑一下支持动态端口
https://github.com/XTLS/Xray-core/issues/630
感谢报告 你截取的日志非常有用 定位问题的是当 buffer 达到 8192 的时候打包逻辑有问题 下个版本会修复
请utls开始就考虑一下支持动态端口
#630
实际上被封端口就是gfw的警告了，动态端口只会导致ip被ban，要是开utls还是被封端口，我觉得你得考虑换配置了
感谢报告 你截取的日志非常有用 定位问题的是当 buffer 达到 8192 的时候打包逻辑有问题 下个版本会修复
请utls开始就考虑一下支持动态端口 #630
实际上被封端口就是gfw的警告了，动态端口只会导致ip被ban，要是开utls还是被封端口，我觉得你得考虑换配置了
你根本不明白动态端口的作用，围墙对单端口通过流量大小特别关注，目前使用vmess动态端口，几乎没被封过端口，要是固定端口用不多久就被关注，你可以不用，但不要以自己环境为中心