A Xray backend framework that can easily support many panels. 一个基于Xray的后端框架,支持V2ay,Trojan,Shadowsocks协议,极易扩展,支持多面板对接

XRayR

A Xray backend framework that can easily support many panels.

一个基于Xray的后端框架,支持V2ay,Trojan,Shadowsocks协议,极易扩展,支持多面板对接。

如果您喜欢本项目,可以右上角点个star+watch,持续关注本项目的进展。

免责声明

本项目只是本人个人学习开发并维护,本人不保证任何可用性,也不对使用本软件造成的任何后果负责。

特点

  • 永久开源且免费。
  • 支持V2ray,Trojan, Shadowsocks多种协议。
  • 支持Vless和XTLS等新特性。
  • 支持单实例对接多面板、多节点,无需重复启动。
  • 支持限制在线IP
  • 支持节点端口级别、用户级别限速。
  • 配置简单明了。
  • 修改配置自动重启实例。
  • 方便编译和升级,可以快速更新核心版本, 支持Xray-core新特性。

TODO

  • 在线用户统计和限制
  • 限速实现
  • 审计规则
  • 对接ProxyPanel
  • 对接v2board

功能介绍

功能 v2ray trojan shadowsocks
获取节点信息
获取用户信息
用户流量统计
服务器信息上报
自动申请tls证书
自动续签tls证书
在线人数统计
在线用户限制
审计规则 TODO TODO TODO
节点端口限速
按照用户限速

支持前端

前端 v2ray trojan shadowsocks
sspanel-uim √ (Shadowsocks - V2Ray-Plugin)
ProxyPanel TODO TODO TODO
v2board TODO TODO TODO

Thanks

Licence

Mozilla Public License Version 2.0

Telgram

XrayR后端讨论

XrayR通知

下载并使用

  1. 在此处,根据自身系统选择合适的版本:Release
  2. 解压压缩包,之后运行:./XrayR -config config.yml

编译并使用

  1. go 1.16.0
  2. 依次运行
git clone https://github.com/XrayR-project/XrayR
cd XrayR/main
go mod tidy
go build -o XrayR -ldflags "-s -w"
./XrayR -config config.yml

配置文件

  1. cp config.yml.example config.yml
  2. nano config.yml

配置文件基本格式,Nodes下可以同时添加多个面板,多个节点配置信息,只需添加相同格式的Nodes item即可。

Log:
  Level: debug # Log level: none, error, warning, info, debug 
  AccessPath: # ./access.Log
  ErrorPath: # ./error.log
Nodes:
  -
    PanelType: "SSpanel" # Panel type: SSpanel
    ApiConfig:
      ApiHost: "http://127.0.0.1:667"
      ApiKey: "123"
      NodeID: 41
      NodeType: V2ray # Node type: V2ray, Shadowsocks, Trojan
    ControllerConfig:
      UpdatePeriodic: 60 # Time to update the nodeinfo, how many sec.
      CertConfig:
        CertMode: dns # Option about how to get certificate: none, file, http, dns
        CertDomain: "node1.test.com" # Domain to cert
        CertFile: ./cert/node1.test.com.cert # Provided if the CertMode is file
        KeyFile: ./cert/node1.test.com.key
        Provider: alidns # DNS cert provider, Get the full support list here: https://go-acme.github.io/lego/dns/
        Email: [email protected]
        DNSEnv: # DNS ENV option used by DNS provider
          ALICLOUD_ACCESS_KEY: aaa
          ALICLOUD_SECRET_KEY: bbb

前端配置

限速说明

  1. 节点限速:请在SSpanel的节点限速处填写,单位mbps。
  2. 用户限速:请在SSpanel的用户设置处填写,单位mbps。
  3. 限速值设为0,则为不限速。

V2ray

协议 支持情况
VMess tcp, tcp+tls/xtls, ws, ws+tls/xtls, h2c, h2+tls/xtls
VMessAEAD tcp, tcp+tls/xtls, ws, ws+tls/xtls, h2c, h2+tls/xtls
VLess tcp, tcp+tls/xtls, ws, ws+tls/xtls, h2c, h2+tls/xtls

SSpanel-uim 节点地址格式

IP;监听端口;alterId;(tcp或ws);(tls或xtls或不填);path=/xxx|host=xxxx.com|server=xxx.com|outside_port=xxx|enable_vless=(true或false)

alterId设为0,则自动启用VMessAEAD。

TCP示例

ip;12345;2;tcp;;server=域名
示例:1.3.5.7;12345;2;tcp;;server=hk.domain.com

tcp + tls 示例

ip;12345;2;tcp;tls;server=域名|host=域名
示例:1.3.5.7;12345;2;tcp;tls;server=hk.domain.com|host=hk.domain.com

ws示例

ip;80;2;ws;;path=/xxx|server=域名|host=CDN域名
示例:1.3.5.7;80;2;ws;;path=/v2ray|server=hk.domain.com|host=hk.domain.com

ws + tls 示例

ip;443;2;tls;ws;path=/xxx|server=域名|host=CDN域名
示例:1.3.5.7;443;2;ws;tls;path=/v2ray|server=hk.domain.com|host=hk.domain.com

中转端口

在任一配置组合后增加|outside_port=xxx,此项为用户连接端口。

示例:1.3.5.7;80;2;ws;;path=/v2ray|server=hk.domain.com|host=hk.domain.com|outside_port=12345

启用Vless (此项为实验性功能)

在任一配置组合后增加|enable_vless=true.

示例:1.3.5.7;12345;2;tcp;tls;server=hk.domain.com|host=hk.domain.com|enable_vless=true

请开启vless同时务必使用tls或者xtls。

启用xtls (此项为实验性功能)

替换tls为xtls

示例:1.3.5.7;12345;2;tcp;xtls;server=hk.domain.com|host=hk.domain.com

Trojan

协议 支持情况
Trojan

SSpanel-uim 节点地址格式

域名或IP;port=监听端口#用户连接端口|host=xx

直连示例

示例:gz.aaa.com;port=443|host=gz.aaa.com

中转示例

示例:gz.aaa.com;port=443#12345|host=hk.aaa.com

启用xtls (此项为实验性功能)

在配置后增加|enable_xtls=true.

示例:gz.aaa.com;port=443#12345|host=hk.aaa.com|enable_xtls=true

Shadowsocks

协议 支持情况 加密方法
ShadowsocksAEAD aes-128-gcm, aes-256-gcm, chacha20-poly1305

SSpanel-uim 节点地址格式

请注意,节点类型请选择:Shadowsocks - V2Ray-Plugin

域名或IP;监听端口|server=xx

Shadowsocks 示例

示例:gz.aaa.com;12345|server=gz.aaa.com
Comments
  • 交叉测试很多遍,不知道是v2board还是XrayR的问题

    交叉测试很多遍,不知道是v2board还是XrayR的问题

    ss tojan 会导致ssh频繁掉线,只要不操作 撑不过2 3分钟 已经完成以下测试 1:确保线路不丢包(ucloud 的IEPL 2:已经用L2TP连接IEPL 测试7台服务器 不掉线 且隔段时间会去每个ssh按空格确保可操作性 3:手搓xray的ss同样可以做到不掉线 且同样间隔时间按空格确保可操作性 4:v2board+XrayR+trojan或者ss 都会导致ssh频繁掉线

  • [GlobalDeviceLimitConfig] RedisDB settings do not work well[v0.8.6]

    [GlobalDeviceLimitConfig] RedisDB settings do not work well[v0.8.6]

    My two nodes config are set to different redisDB numbers, but when I check redis, they are actually stored in DB number 1

    config.yml image

    redis-cli image '141' is my test account and it should appear in redisDB 0

    If we need more log information, please reply to me. Thank you

  • Global Limit Not Works !!!

    Global Limit Not Works !!!

        I am testing it and doesn't work !!!
    

    Originally posted by @Github-Aiko in https://github.com/XrayR-project/XrayR/issues/121#issuecomment-1328220412

  •  vendor preset: disabled

    vendor preset: disabled

    XrayR.service - XrayR Service Loaded: loaded (/etc/systemd/system/XrayR.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2022-12-25 21:22:22 CST; 17min ago Main PID: 282362 (XrayR) Tasks: 6 (limit: 5817) Memory: 31.3M CGroup: /system.slice/XrayR.service └─282362 /usr/local/XrayR/XrayR -config /etc/XrayR/config.yml

    我 真的是崩溃,折腾了两个月,节点一直是黄色的,什么防火墙都关了,就是连不上,教程我都翻烂了,tg群也加了无数次都不给进去

  • 0.8.7 when use newv2board it shows some bug

    0.8.7 when use newv2board it shows some bug

    Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: 2022/12/08 07:19:28 Panel Start fialed: request https://v2.hicat.net/api/v1/server/UniProxy/config failed: { Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: "message": "\u9047\u5230\u4e86\u4e9b\u95ee\u9898\uff0c\u6211\u4eec\u6b63\u5728\u8fdb\u884c\u5904\u7406" Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: }, %!s() Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: panic: Panel Start fialed: request https://v2.hicat.net/api/v1/server/UniProxy/config failed: { Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: "message": "\u9047\u5230\u4e86\u4e9b\u95ee\u9898\uff0c\u6211\u4eec\u6b63\u5728\u8fdb\u884c\u5904\u7406" Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: }, %!s() Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: goroutine 1 [running]: Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: log.Panicf({0x317d042?, 0x0?}, {0xc000861e80?, 0xc00011d780?, 0xc00022fc10?}) Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: log/log.go:395 +0x67 Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: github.com/XrayR-project/XrayR/panel.(*Panel).Start(0xc00033bf80) Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: github.com/XrayR-project/XrayR/panel/panel.go:204 +0x5bc Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: main.main() Dec 08 07:19:28 GreenCloud.1669385429 XrayR[510]: github.com/XrayR-project/XrayR/main/main.go:97 +0x250 Dec 08 07:19:28 GreenCloud.1669385429 systemd[1]: XrayR.service: main process exited, code=exited, status=2/INVALIDARGUMENT Dec 08 07:19:28 GreenCloud.1669385429 systemd[1]: Unit XrayR.service entered failed state. Dec 08 07:19:28 GreenCloud.1669385429 systemd[1]: XrayR.service failed. ^C

  • update: refactor the global limit

    update: refactor the global limit

    fix: some log prefix

    It an enhance device limit. Redis just use to sync local ipMap. If global limit is enabled. The online report will faliure. All enabled nodes will report the device from redis.

  • Can Use V2BOARD XrayR with nginx for reverse proxy to cdn?

    Can Use V2BOARD XrayR with nginx for reverse proxy to cdn?

    hello all i need hide XrayR node behind Cloudflare and tunnel to XrayR with Server a

    v2board can support this config ? i do reverse proxy with TLS in Both Server But i get WebSocket error

    thanks

  • GlobalDeviceLimit not work 全局设备限制不生效 v0.8.7

    GlobalDeviceLimit not work 全局设备限制不生效 v0.8.7

    I upgraded XrayR to v0.8.7. After modifying according to the new sample configuration file, I found that GlobalDeviceLimit did not take effect.

    The config node1

        PanelType: "V2board"
    ....
          DeviceLimit: 1
    ....
          GlobalDeviceLimitConfig:
            Enable: true 
            RedisAddr: redis.com:6379 
            RedisPassword: passwd 
            RedisDB: 1 # Redis DB
            Timeout: 5 # Timeout for redis request
            Expiry: 60 # Expiry time (second)
    

    node2

        PanelType: "V2board"
    ....
          DeviceLimit: 1
    ....
          GlobalDeviceLimitConfig:
            Enable: true 
            RedisAddr: redis.com:6379 
            RedisPassword: passwd 
            RedisDB: 1 # Redis DB
            Timeout: 5 # Timeout for redis request
            Expiry: 60 # Expiry time (second)
    

    I tried putting them in the same or different redis DB, but the result is the same

    With such a configuration, the device limit will only take effect when two different ips connect to the same node, and if two different ips connect to different nodes, then they can connect normally without being limited.

    And I check the redis

    redis.com:6379> select 1
    redis.com:6379[1]> keys *
    .....
    1) "V2ray_127.0.0.1_54443|[email protected]|1"
    2) "1|[email protected]|1"
    .....
    redis.com:6379[1]> get V2ray_127.0.0.1_54443|[email protected]|1
    "\x82\xab1.1.1.1\xd3\x00\x00\x00\x00\x00\x00\x00`\xad2.2.2.2\xd3\x00\x00\x00\x00\x00\x00\x00`"
    redis.com:6379[1]> get 1|[email protected]|1
    "\x81\xab1.1.1.1\xd3\x00\x00\x00\x00\x00\x00\x00`"
    

    The different IPs of my two different devices appear in the key, but any one of the IPs can connect to different node to online at the same time.

    Please check if this is a problem with my configuration, thanks.

  • Global limit with L2 cache of gocache lib

    Global limit with L2 cache of gocache lib

    Hi @thank243 , I have reviewed the code and fixed a few small bugs. But, I have a few concerns for current implementation. Thus, I create a PR here to help us discuss.

    1. For now, we fully copy the Redis in local machine. Could this largely increase the RAM usage?
    2. We only update the cache every c.config.UpdatePeriodic, which could be bypassed sometimes. For instance, if we set the deviceLimit to 1, and two IPs establish connections to two nodes respectively. They are both able to connect and bypass the deviceLimit. I have added following lines to refuse the latter IP stored in redis, which could reject this IP in next cache update. But it can still connect in the first cycle. https://github.com/XrayR-project/XrayR/blob/839b15c22ca2f5c307bb388efd16f3fb6f111793/common/limiter/limiter.go#L221-L224

    To address these challenges, I implement a cache-on-demand version, which only cache the IPs from Redis on request. I create another PR for this implementation.

    What do you think about these concerns? We can make a comparison between these two implementations and merge one into the master branch.

  • 无法获取证书是什么情况,谢谢

    无法获取证书是什么情况,谢谢

    用的一件脚本 麻烦看下 谢谢

    请输入选择 [0-13]: 8 -- Logs begin at 日 2022-08-07 18:49:20 CST. -- 8月 07 18:54:32 c11-v2 systemd[1]: Started XrayR Service. 8月 07 18:54:32 c11-v2 XrayR[5424]: XrayR 0.8.1 (A Xray backend that supports many panels) 8月 07 18:54:32 c11-v2 XrayR[5424]: 2022/08/07 18:54:32 Start the panel.. 8月 07 18:54:32 c11-v2 XrayR[5424]: 2022/08/07 18:54:32 Xray Core Version: 1.5.9 8月 07 18:54:32 c11-v2 XrayR[5424]: 2022/08/07 18:54:32 No key found for account [email protected]. Generating a P256 key. 8月 07 18:54:32 c11-v2 XrayR[5424]: 2022/08/07 18:54:32 Saved key to /etc/XrayR/cert/accounts/acme-v02.api.letsencrypt.org/[email protected]/keys/[email protected] 8月 07 18:54:33 c11-v2 XrayR[5424]: 2022/08/07 18:54:33 [INFO] acme: Registering account for [email protected] 8月 07 18:54:33 c11-v2 XrayR[5424]: !!!! HEADS UP !!!! 8月 07 18:54:33 c11-v2 XrayR[5424]: Your account credentials have been saved in your Let's Encrypt 8月 07 18:54:33 c11-v2 XrayR[5424]: configuration directory at "/etc/XrayR/cert/accounts". 8月 07 18:54:33 c11-v2 XrayR[5424]: You should make a secure backup of this folder now. This 8月 07 18:54:33 c11-v2 XrayR[5424]: configuration directory will also contain certificates and 8月 07 18:54:33 c11-v2 XrayR[5424]: private keys obtained from Let's Encrypt so making regular 8月 07 18:54:33 c11-v2 XrayR[5424]: backups of this folder is ideal. 8月 07 18:54:33 c11-v2 XrayR[5424]: 2022/08/07 18:54:33 [INFO] [c1.5xxxxx.xyz] acme: Obtaining bundled SAN certificate 8月 07 18:54:33 c11-v2 XrayR[5424]: 2022/08/07 18:54:33 [INFO] [c1.5xxxxx.xyz] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz-v3/139327755396 8月 07 18:54:33 c11-v2 XrayR[5424]: 2022/08/07 18:54:33 [INFO] [c1.5xxxxx.xyz] acme: Could not find solver for: tls-alpn-01 8月 07 18:54:33 c11-v2 XrayR[5424]: 2022/08/07 18:54:33 [INFO] [c1.5xxxxx.xyz] acme: Could not find solver for: http-01 8月 07 18:54:33 c11-v2 XrayR[5424]: 2022/08/07 18:54:33 [INFO] [c1.5xxxxx.xyz] acme: use dns-01 solver 8月 07 18:54:33 c11-v2 XrayR[5424]: 2022/08/07 18:54:33 [INFO] [c1.5xxxxx.xyz] acme: Preparing to solve DNS-01 8月 07 18:54:33 c11-v2 XrayR[5424]: 2022/08/07 18:54:33 [INFO] cloudflare: new record for c1.5xxxxx.xyz, ID b40d92837d7a6db325c32d712dbe795d 8月 07 18:54:33 c11-v2 XrayR[5424]: 2022/08/07 18:54:33 [INFO] [c1.5xxxxx.xyz] acme: Trying to solve DNS-01 8月 07 18:54:33 c11-v2 XrayR[5424]: 2022/08/07 18:54:33 [INFO] [c1.5xxxxx.xyz] acme: Checking DNS record propagation using [8.8.8.8:53 8.8.4.4:53] 8月 07 18:54:35 c11-v2 XrayR[5424]: 2022/08/07 18:54:35 [INFO] Wait for propagation [timeout: 2m0s, interval: 2s] 8月 07 18:54:45 c11-v2 XrayR[5424]: 2022/08/07 18:54:45 [INFO] [c1.5xxxxx.xyz] acme: Waiting for DNS record propagation. 8月 07 18:54:57 c11-v2 XrayR[5424]: 2022/08/07 18:54:57 [INFO] [c1.5xxxxx.xyz] acme: Waiting for DNS record propagation. 8月 07 18:55:09 c11-v2 XrayR[5424]: 2022/08/07 18:55:09 [INFO] [c1.5xxxxx.xyz] acme: Waiting for DNS record propagation. 8月 07 18:55:21 c11-v2 XrayR[5424]: 2022/08/07 18:55:21 [INFO] [c1.5xxxxx.xyz] acme: Waiting for DNS record propagation. 8月 07 18:55:33 c11-v2 XrayR[5424]: 2022/08/07 18:55:33 [INFO] [c1.5xxxxx.xyz] acme: Waiting for DNS record propagation. 8月 07 18:55:45 c11-v2 XrayR[5424]: 2022/08/07 18:55:45 [INFO] [c1.5xxxxx.xyz] acme: Waiting for DNS record propagation. 8月 07 18:55:57 c11-v2 XrayR[5424]: 2022/08/07 18:55:57 [INFO] [c1.5xxxxx.xyz] acme: Waiting for DNS record propagation. 8月 07 18:56:09 c11-v2 XrayR[5424]: 2022/08/07 18:56:09 [INFO] [c1.5xxxxx.xyz] acme: Waiting for DNS record propagation. 8月 07 18:56:21 c11-v2 XrayR[5424]: 2022/08/07 18:56:21 [INFO] [c1.5xxxxx.xyz] acme: Waiting for DNS record propagation. 8月 07 18:56:33 c11-v2 XrayR[5424]: 2022/08/07 18:56:33 [INFO] [c1.5xxxxx.xyz] acme: Waiting for DNS record propagation. 8月 07 18:56:35 c11-v2 XrayR[5424]: 2022/08/07 18:56:35 [INFO] [c1.5xxxxx.xyz] acme: Cleaning DNS-01 challenge 8月 07 18:56:36 c11-v2 XrayR[5424]: 2022/08/07 18:56:36 [INFO] retry due to: acme: error: 400 :: POST :: https://acme-v02.api.letsencrypt.org/acme/authz-v3/139327755396 :: urn:ietf:params:acme:error:badNonce :: JWS has an invalid anti-replay nonce: "0002VJ5Exa3hGCg9ClonshIax5CbxNa0Y5HSup9REiui80w" 8月 07 18:56:36 c11-v2 XrayR[5424]: 2022/08/07 18:56:36 [INFO] Deactivating auth: https://acme-v02.api.letsencrypt.org/acme/authz-v3/139327755396 8月 07 18:56:36 c11-v2 XrayR[5424]: 2022/08/07 18:56:36 Could not obtain certificates: 8月 07 18:56:36 c11-v2 XrayR[5424]: error: one or more domains had a problem: 8月 07 18:56:36 c11-v2 XrayR[5424]: [c1.5xxxxx.xyz] time limit exceeded: last error: read udp [2607:f130:0:151:216:3eff:fe2d:8f76]:57894->[2606:4700:50::adf5:3a56]:53: i/o timeout 8月 07 18:56:36 c11-v2 XrayR[5424]: 2022/08/07 18:56:36 Could not obtain certificates: 8月 07 18:56:36 c11-v2 XrayR[5424]: error: one or more domains had a problem: 8月 07 18:56:36 c11-v2 XrayR[5424]: [c1.5xxxxx.xyz] time limit exceeded: last error: read udp [2607:f130:0:151:216:3eff:fe2d:8f76]:57894->[2606:4700:50::adf5:3a56]:53: i/o timeout 8月 07 18:56:36 c11-v2 XrayR[5424]: panic: Could not obtain certificates: 8月 07 18:56:36 c11-v2 XrayR[5424]: error: one or more domains had a problem: 8月 07 18:56:36 c11-v2 XrayR[5424]: [c1.5xxxxx.xyz] time limit exceeded: last error: read udp [2607:f130:0:151:216:3eff:fe2d:8f76]:57894->[2606:4700:50::adf5:3a56]:53: i/o timeout 8月 07 18:56:36 c11-v2 XrayR[5424]: goroutine 1 [running]: 8月 07 18:56:36 c11-v2 XrayR[5424]: log.Panic({0xc00054fd48?, 0xc000220a90?, 0xc00086fd78?}) 8月 07 18:56:36 c11-v2 XrayR[5424]: log/log.go:385 +0x65 8月 07 18:56:36 c11-v2 XrayR[5424]: github.com/XrayR-project/XrayR/service/controller.(*Controller).Start(0xc000220820) 8月 07 18:56:36 c11-v2 XrayR[5424]: github.com/XrayR-project/XrayR/service/controller/controller.go:68 +0x256 8月 07 18:56:36 c11-v2 XrayR[5424]: github.com/XrayR-project/XrayR/panel.(*Panel).Start(0xc000039e00) 8月 07 18:56:36 c11-v2 XrayR[5424]: github.com/XrayR-project/XrayR/panel/panel.go:192 +0x4fa 8月 07 18:56:36 c11-v2 XrayR[5424]: main.main() 8月 07 18:56:36 c11-v2 XrayR[5424]: github.com/XrayR-project/XrayR/main/main.go:92 +0x1ed 8月 07 18:56:36 c11-v2 systemd[1]: XrayR.service: main process exited, code=exited, status=2/INVALIDARGUMENT 8月 07 18:56:36 c11-v2 systemd[1]: Unit XrayR.service entered failed state. 8月 07 18:56:36 c11-v2 systemd[1]: XrayR.service failed. 8月 07 18:56:46 c11-v2 systemd[1]: XrayR.service holdoff time over, scheduling restart. 8月 07 18:56:46 c11-v2 systemd[1]: Stopped XrayR Service. 8月 07 18:56:46 c11-v2 systemd[1]: Started XrayR Service. 8月 07 18:56:46 c11-v2 XrayR[6980]: XrayR 0.8.1 (A Xray backend that supports many panels) 8月 07 18:56:46 c11-v2 XrayR[6980]: 2022/08/07 18:56:46 Start the panel..

  • 希望 XrayR 能支持一下IP证书。

    希望 XrayR 能支持一下IP证书。

    分别用XrayR 和Xray-Core 测试使用IP证书。 Xray-Core 一切正常 XrayR 日志调debug error日志输出

    2022/12/23 10:34:58 [Info] [2318022440] app/proxyman/inbound: connection ends > proxy/trojan: failed to read first request > tls: no certificates configured
    2022/12/23 10:34:58 [Info] [1126801330] app/proxyman/inbound: connection ends > proxy/trojan: failed to read first request > tls: no certificates configured
    2022/12/23 10:35:02 [Info] [3068013785] app/proxyman/inbound: connection ends > proxy/trojan: failed to read first request > tls: no certificates configured
    2022/12/23 10:35:02 [Info] [2160327210] app/proxyman/inbound: connection ends > proxy/trojan: failed to read first request > tls: no certificates configured
    2022/12/23 10:35:10 [Info] [2722141912] app/proxyman/inbound: connection ends > proxy/trojan: failed to read first request > tls: no certificates configured
    2022/12/23 10:35:10 [Info] [2370990756] app/proxyman/inbound: connection ends > proxy/trojan: failed to read first request > tls: no certificates configured
    2022/12/23 10:35:12 [Info] [2388003769] app/proxyman/inbound: connection ends > proxy/trojan: failed to read first request > tls: no certificates configured
    2022/12/23 10:35:12 [Info] [722144358] app/proxyman/inbound: connection ends > proxy/trojan: failed to read first request > tls: no certificates configured
    
  • build(deps): bump github.com/sagernet/sing from 0.1.1 to 0.1.2

    build(deps): bump github.com/sagernet/sing from 0.1.1 to 0.1.2

    Bumps github.com/sagernet/sing from 0.1.1 to 0.1.2.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Related tags
A base gui tool for xray/v2ray/hysteria/trojan-go without system proxy

A base gui tool for xray/v2ray/hysteria/trojan-go without system proxy

Dec 8, 2022
Docker-trojan-go - 使用 Go 实现的完整 Trojan 代理

使用 Go 实现的完整 Trojan 代理,兼容原版 Trojan 协议及配置文件格式。安全、高效、轻巧、易用。

Feb 13, 2022
Xray, Penetrates Everything. Also the best v2ray-core, with XTLS support. Fully compatible configuration.

Project X Project X originates from XTLS protocol, provides a set of network tools such as Xray-core and Xray-flutter. License Mozilla Public License

Jan 7, 2023
Yet another SIP003 plugin for shadowsocks, based on Xray-core

Yet another SIP003 plugin for shadowsocks, based on Xray-core Build go build Usage See command line args for advanced usages.

Jan 8, 2023
一个多功能 SSPanel 机场后端, 支持 V2Ray(Vmess), Trojan, Shadowsocks(单端口多用户)
一个多功能 SSPanel 机场后端, 支持 V2Ray(Vmess), Trojan, Shadowsocks(单端口多用户)

一个多功能 SSPanel 机场后端, 支持 V2Ray(Vmess), Trojan, Shadowsocks(单端口多用户)

Jan 3, 2023
An event driven remote access trojan for experimental purposes.

erat An event driven remote access trojan for experimental purposes. This example is very simple and leverages ssh failed login events to trigger erat

Jan 16, 2022
🚀Gev is a lightweight, fast non-blocking TCP network library based on Reactor mode. Support custom protocols to quickly and easily build high-performance servers.
🚀Gev is a lightweight, fast non-blocking TCP network library based on Reactor mode. Support custom protocols to quickly and easily build high-performance servers.

gev 中文 | English gev is a lightweight, fast non-blocking TCP network library based on Reactor mode. Support custom protocols to quickly and easily bui

Jan 6, 2023
llb - It's a very simple but quick backend for proxy servers. Can be useful for fast redirection to predefined domain with zero memory allocation and fast response.

llb What the f--k it is? It's a very simple but quick backend for proxy servers. You can setup redirect to your main domain or just show HTTP/1.1 404

Sep 27, 2022
Sep 23, 2022
many tools implemented in Golang

Go-Tools many tools implemented in Golang tools project comments abtest AB测试分流 dag_flow DAG工作流 hugo_themes Hugo主题 log_monitor 日志监控服务 pepper_cache 内存kv

Dec 12, 2021
Assanlab - JSON input data with counts on how many times you showed an ad on each individual domain

