Giter Site home page Giter Site logo

ssrpanel-v2ray's Introduction

项目描述

SSRPanel的V2ray节点端

SSRPanel面板: https://github.com/ssrpanel/SSRPanel

准备

  • 先去v2ray.com熟悉一下V2ray的基本配置
  • 先去v2ray.com熟悉一下V2ray的基本配置
  • 先去v2ray.com熟悉一下V2ray的基本配置
  • 我管的是如何将V2ray连接面板，不是教你们怎么配置V2ray的
  • 我管的是如何将V2ray连接面板，不是教你们怎么配置V2ray的
  • 我管的是如何将V2ray连接面板，不是教你们怎么配置V2ray的

环境配置

安装JDK8

# ubuntu
sudo apt install openjdk-8-jdk
# centos
yum install java-1.8.0-openjdk java-1.8.0-openjdk-devel

配置V2ray

下载V2ray
在 config.json 中按自己希求修改一些的配置
(v0.0.3以上已自动下载更新)

配置SSRPanel后台

添加节点
基础信息按实际情况填写
扩展信息的服务类型选择V2ray

基础选项:

  • 额外ID (alterId)
  • 端口 (VMess协议的端口)

高级选项(不懂就不要动下面几个选项):

  • 传输协议
  • 伪装类型
  • 伪装域名
  • WS/H2路径
  • TLS

配置节点端

在 releases 页面下载编译版 修改 config.properties

几个重点配置项

  • v2ray.system (操作系统，可选linux和windows，v0.0.3以上)
  • v2ray.arch (操作系统位数，可选32和64，v0.0.3以上)
  • v2ray.grpc.port (tag为api的传入连接的端口) (v0.0.3以上自动获取)
  • v2ray.tag (VMess协议的tag)
  • v2ray.alter-id (与面板额外ID一致)
  • node.id (面板添加节点后得到的节点ID)
  • node.traffic-rate (与面板流量比例一致)

数据库配置(远程连接SSRPanel的数据库)

  • datasource.url (数据库的连接URL, 格式为 jdbc:mysql://地址:端口/数据库名称?serverTimezone=GMT%2B8)
  • datasource.username (用户名)
  • datasource.password (密码)

执行 java -jar xxxxx.jar即可

v0.0.3更新说明

  1. 自动下载和更新V2Ray，每晚0点左右检查更新
  2. config.json位置转移到了节点端下
  3. GRPC配置会自动从config.json中读取

构建

git clone https://github.com/aiyahacke/ssrpanel-v2ray.git
cd ssrpanel-v2ray
git submodule update --init --recursive
chmod +x ./mvnw
./mvnw package

ssrpanel-v2ray's People

Contributors

dependabot[bot] avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar

Forkers

supsfun uhtred009 kzhy sharpesir wusme zhanggf2010 bigrain1993 lizhongnian rabichannel tuboshu62 lcboy quniu suoyaosuoyao prentice-svg heweiye jialinjun afeigorgor manshuli chunyu-zhou axslashl zwygdnz ximliu vpn-v2ray s884812 mibusix tdickson3 omiku onfork onplus holokeholoke453 shino49 supersongssr wxpiero fallenmaple koonuz caowh725 yoyobbs dawfds chinjun 4kercc wandou911 tsiin vailin visense qingfengshini zhiqueen nmslooo ownpradise inetcoding 130185830 patrickuo hongluoluo elvischao eddycat shadowxrj hackenwu ygygee sjhfs3 ssrpaneld 8choi aiastia-shadowsocksr oxygenproxy ojbk8 evolutionboy github1-2-3 lyjspeedx skuanhdj metdu yongjie0203 lzw0128 peeliye han767 koalaskycn demons666 sgseo cracksfuck 4server hwbadmin cathy2001 linwojian zwjceo hvvy emvuys cnmars fei5seven sage-ihealth peaceanddemocracy maxwellhouse102 busanbusi yyyyy1412 stallr spiderman5408 spiderman3429 dayudaoren mrzhangshengbaba ggfvictor maxwelljun xusos zdqszt hanxianzhai

ssrpanel-v2ray's Issues

设定流量比例不计算 ,实际按照1:1

虎哥面板显示还是实际按照1:1计算.并没有按照节点的比例计算,求证过虎哥说是后端没有计算问题 . 可能需要修正此问题. ssr后端测试都是正常.

FWnhuj.png

服务端开了一天，报错了

2018/11/05 01:38:11开启的

2018/11/05 12:16:13 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 获取用户流量: USER user>>>[email protected]>>>traffic>>>uplink TRAFFIC 221174  
2018/11/05 12:16:13 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 获取用户流量: USER user>>>[email protected]>>>traffic>>>downlink TRAFFIC 1361152  
2018/11/05 12:16:13 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 获取用户流量: USER user>>>[email protected]>>>traffic>>>uplink TRAFFIC 0  
2018/11/05 12:16:13 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 获取用户流量: USER user>>>[email protected]>>>traffic>>>downlink TRAFFIC 0  
2018/11/05 12:16:13 [ERROR] cn.moegezi.v2ray.node.process.V2rayDao: 记录流量日志: USER_NUM 1 ALL_TRAFFIC 1545.24KB  
2018/11/05 12:16:13 [ERROR] cn.moegezi.v2ray.node.process.V2rayDao: 更新用户流量信息: USER_NUM 1  
2018/11/05 12:16:13 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新在线用户数: NUMBER 1  
2018/11/05 12:16:13 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新节点负载信息: LOAD 0.01 0.01 0.00

最后一次成功的记录↑

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x2a pc=0x75bc76]

