-
Notifications
You must be signed in to change notification settings - Fork 738
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
用Websocket+TLS+Web方式搭建节点不到一天被干掉了 #98
Comments
现在GFW会阻断SSL流量,你反而直接vmess+ws会特别抗墙,套一层SSL会导致SNI流量特征问题直接拦截() |
你为啥要用/v2ray这个路径?
换个没规律的路径。
我https, websocket+vmess跑了4, 5年了。多台服务器,没一台被封。
wuchen4588 ***@***.***> 于 2024年6月18日周二 20:00写道:
… 现在GFW会阻断SSL流量,你反而直接vmess+ws会特别抗墙,套一层SSL会导致SNI流量特征问题直接拦截()
—
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPI3UKQDYL4F3A2MTBRD2LZIAON7AVCNFSM6AAAAABIQDN2I2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZVHEZDSNBVGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
改成了一个看起来很正常的路径,然后套了一层openvpn,现在暂时是正常能用的状态,就是速度有点感人。。。 |
如题,vmess + websocket的节点,用 nginx + https 反代,结果不到一天就访问不了了,而且因为nginx设置的路径是/ray,结果就是 域名会出现nginx的欢迎页, 域名/ray 是无法访问此页。
这种情况是正常的吗?
The text was updated successfully, but these errors were encountered: