reality被封
#5494
Replies: 9 comments 20 replies
|
服务端的xray内核版本现在看是25.1.8,被墙的时候是那个版本忘记了,我好像被墙过后更新了一次,不过每隔一个月左右都会更一下内核,所以被墙时候的版本即便不是25.1.8也不会比现在差太多 |
0 replies
|
去讨论区讨论吧 |
0 replies
|
服务端禁用了回国流量么? |
4 replies
|
昨晚刚被封来报个到,我是vless+reality,看来墙又加高了 |
5 replies
0 replies
|
另外看起来端口号也不是特别常用的443?实践中一般建议选择443,不要选择比较高的那种看起来就很奇怪的 |
1 reply
|
我的reality似乎从1月29日开始被封锁,之前一直用xtls-vision没遇到啥问题,最近用起来了reality,不过每天会看看youtube视频,内容没有敏感的,x都不太看,也不知道有啥特征还是怎么 |
8 replies
anytls加reality不行吗 |
2 replies
|
@sept5920 服务器上搭别的服务了、开别的协议了吗?31305挂了一个站点还是啥也没有? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
reality被封,整个ip加上22端口全部被墙,推测是特征问题,想和大家讨论一下经验
服务端使用mack的一键脚本搭建:VLESS+Reality+uTLS+Vision,开启了bbr+fq
以下是配置文件:
{
"inbounds": [
{
"port": 19911,
"protocol": "vless",
"tag": "VLESSReality",
"settings": {
"clients": [
{
"id": "b742e351-baea-4b24-baaf-c7c961912ef3",
"email": "b742e351-vless_reality_vision",
"flow": "xtls-rprx-vision"
}
],
"decryption": "none",
"fallbacks":[
{
"dest": "31305",
"xver": 1
}
]
},
"streamSettings": {
"network": "tcp",
"security": "reality",
"realitySettings": {
"show": false,
"dest": "www.icloud.com:443",
"xver": 0,
"serverNames": [
"www.icloud.com"
],
"privateKey": "0LVJKT5EauQ-d0TNbO3qatlyAiuHPR53TwGe5hD2gxk",
"publicKey": "AViQKpOY835HPgMMyjYdgvJX2EzbF4TAjuXbJhzMJh0",
"maxTimeDiff": 70000,
"shortIds": [
"",
"6ba85179e30d4fc2"
]
}
}
}
]
客户端是openclash和手机clash内核版本是1.19.17
以下是客户端配置文件:
proxies:
server: 0.0.0.0
type: vless
port: 19911
uuid: b742e351-baea-4b24-baaf-c7c961912ef3
network: tcp
servername: www.icloud.com
flow: xtls-rprx-vision
udp: true
tls: true
All reactions