goroutine 30815 [running]:
v2ray.com/core/common/mux.(*Session).NewReader(0x0, 0xc000970ab0, 0xbea7a0, 0x10bc1ed)
	/v2/src/v2ray.com/core/common/mux/session.go:148 +0x26
v2ray.com/core/common/mux.(*ServerWorker).handleStatusKeep(0xc00069a940, 0xc000bacaa0, 0xc000970ab0, 0x0, 0x0)
	/v2/src/v2ray.com/core/common/mux/server.go:148 +0x82
v2ray.com/core/common/mux.(*ServerWorker).handleFrame(0xc00069a940, 0xbf4e60, 0xc0009708d0, 0xc000970ab0, 0x0, 0x0)
	/v2/src/v2ray.com/core/common/mux/server.go:192 +0x210
v2ray.com/core/common/mux.(*ServerWorker).run(0xc00069a940, 0xbf4e60, 0xc0009708d0)
	/v2/src/v2ray.com/core/common/mux/server.go:215 +0x111
created by v2ray.com/core/common/mux.(*Server).Dispatch
	/v2/src/v2ray.com/core/common/mux/server.go:55 +0x2f4
2018/11/05 12:17:03 [INFO] cn.moegezi.v2ray.node.process.V2rayDestroyer: V2ray已停止

接下去就是v2ray报错，然后服务端也跟着关闭了。

时间错误

同步时间时发现错误 如图 修改成CST 时区吧!

FDlfCd.png

连接成功有报错

golang.org/x/net/http2.(*Framer).ReadFrame(0xc000180460, 0xc0005611c0, 0xc0005611c0, 0x0, 0x0)
golang.org/x/net/http2/frame.go:492 +0xa3
google.golang.org/grpc/internal/transport.(*http2Server).HandleStreams(0xc000185680, 0xc00017a5d0, 0xb8b3e0)
google.golang.org/grpc/internal/transport/http2_server.go:429 +0x7c
google.golang.org/grpc.(*Server).serveStreams(0xc000001c80, 0xc22100, 0xc000185680)
google.golang.org/grpc/server.go:681 +0xdd
google.golang.org/grpc.(*Server).handleRawConn.func1(0xc000001c80, 0xc22100, 0xc000185680)
google.golang.org/grpc/server.go:643 +0x43
created by google.golang.org/grpc.(*Server).handleRawConn
google.golang.org/grpc/server.go:642 +0x57e
2019/01/07 20:56:25 [ERROR] cn.moegezi.v2ray.node.process.V2rayGrpc: 添加用户失败io.grpc.StatusRuntimeException: UNAVAILABLE: Network closed for unknown reason
2019/01/07 20:56:25 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 更新用户: ADD 1 REMOVE 0
然后就退出了

数据链接SSL 如何添加选项参数

mysql'5.6以上好像如果不添加禁用或者启用ssl链接数据库参数默认都是SSL 现在需要添加SSL 选项我该怎么写呢 ?
原文:
UTC 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.

使用mkcp报错

大佬，我用mkcp出现报错，我的config.json文件是

{
"api": {
"services": [
"HandlerService",
"StatsService"
],
"tag": "api"
},
"stats": {},
"inbound": {
"port": 10088,
"protocol": "vmess",
"settings": {
"clients": []
},
"streamSettings": {
"network": "mkcp"
"kcpSettings": {
"header": {
"type": "wechat-video"
},
"uplinkCapacity": 100,
"downlinkCapacity": 100,
"tti": 50,
"writeBufferSize": 2,
"mtu": 1350,
"congestion": false,
"readBufferSize": 2
},
},
"tag": "proxy"
},
"inboundDetour": [
{
"listen": "0.0.0.0",
"port": 10086,
"protocol": "dokodemo-door",
"settings": {
"address": "0.0.0.0"
},
"tag": "api"
}
],
"log": {
"access": "./access.log",
"error": "./error.log",
"loglevel": "debug"
},
"outbound": {
"protocol": "freedom",
"settings": {}
},
"routing": {
"settings": {
"rules": [
{
"inboundTag": [
"api"
],
"outboundTag": "api",
"type": "field"
}
]
},
"strategy": "rules"
},
"policy": {
"levels": {
"1": {
"statsUserUplink": true,
"statsUserDownlink": true
}
}
}
}
您知道哪里参数出问题了吗，谢谢