JSON input data with counts on how many times you showed an ad on each individua

Dec 31, 2021
High-performance, non-blocking, event-driven, easy-to-use networking framework written in Go, support tls/http1.x/websocket.

High-performance, non-blocking, event-driven, easy-to-use networking framework written in Go, support tls/http1.x/websocket.

Jan 8, 2023
a tcp framework which support pub/sub and request/reply

支持 事件订阅/请求回应 的的TCP通讯框架 源于 zinx 的业务定制版本 TCP 通讯框架 特点 服务端/客户端均支持订阅事件通讯. 服务端支持 Broadcast 方式发送信息到客户端. 客户端均支持 Request/Reply 方式与服务端通讯 服务端用多个worker去处理客户端的请求 目

Oct 9, 2021
Easily generate gRPC services in Go ⚡️
Easily generate gRPC services in Go ⚡️

Lile is a application generator (think create-react-app, rails new or django startproject) for gRPC services in Go and a set of tools/libraries. The p

Dec 27, 2022
Easily and securely send things from one computer to another :crocodile: :package:
Easily and securely send things from one computer to another :crocodile: :package:

This project is supported by: croc is a tool that allows any two computers to simply and securely transfer files and folders. AFAIK, croc is the only

Jan 3, 2023
Talk, easily.
Talk, easily.

Quik.do v0.1.0 talk, easily. Note: This project is heavily under development. IT IS NOT PRODUCTION READY YET. DO NOT USE IT. What Quik.do is a video c

Jan 1, 2023
Easily increment 📶 a multi-language 🔱 project version
 Easily increment 📶 a multi-language 🔱 project version

version-bump Have you ever made a mistake incrementing a project version? Do you have multiple files to update the version at? I was always forgetting

Dec 14, 2022
Switch git user easily with ssh identity.
Switch git user easily with ssh identity.

gitusr A cli tool to easily manage multiple git users and their ssh identity. Add a new git user to gitusr config. Delete a git user from gitusr confi

Aug 22, 2021