Xray-core
Xray-core copied to clipboard
Xray, Penetrates Everything. Also the best v2ray-core. Where the magic happens. An open platform for various uses.
配置如下的路由信息,确保所有链接都是直连: [ { "port": "0-65535", "inboundTag": [], "outboundTag": "direct", "enabled": true } ] 在浏览器设置好xray-core的http代理地址: 并配置好设置开启ECH后,访问如下ECH测试网站: https://tls-ech.dev/ https://defo.ie/ech-check.php 结果都显示没有使用ECH,不知道为何过了一到手后就没法使用ECH了? 完整配置: ``` { "policy": { "system": { "statsOutboundUplink": true, "statsOutboundDownlink": true }...
在配置未做改动的情况下,XRay 开始出现崩溃现象。 每次崩溃的日志都一样,只是 `slice bounds out of range [1158:0]` 中的数字有所不同。 ``` Sep 05 11:30:42 xray[824]: panic: runtime error: slice bounds out of range [1158:0] Sep 05 11:30:42 xray[824]: goroutine 1328675...
这是服务器端配置文件,我这边反复测试过,只要两者同时监听443端口,quic就不能用,虽然启动正常,查看端口监听也是一个tcp 443和一个udp 443,但它就是用不了,但是只要把quic改个端口,quic就可以用 ```json { "log": { "access": "/var/log/xray/access.log", "error": "/var/log/xray/error.log", "loglevel": "warning", "dnsLog": false }, "api": { "tag": "api", "services": [ "HandlerService", "LoggerService", "StatsService" ] }, "dns": { "hosts":...
quic
大佬,考不考虑换成quic bbr
i have 3 servers with running same configuration, after 2-3 month per today one of servers can't connected to all gRPC. access.log ``` 2022/08/15 07:54:32 162.158.162.161:16652 rejected proxy/trojan: not trojan...
使用场景:Android 手机,透明代理由 Magisk 模块 [Xray4Magisk](https://github.com/Asterisk4Magisk/Xray4Magisk) 提供 以下配置文件为了便于说明做了一些简化 DNS 配置,!cn 域名使用 fakedns,cn 则为 localhost "dns": { "servers": [ { "address": "fakedns", "domains": ["geosite:geolocation-!cn"] }, { "address": "localhost", "domains": ["geosite:cn", "geosite:geolocation-cn"] }...
信息源是: https://github.com/net4people/bbs/issues/129 大规模封锁现象指: 自北京时间2022年10月3日起,超过一百名用户报告他们至少有一台基于TLS的翻墙服务器被封锁了。被封锁的服务器使用的协议包括了[trojan](https://github.com/trojan-gfw/trojan),[Xray](https://github.com/XTLS/Xray-core),[V2Ray TLS+Websocket](https://www.v2fly.org/config/transport/websocket.html),[VLESS](https://www.v2fly.org/config/protocols/vless.html),以及[gRPC](https://www.v2fly.org/config/transport/grpc.html)。我们还未收到任何[naiveproxy](https://github.com/klzgrad/naiveproxy)被封锁的消息。 当前“结论”: 基于以上信息,我们推测(但还未进行实证性的测量),这些封锁可能与翻墙软件客户端发出的[Clienthello指纹](https://tlsfingerprint.io/)相关。开发者们或许可以考虑采用[uTLS](https://github.com/refraction-networking/utls)。这个[论文阅读小组](https://github.com/net4people/bbs/issues/54),[这篇总结](https://gfw.report/blog/v2ray_weaknesses/zh/#%E7%8B%AC%E7%89%B9%E7%9A%84tls-clienthello%E6%8C%87%E7%BA%B9),以及[这篇博文](https://zhufan.net/2022/06/18/tls%E6%8F%A1%E6%89%8B%E6%8C%87%E7%BA%B9%E6%A3%80%E6%B5%8B%E6%81%B6%E6%84%8F%E8%BD%AF%E4%BB%B6%E6%B5%81%E9%87%8F/)都是关于TLS指纹的,也许会有帮助。 请问xray这边是否需要做针对性的调整?
If more than 5 clients are simultaneously connected for a few hours (any devices, such as Windows, Android, iOS) the GFW will block the Public ipv4 address. 如果超过 5 个客户端同时连接几个小时(任何设备,例如...
I'm testing xray-core performance now. when I want to try socks5 protocol with xtls. Happend the flowing error : `Failed to start: main: failed to load config files: [xxxx.json] >...
详情见:https://github.com/v2fly/v2ray-core/issues/2054 可以按照[这个PR](https://github.com/v2fly/v2ray-core/pull/2032)提供的方法修复漏洞。