服务端没有错误，就是连接不上

防火墙全开
config.json配置
{
"log": {
"access": "./access.log",
"error": "./error.log",
"loglevel": "error"
},
"api": {
"services": [
"HandlerService",
"StatsService"
],
"tag": "api"
},
"stats": {},
"inbounds": [
{
"listen": "0.0.0.0",
"port": 10086,
"protocol": "dokodemo-door",
"settings": {
"address": "0.0.0.0"
},
"tag": "api"
},
{
"tag": "proxy",
"listen": "0.0.0.0",
"port": 23333,
"protocol": "vmess",
"settings": {
"clients": [],
"disableInsecureEncryption": true,
"default": {
"level": 0,
"alterId": 233
}
},
"streamSettings": {
"network": "ws",
"wsSettings": {
"path": "/233",
"headers": {
"Host": "v2.xxx.party"
}
}
}
}
],
"outbounds": [
{
"protocol": "freedom",
"settings": {}
}
],
"routing": {
"rules": [
{
"inboundTag": [
"api"
],
"outboundTag": "api",
"type": "field"
}
]
},
"policy": {
"levels": {
"1": {
"statsUserUplink": true,
"statsUserDownlink": true
}
}
}
}

config

操 作 系 统 (windows,linux)

v2ray.system=linux

系 统 位 数 (32,64)

v2ray.arch=64

协 议 标 签

v2ray.tag=proxy

额 外 ID

v2ray.alter-id=233

用 户 等 级

v2ray.level=1

节 点 配 置

节 点 ID

node.id=10

检 查 时 间 (秒 )

node.check-rate=60

流 量 比 例

node.traffic-rate=1.0

Ubuntu 14下载v2ray-core文件失败

启动服务失败，下载v2ray-core失败

 |  \/  (_)___  __ _| | ____ _  | \ | | ___| |_
 | |\/| | / __|/ _` | |/ / _` | |  \| |/ _ \ __|
 | |  | | \__ \ (_| |   < (_| | | |\  |  __/ |_
 |_|  |_|_|___/\__,_|_|\_\__,_| |_| \_|\___|\__|

2019/01/09 06:41:49 [INFO] cn.moegezi.v2ray.node.process.V2rayUpdate: 开始检测V2Ray更新  
2019/01/09 06:41:51 [INFO] cn.moegezi.v2ray.node.process.V2rayUpdate: 检测到新版本V2Ray: v4.10.0  
2019/01/09 06:41:51 [INFO] cn.moegezi.v2ray.node.process.V2rayUpdate: 开始下载: https://github.com/v2ray/v2ray-core/releases/download/v4.10.0/v2ray-linux-64.zip  
2019/01/09 06:41:51 [INFO] cn.moegezi.v2ray.node.process.V2rayUpdate: 更新失败:   
javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
        at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1944)
        at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1939)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1938)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1508)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263)
        at cn.moegezi.v2ray.node.utils.DownloadUtil.download(DownloadUtil.java:24)
        at cn.moegezi.v2ray.node.process.V2rayUpdate.checkUpdate(V2rayUpdate.java:55)
        at cn.moegezi.v2ray.node.process.V2rayTimingThread.lambda$start$0(V2rayTimingThread.java:32)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
        at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
        at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
        at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1921)
        at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1904)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1420)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397)
        at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
        at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection
.java:185)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
        at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:3000)
        at java.net.URLConnection.getHeaderFieldLong(URLConnection.java:629)
        at java.net.URLConnection.getContentLengthLong(URLConnection.java:501)
        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getContentLengthLong(HttpsURLConnectionImpl.java:411)
        at cn.moegezi.v2ray.node.utils.DownloadUtil.download(DownloadUtil.java:23)
        ... 9 more
Caused by: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trus
tAnchors parameter must be non-empty
        at sun.security.validator.PKIXValidator.<init>(PKIXValidator.java:91)
        at sun.security.validator.Validator.getInstance(Validator.java:179)
        at sun.security.ssl.X509TrustManagerImpl.getValidator(X509TrustManagerImpl.java:312)
        at sun.security.ssl.X509TrustManagerImpl.checkTrustedInit(X509TrustManagerImpl.java:171)
        at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:184)
        at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
        at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)
        at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
        at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1052)
        at sun.security.ssl.Handshaker.process_record(Handshaker.java:987)
        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1072)
        at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413)
        ... 19 more
Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
        at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
        at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
        at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
        at sun.security.validator.PKIXValidator.<init>(PKIXValidator.java:89)
        ... 31 more

编译错误

Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-compat/3.0/maven-compat-3.0.jar (285 kB at 259 kB/s)
Downloading from central: https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/3.5.1/protoc-3.5.1.pom
Downloaded from central: https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/3.5.1/protoc-3.5.1.pom (4.5 kB at 151 kB/s)
Downloading from central: https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/3.5.1/protoc-3.5.1-linux-x86_64.exe
Downloaded from central: https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/3.5.1/protoc-3.5.1-linux-x86_64.exe (4.4 MB at 2.6 MB/s)
[INFO] Compiling 47 proto file(s) to /root/ssrpanel-v2ray/target/generated-sources/protobuf/java
[ERROR] PROTOC FAILED: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/websocket/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/tls/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/tcp/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/kcp/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/domainsocket/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/http/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/headers/noop/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/headers/wechat/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/headers/utp/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/headers/tls/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/headers/srtp/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/headers/wireguard/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/headers/http/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/internet/udp/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/transport/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/commander/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/policy/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/dns/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/log/command/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/log/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/router/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/dispatcher/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/stats/command/command.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/stats/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/proxyman/command/command.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/app/proxyman/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/proxy/mtproto/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/proxy/freedom/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/proxy/blackhole/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/proxy/shadowsocks/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/proxy/socks/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/proxy/vmess/outbound/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/proxy/vmess/inbound/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/proxy/vmess/account.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/proxy/dokodemo/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/proxy/http/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/common/log/log.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/common/net/network.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/common/net/destination.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/common/net/address.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/common/net/port.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/common/serial/typed_message.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/common/protocol/server_spec.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/common/protocol/user.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/common/protocol/headers.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[ERROR] /root/ssrpanel-v2ray/src/main/proto/v2ray.com/core/config.proto [0:0]: /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/ssrpanel-v2ray/target/protoc-plugins/protoc-3.5.1-linux-x86_64.exe)

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 25.989 s
[INFO] Finished at: 2018-10-26T15:38:08+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile (default) on project ssrpanel-v2ray: protoc did not exit cleanly. Review output for more information. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

错误问题 统计问题 求解? log看不到更多信息

2018/12/10 11:17:10 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新在线用户数: NUMBER 0
2018/12/10 11:17:10 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新节点负载信息: LOAD 0.03 0.02 0.00
2018/12/10 11:18:10 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 获取用户流量: USER user>>>[email protected]>>>traffic>>>uplink TRAFFIC 4225
2018/12/10 11:18:10 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 获取用户流量: USER user>>>[email protected]>>>traffic>>>downlink TRAFFIC 20731
2018/12/10 11:18:10 [ERROR] cn.moegezi.v2ray.node.process.V2rayDao: 记录流量日志: USER_NUM 1 ALL_TRAFFIC 24.37KB
2018/12/10 11:18:10 [ERROR] cn.moegezi.v2ray.node.process.V2rayDao: 更新用户流量信息: USER_NUM 1
2018/12/10 11:18:10 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新在线用户数: NUMBER 1
2018/12/10 11:18:10 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新节点负载信息: LOAD 0.01 0.02 0.00

dalao,遇到这个问题是什么原因呢

[root@VM_81_0_centos ssrpanel-v2ray]# java -jar ssrpanel-v2ray-0.0.2.jar

| / ()__ __ | | ____ _ | \ | | | |
| |/| | / __|/ | |/ / _ | | | |/ _ \ _|
| | | | _ \ (| | < (| | | |\ | _/ |
|| |||/_,||__,| || _|___|__|

V2Ray 3.49 (die Commanderin) 20181025
A unified platform for anti-censorship.
2018/10/30 21:20:50 [INFO] cn.moegezi.v2ray.node.process.V2rayDestroyer: V2ray已启动
Failed to start v2ray.com/core/app/proxyman/inbound: failed to listen TCP on 10087 > v2ray.com/core/transport/internet: failed to listen on address: 0.0.0.0:10087 > listen tcp 0.0.0.0:10087: bind: address already in use
2018/10/30 21:20:50 [INFO] com.zaxxer.hikari.HikariDataSource: HikariPool-1 - Starting...
2018/10/30 21:20:51 [INFO] com.zaxxer.hikari.HikariDataSource: HikariPool-1 - Start completed.
2018/10/30 21:20:51 [INFO] cn.moegezi.v2ray.node.process.V2rayDestroyer: V2ray已停止
2018/10/30 21:20:51 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新在线用户数: NUMBER 0
2018/10/30 21:20:51 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新节点负载信息: LOAD 0.17 0.18 0.15
2018/10/30 21:20:51 [ERROR] cn.moegezi.v2ray.node.process.V2rayGrpc: 添加用户失败io.grpc.StatusRuntimeException: UNAVAILABLE: Channel shutdown invoked
2018/10/30 21:20:51 [ERROR] cn.moegezi.v2ray.node.process.V2rayGrpc: 添加用户失败io.grpc.StatusRuntimeException: UNAVAILABLE: Channel shutdown invoked
2018/10/30 21:20:51 [ERROR] cn.moegezi.v2ray.node.process.V2rayGrpc: 添加用户失败io.grpc.StatusRuntimeException: UNAVAILABLE: Channel shutdown invoked
2018/10/30 21:20:51 [ERROR] cn.moegezi.v2ray.node.process.V2rayGrpc: 添加用户失败io.grpc.StatusRuntimeException: UNAVAILABLE: Channel shutdown invoked
2018/10/30 21:20:51 [ERROR] cn.moegezi.v2ray.node.process.V2rayGrpc: 添加用户失败io.grpc.StatusRuntimeException: UNAVAILABLE: Channel shutdown invoked
2018/10/30 21:20:51 [ERROR] cn.moegezi.v2ray.node.process.V2rayGrpc: 添加用户失败io.grpc.StatusRuntimeException: UNAVAILABLE: Channel shutdown invoked
2018/10/30 21:20:51 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 更新用户: ADD 6 REMOVE 0

接面板客户端连接『403 Forbidden > websocket: bad handshake』，求大神普度

应用场景：一个被墙的服务器，ws+tls协议，用cloudflare的免费中转
该服务器使用233boy一键脚本安装的v2ray使用很正常，油管速度也很好，但使用接入ssrpanel面板后出现如下错误：

2018/12/11 21:18:11 [Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: failed to find an available destination > v2ray.com/core/common/retry: [v2ray.com/core/transport/internet/websocket: failed to dial WebSocket > v2ray.com/core/transport/internet/websocket: failed to dial to (wss://xx.xxx.xyz/down): 403 Forbidden > websocket: bad handshake] > v2ray.com/core/common/retry: all retry attempts failed

客户端出错误的时候，服务端日志未出现错误：

V2Ray 4.8.0 (Po) 20181206
A unified platform for anti-censorship.
2018/12/11 21:23:12 [INFO] cn.moegezi.v2ray.node.process.V2rayDestroyer: V2ray已启动  
2018/12/11 21:23:12 [INFO] com.zaxxer.hikari.HikariDataSource: HikariPool-1 - Starting...  
2018/12/11 21:23:15 [INFO] com.zaxxer.hikari.HikariDataSource: HikariPool-1 - Start completed.  
2018/12/11 21:23:19 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新在线用户数: NUMBER 0  
2018/12/11 21:23:19 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新节点负载信息: LOAD 2.02 1.97 1.46  
2018/12/11 21:23:20 [WARN] io.netty.util.internal.MacAddressUtil: Failed to find a usable hardware address from the network interfaces; using random bytes: 13:7b:13:77:e6:71:23:18  
2018/12/11 21:23:43 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 更新用户: ADD 395 REMOVE 0  
2018/12/11 21:24:29 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新在线用户数: NUMBER 0

  1. 面板配置

  2. 服务端配置

  • caddy反代
xx.xxx.xyz {
    tls [email protected]
    gzip
timeouts none
    proxy / https://xx.vip {
        without /down
    }
    proxy /down 127.0.0.1:10086 {
        without /down  //最终确认，这个配置有问题，去掉
        websocket
    }
}
  • config.json
{
  "log": {
    "access": "./access.log",
    "error": "./error.log",
    "loglevel": "debug"
  },
  "api": {
    "services": [
      "HandlerService",
      "StatsService"
    ],
    "tag": "api"
  },
  "stats": {},
  "inbound": {
    "port": 10086,
    "protocol": "vmess",
    "settings": {
      "udp": true,
      "clients": []
    },
    "streamSettings": {
      "network": "ws",
      "wsSettings": {
      "path": "/down"
      }
    },
    "tag": "proxy"
  },
  "outbound": {
    "protocol": "freedom",
    "settings": {}
  },
  "inboundDetour": [
    {
      "listen": "0.0.0.0",
      "port": 10087,
      "protocol": "dokodemo-door",
      "settings": {
        "address": "0.0.0.0"
      },
      "tag": "api"
    }
  ],
  "outboundDetour": [
    {
       "protocol": "blackhole",
       "settings": {},
       "tag": "blocked"
    }
  ],
  "routing": {
    "strategy": "rules",
    "settings": {
      "rules": [
        {
          "inboundTag": [
            "api"
          ],
          "outboundTag": "api",
          "type": "field"
        }
      ]
    }
  },
  "policy": {
    "levels": {
      "1": {
        "statsUserUplink": true,
        "statsUserDownlink": true
      }
    }
  }
}
  • config.properties
# v2ray路径
v2ray.path=/root/v2ray
# 可执行文件名
v2ray.exec=v2ray 
# GRPC设置
v2ray.grpc.address=127.0.0.1
v2ray.grpc.port=10087
# 协议标签
v2ray.tag=proxy
# 加密方式 可选值(aes-128-gcm, chacha20-poly1305, none, auto)
v2ray.security=auto
# 额外ID
v2ray.alter-id=64
# 用户等级
v2ray.level=1

### 节点配置 ###

# 节点ID
node.id=9
# 检查时间(秒)
node.check-rate=300
# 流量比例
node.traffic-rate=1.5

### 数据库配置 ###
  1. 客户端配置

超流量后不能主动断开客户链接

2018/10/28 20:07:49 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 更新用户: ADD 0 REMOVE 1
2018/10/28 20:08:49 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新在线用户 数: NUMBER 0

remove的这个用户当前尚未断开的v2ray连接仍可以使用，而且不再统计流量了

建议将能自动化的都自动化一下

提一个建议，因为java能读数据库，那么也能读取到协议设置，因为v2ray一个服务器只有一个协议设置，因此可以尝试获取而外连接和加密方式等等的东西，那也就能写成自动脚本了

连接中断

您好，我用screen守护java -jar ssrpanel-v2ray-0.0.2.jar，1一夜之后，就自动退出了，大佬您是用什么守护的，我的机子是阿里云H1G

alpine报错

nat126579:~# java -jar ssrpanel-v2ray-0.0.3-jar-with-dependencies.jar

| / ()__ __ | | ____ _ | \ | | | |
| |/| | / __|/ | |/ / _ | | | |/ _ \ _|
| | | | _ \ (| | < (| | | |\ | _/ |
|| |||/_,||__,| || _|___|__|

2019/01/27 09:34:35 [INFO] cn.moegezi.v2ray.node.process.V2rayUpdate: 开始检测V2Ray更新
2019/01/27 09:34:37 [INFO] cn.moegezi.v2ray.node.process.V2rayUpdate: V2Ray已是最新版本
V2Ray 4.13.0 (Po) 20190117
A unified platform for anti-censorship.
main: failed to read config file: /root/config.json > v2ray.com/core/main/json: failed to execute v2ctl to convert config file. > v2ray.com/core/common/platform/ctlcmd: failed to execute v2ctl: fatal error: out of memory allocating heap arena map

runtime stack:
runtime.throw(0xc4e760, 0x27)
/go/src/runtime/panic.go:608 +0x72 fp=0x7fff2edf1c30 sp=0x7fff2edf1c00 pc=0x42a9f2
runtime.(*mheap).sysAlloc(0x1265780, 0x4000000, 0x0, 0x0)
/go/src/runtime/malloc.go:629 +0x599 fp=0x7fff2edf1cb8 sp=0x7fff2edf1c30 pc=0x40b079
runtime.(*mheap).grow(0x1265780, 0x1, 0x0)
/go/src/runtime/mheap.go:920 +0x42 fp=0x7fff2edf1d10 sp=0x7fff2edf1cb8 pc=0x423132
runtime.(*mheap).allocSpanLocked(0x1265780, 0x1, 0x127f1c8, 0x0)
/go/src/runtime/mheap.go:848 +0x337 fp=0x7fff2edf1d50 sp=0x7fff2edf1d10 pc=0x422fb7
runtime.(*mheap).alloc_m(0x1265780, 0x1, 0x2a, 0x0)
/go/src/runtime/mheap.go:692 +0x119 fp=0x7fff2edf1d90 sp=0x7fff2edf1d50 pc=0x4227c9
runtime.(*mheap).alloc.func1()
/go/src/runtime/mheap.go:759 +0x4c fp=0x7fff2edf1dc8 sp=0x7fff2edf1d90 pc=0x45331c
runtime.(*mheap).alloc(0x1265780, 0x1, 0x1002a, 0x0)
/go/src/runtime/mheap.go:758 +0x8a fp=0x7fff2edf1e18 sp=0x7fff2edf1dc8 pc=0x422a6a
runtime.(*mcentral).grow(0x1267538, 0x0)
/go/src/runtime/mcentral.go:232 +0x94 fp=0x7fff2edf1e60 sp=0x7fff2edf1e18 pc=0x416824
runtime.(*mcentral).cacheSpan(0x1267538, 0x7f9f44a12000)
/go/src/runtime/mcentral.go:106 +0x2f8 fp=0x7fff2edf1ea8 sp=0x7fff2edf1e60 pc=0x416378
runtime.(*mcache).refill(0x7f9f44a12000, 0x2a)
/go/src/runtime/mcache.go:122 +0x95 fp=0x7fff2edf1ed8 sp=0x7fff2edf1ea8 pc=0x415f35
runtime.(*mcache).nextFree.func1()
/go/src/runtime/malloc.go:749 +0x32 fp=0x7fff2edf1ef8 sp=0x7fff2edf1ed8 pc=0x452732
runtime.(*mcache).nextFree(0x7f9f44a12000, 0x127f22a, 0x4000, 0x7f9f44a12000, 0x7fff2edf1fb8)
/go/src/runtime/malloc.go:748 +0xb6 fp=0x7fff2edf1f50 sp=0x7fff2edf1ef8 pc=0x40b356
runtime.mallocgc(0x180, 0xc317c0, 0x7fff2edf2001, 0x7f9f44a16000) /go/src/runtime/malloc.go:903 +0x793 fp=0x7fff2edf1ff0 sp=0x7fff2edf1f50 pc=0x40bca3
runtime.newobject(0xc317c0, 0x127f220)
/go/src/runtime/malloc.go:1032 +0x38 fp=0x7fff2edf2020 sp=0x7fff2edf1ff0 pc=0x40c088
runtime.malg(0x7f9f00008000, 0x7f9f44a12000)
/go/src/runtime/proc.go:3285 +0x31 fp=0x7fff2edf2060 sp=0x7fff2edf2020 pc=0x433d71
runtime.mpreinit(0x1260260)
/go/src/runtime/os_linux.go:311 +0x29 fp=0x7fff2edf2080 sp=0x7fff2edf2060 pc=0x428e29
runtime.mcommoninit(0x1260260)
/go/src/runtime/proc.go:624 +0xc1 fp=0x7fff2edf20b8 sp=0x7fff2edf2080 pc=0x42d821
runtime.schedinit()
/go/src/runtime/proc.go:546 +0x89 fp=0x7fff2edf2120 sp=0x7fff2edf20b8 pc=0x42d4e9
runtime.rt0_go(0x7fff2edf2158, 0x2, 0x7fff2edf2158, 0x0, 0x0, 0x2, 0x7fff2edf2df2, 0x7fff2edf2e06, 0x0, 0x7fff2edf2e0d, ...)
/go/src/runtime/asm_amd64.s:195 +0x11a fp=0x7fff2edf2128 sp=0x7fff2edf2120 pc=0x454f7a

exit status 2

跑不起来

[root@host ssrpanel-v2ray]# java -jar /root/ssrpanel-v2ray/ssrpanel-v2ray-0.0.1-SNAPSHOT.jar

| / ()__ __ | | ____ _ | \ | | | |
| |/| | / __|/ | |/ / _ | | | |/ _ \ _|
| | | | _ \ (| | < (| | | |\ | _/ |
|| |||/_,||__,| || _|___|__|

/root/v2ray-linux-64/v2ray: /root/v2ray-linux-64/v2ray: cannot execute binary file
2018/10/26 12:33:56 [INFO] cn.moegezi.v2ray.node.process.V2rayDestroyer: V2ray已启动
2018/10/26 12:33:56 [INFO] com.zaxxer.hikari.HikariDataSource: HikariPool-1 - Starting...
2018/10/26 12:33:57 [INFO] com.zaxxer.hikari.HikariDataSource: HikariPool-1 - Start completed.
2018/10/26 12:33:57 [INFO] cn.moegezi.v2ray.node.process.V2rayDestroyer: V2ray已停止
2018/10/26 12:33:57 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新在线用户数: NUMBER 0
2018/10/26 12:33:57 [INFO] cn.moegezi.v2ray.node.process.V2rayDao: 更新节点负载信息: LOAD 0.080.030.01
2018/10/26 12:33:58 [ERROR] cn.moegezi.v2ray.node.process.V2rayGrpc: 添加用户失败io.grpc.StatusRuntimeException: UNAVAILABLE: Channel shutdown invoked
2018/10/26 12:33:58 [INFO] cn.moegezi.v2ray.node.process.V2rayGrpc: 更新用户: ADD 45 REMOVE 0
[root@host ssrpanel-v2ray]# /etc/init.d/iptables stop

使用ws下用户添加失败

2018/11/06 08:41:05 [ERROR] cn.moegezi.v2ray.node.process.V2rayGrpc: 添加用户失败io.grpc.StatusRuntimeException: UNKNOWN: v2ray.com/core/app/proxyman/command: failed to get handler: proxy > v2ray.com/core/app/proxyman/inbound: handler not found: proxy

{
"api": {
"services": [
"HandlerService",
"StatsService"
],
"tag": "api"
},
"stats": {},
"inbound": {
"port": 10087,
"protocol": "vmess",
"settings": {
"clients": []
},
"streamSettings":{
"network":"ws",
"wsSettings": {
"path": "/ws",
"headers": {
"Host": "****.com"
}
}
}},
"inboundDetour": [
{
"listen": "0.0.0.0",
"port": 10086,
"protocol": "dokodemo-door",
"settings": {
"address": "0.0.0.0"
},
"tag": "api"
}
],
"log": {
"access": "./access.log",
"error": "./error.log",
"loglevel": "debug"
},
"outbound": {
"protocol": "freedom",
"settings": {}
},
"routing": {
"settings": {
"rules": [
{
"inboundTag": [
"api"
],
"outboundTag": "api",
"type": "field"
}
]
},
"strategy": "rules"
},
"policy": {
"levels": {
"1": {
"statsUserUplink": true,
"statsUserDownlink": true
}
}
}
}

dalao出现这个是怎么回事呢

java -jar /root/ssrpanel-v2ray/ssrpanel-v2ray-0.0.1-SNAPSHOT.jar
Error: Unable to access jarfile /root/ssrpanel-v2ray/ssrpanel-v2ray-0.0.1-SNAPSHOT.jar

提示找不到config.properties？

java -jar /root/ssrpanel-v2ray/ssrpanel-v2ray-0.0.2.jar

| / ()__ __ | | ____ _ | \ | | | |
| |/| | / __|/ | |/ / _ | | | |/ _ \ _|
| | | | _ \ (| | < (| | | |\ | _/ |
|| |||/_,||__,| || _|___|__|

2018/10/28 18:46:04 [ERROR] cn.moegezi.v2ray.node.utils.ConfigUtil: 配置文件错误
org.apache.commons.configuration2.ex.ConfigurationException: Could not locate: org.apache.commons.configuration2.io.FileLocator@2133c8f8[fileName=config.properties,basePath=,sourceURL=,encoding=ISO-8859-1,fileSystem=,locationStrategy=]
at org.apache.commons.configuration2.io.FileLocatorUtils.locateOrThrow(FileLocatorUtils.java:346)
at org.apache.commons.configuration2.io.FileHandler.load(FileHandler.java:972)
at org.apache.commons.configuration2.io.FileHandler.load(FileHandler.java:702)
at org.apache.commons.configuration2.builder.FileBasedConfigurationBuilder.initFileHandler(FileBasedConfigurationBuilder.java:312)
at org.apache.commons.configuration2.builder.FileBasedConfigurationBuilder.initResultInstance(FileBasedConfigurationBuilder.java:291)
at org.apache.commons.configuration2.builder.FileBasedConfigurationBuilder.initResultInstance(FileBasedConfigurationBuilder.java:60)
at org.apache.commons.configuration2.builder.BasicConfigurationBuilder.createResult(BasicConfigurationBuilder.java:421)
at org.apache.commons.configuration2.builder.BasicConfigurationBuilder.getConfiguration(BasicConfigurationBuilder.java:285)
at cn.moegezi.v2ray.node.utils.ConfigUtil.(ConfigUtil.java:24)
at cn.moegezi.v2ray.node.process.V2rayManager.(V2rayManager.java:11)
at cn.moegezi.v2ray.node.process.V2rayManager.getInstance(V2rayManager.java:39)
at cn.moegezi.v2ray.node.V2rayNodeApp.main(V2rayNodeApp.java:15)
Exception in thread "main" java.lang.NullPointerException
at cn.moegezi.v2ray.node.utils.ConfigUtil.getString(ConfigUtil.java:31)
at cn.moegezi.v2ray.node.process.V2rayManager.(V2rayManager.java:11)
at cn.moegezi.v2ray.node.process.V2rayManager.getInstance(V2rayManager.java:39)
at cn.moegezi.v2ray.node.V2rayNodeApp.main(V2rayNodeApp.java:15)

奇怪的错误

V2Ray 3.49 (die Commanderin) 20181025
A unified platform for anti-censorship.
2018/11/07 02:38:47 [INFO] cn.moegezi.v2ray.node.process.V2rayDestroyer: V2ray已启动
Failed to start v2ray.com/core/app/proxyman/inbound: failed to listen TCP on 53 > v2ray.com/core/transport/internet: failed to listen on address: 0.0.0.0:53 > listen udp 0.0.0.0:53: bind: address already in use
2018/11/07 02:38:47 [INFO] com.zaxxer.hikari.HikariDataSource: HikariPool-1 - Starting...
2018/11/07 02:38:49 [INFO] com.zaxxer.hikari.HikariDataSource: HikariPool-1 - Start completed.
2018/11/07 02:38:50 [INFO] cn.moegezi.v2ray.node.process.V2rayDestroyer: V2ray已停止

当端口设置为53时候就报错，修改端口为65后，就能正常运行了
这次我检查了json
{ "api": { "services": ["HandlerService", "StatsService"], "tag": "api" }, "stats": {}, "inbound": { "port": 65, "protocol": "vmess", "settings": { "clients": [] }, "streamSettings": { "network": "mkcp", "kcpSettings": { "mtu": 1350, "tti": 20, "uplinkCapacity": 5, "downlinkCapacity": 100, "congestion": true, "readBufferSize": 1, "writeBufferSize": 1, "header": { "type": "none" } } }, "tag": "proxy" }, "inboundDetour": [{ "listen": "0.0.0.0", "port": 10086, "protocol": "dokodemo-door", "settings": { "address": "0.0.0.0" }, "tag": "api" }], "log": { "access": "./access.log", "error": "./error.log", "loglevel": "debug" }, "outbound": { "protocol": "freedom", "settings": {} }, "routing": { "settings": { "rules": [{ "inboundTag": ["api"], "outboundTag": "api", "type": "field" }] }, "strategy": "rules" }, "policy": { "levels": { "1": { "statsUserUplink": true, "statsUserDownlink": true } } } }

关于config

请问在config.properties文件中，v2ray.tag该值应该设置为什么？默认是“proxy”。

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.