正在开发的全新 V2ray.Fun
一个基于 Web 的 V2ray 控制面板
请务必使用新系统，纯净的VPS系统安装!!!
目前处于测试阶段，不保证一键脚本能安装成功
wget -N --no-check-certificate https://raw.githubusercontent.com/FunctionClub/V2ray.Fun/master/install.sh && bash install.sh
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
vps上面有多个ip 程序只能识别一个，另一个无法使用
输入v2ray抱着个错误是应为什么呢
没有卸载的操作嘛
问题描述
如何复现
<完整日志/报错>
其他问题
I would like to help translating this.
问题描述
搬瓦工vps，安装后，在打开面板运行状态上没有服务器ip地址显示
如何复现
<完整日志/报错>
其他问题
请从境外服务器获取服务器的IP地址，否则被wall的服务器运行此脚本就会因为无法获取服务器的公网IP而卡很久，进而安装好后要手动配置config，面板才会显示服务器IP。
问题描述
如何复现
<完整日志/报错>
其他问题
问题描述
如何复现
<完整日志/报错>
其他问题
v2ray.fun: ERROR (spawn error)
启动成功!
浏览器无法访问。。
重启后就无法启动了，报错似乎与supervisor有关，digitalocean centos 7.5
Ubuntu 16.04 LTS
没办法，vps之前运行着ss，按照步骤安装完毕，发现v2ray主进程已经运行，但lsof -i:5000 端口没有监听程序。酷炫的web控制台看不到，安装的时候没有报错，也没找到安装日志，很无奈啊。
难道一定要用全新系统来安装？
https://cdn.bootcss.com/jquery/3.3.1/jquery.min.js
index.html里的这个引用我这边的电信网挂了
改成https://code.jquery.com/jquery-3.3.1.min.js
index功能正常
问题描述
<对问题清晰而简明的描述：HostMybyet的VPS中的CentOS 7系统，一键脚本安装完成，设置好之后可以使用，但是一段时间不使用和连接，发现不能客户端不能登录，进入控制面板发现服务已经停止（未使用期间没有操作），需要手工启动服务可以正常使用。>
如何复现
<完整日志/报错>
其他问题
VPS：Vultr, 系统：Debian9
我用的是Cloudflare做CDN
1，先在CF里创建name为域名（不带www），value为 IP 的A记录,云朵点灰
2，在图形化脚本里面开启tls时输入域名（不带www），此时我的界面没有出现“请检查域名是否已解析至此服务器，这可能需要等待数分钟”，等了几十秒，tls开启成功
3，在CF里创建name为www, value为 IP 的A记录, （我自己的操作步骤是这样的，不知道第3步与 第1步同时做会不会成功，我也没有再验证。）
然后把两个云朵都点亮
4，进入VPS修改json文件，在adress一行，在域名前添加“www.”
5，用v2ray客户端扫描图形化界面的二维码，此时配置信息不全需要做如下修改
地址: 在已经存在的域名前加上“www.”
加密方式：auto（默认）
端口：443（配置文件里也要改成这个）
alterid：查看配置文件（默认100，建议自己修改）
传输协议: ws
伪装类型：none（默认）
伪装域名: 同地址
路径: /
底层传输安全: tls
本人不懂各种相关知识，纯粹是被墙逼成了高手（伪），靠脑洞猜想解决了这个问题，在此把自己的方法分享给大家，可能你用了这种方法不一定会成功，此外我是用纯净的VPS，如果你的vps之前安装了其他程序，那么重装一下系统也许会有帮助。
问题描述
如何复现
<完整日志/报错>
其他问题
可以加上服务器状态图表吗？
请问怎么卸载，卸载命令是什么？
其他问题
网页面板脚本没有动态端口功能
全新纯净ubuntu14，apt-get update后安装面板，reboot后无法进入，提示：
v2ray.fun: ERROR (not running)
v2ray.fun: ERROR (abnormal termination)
请教如何解决。。
下面命令行
root@ubuntu14:~# v2ray
欢迎使用 V2ray.Fun 面板 ---- By 雨落无声
当前面板用户名：admin
当前面板密码：admin
当前面板监听端口：5000
请输入数字选择功能：
请选择：3
v2ray.fun: ERROR (not running)
v2ray.fun: ERROR (abnormal termination)
重启成功!
root@ubuntu14:~#
如题，部分使用Caddy/Nginx做反代的用户就不需要再监听公网IP了，直接127.0.0.1就可以了；
另外面板SSL建议强制要求绑定域名签发Let's encrypt的证书。
How to uninstall this script?
v2ray 命令与其他命令冲突
可以加上电报专属设置么？
环境：DigitalOcean 新重装的 Debian 8.10 x64
pip 没有 -y 参数，去掉 -y 后出现以下错误
root@ubuntu-s-1vcpu-1gb-sfo2-01:/usr/local# pip install flask pyOpenSSL requests urllib3
Downloading/unpacking flask
Downloading Flask-1.0.2-py2.py3-none-any.whl (91kB): 91kB downloaded
Requirement already satisfied (use --upgrade to upgrade): pyOpenSSL in /usr/lib/python2.7/dist-packages
Requirement already satisfied (use --upgrade to upgrade): requests in /usr/lib/python2.7/dist-packages
Requirement already satisfied (use --upgrade to upgrade): urllib3 in /usr/lib/python2.7/dist-packages
Downloading/unpacking Jinja2>=2.10 (from flask)
Downloading Jinja2-2.10-py2.py3-none-any.whl (126kB): 126kB downloaded
Downloading/unpacking click>=5.1 (from flask)
Downloading click-6.7-py2.py3-none-any.whl (71kB): 71kB downloaded
Downloading/unpacking Werkzeug>=0.14 (from flask)
Downloading Werkzeug-0.14.1-py2.py3-none-any.whl (322kB): 322kB downloaded
Downloading/unpacking itsdangerous>=0.24 (from flask)
Downloading itsdangerous-0.24.tar.gz (46kB): 46kB downloaded
Running setup.py (path:/tmp/pip-build-gTNODm/itsdangerous/setup.py) egg_info for package itsdangerous
warning: no previously-included files matching '*' found under directory 'docs/_build'
Requirement already satisfied (use --upgrade to upgrade): cryptography>=0.2.1 in /usr/lib/python2.7/dist-packages (from pyOpenSSL)
Requirement already satisfied (use --upgrade to upgrade): six>=1.5.2 in /usr/lib/python2.7/dist-packages (from pyOpenSSL)
Downloading/unpacking MarkupSafe>=0.23 (from Jinja2>=2.10->flask)
Downloading MarkupSafe-1.0.tar.gz
Running setup.py (path:/tmp/pip-build-gTNODm/MarkupSafe/setup.py) egg_info for package MarkupSafe
Requirement already satisfied (use --upgrade to upgrade): cffi>=0.8 in /usr/lib/python2.7/dist-packages (from cryptography>=0.2.1->pyOpenSSL)
Requirement already satisfied (use --upgrade to upgrade): pycparser in /usr/lib/python2.7/dist-packages (from cffi>=0.8->cryptography>=0.2.1->pyOpenSSL)
Installing collected packages: flask, Jinja2, click, Werkzeug, itsdangerous, MarkupSafe
Compiling /tmp/pip-build-gTNODm/Jinja2/jinja2/asyncfilters.py ...
File "/tmp/pip-build-gTNODm/Jinja2/jinja2/asyncfilters.py", line 7
async def auto_to_seq(value):
^
SyntaxError: invalid syntax
Compiling /tmp/pip-build-gTNODm/Jinja2/jinja2/asyncsupport.py ...
File "/tmp/pip-build-gTNODm/Jinja2/jinja2/asyncsupport.py", line 22
async def concat_async(async_gen):
^
SyntaxError: invalid syntax
Running setup.py install for itsdangerous
warning: no previously-included files matching '*' found under directory 'docs/_build'
Running setup.py install for MarkupSafe
building 'markupsafe._speedups' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c markupsafe/_speedups.c -o build/temp.linux-x86_64-2.7/markupsafe/_speedups.o
markupsafe/_speedups.c:12:20: fatal error: Python.h: No such file or directory
#include <Python.h>
^
compilation terminated.
==========================================================================
WARNING: The C extension could not be compiled, speedups are not enabled.
Failure information, if any, is above.
Retrying the build without the C extension now.
==========================================================================
WARNING: The C extension could not be compiled, speedups are not enabled.
Plain-Python installation succeeded.
==========================================================================
Successfully installed flask Jinja2 click Werkzeug itsdangerous MarkupSafe
Cleaning up...
如题
操作系统:
内核版本:
Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
Release: 16.04
Codename: xenial
Python版本:
Python 3.5.2 (default, Nov 12 2018, 13:43:14)
[GCC 5.4.0 20160609] on linux
Bash版本:
GNU bash, version 4.3.48(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
脚本版本 (或者commit号):
问题描述
如何复现
错误信息：
Cloning into 'V2ray.Fun'...
remote: Enumerating objects: 491, done.
remote: Total 491 (delta 0), reused 0 (delta 0), pack-reused 491
Receiving objects: 100% (491/491), 2.60 MiB | 1.37 MiB/s, done.
Resolving deltas: 100% (251/251), done.
Checking connectivity... done.
Traceback (most recent call last):
File "init.py", line 4, in
import Config_Generator
File "/usr/local/V2ray.Fun/Config_Generator.py", line 4, in
import urllib2
ImportError: No module named 'urllib2'
mkdir: cannot create directory ‘/etc/supervisor’: File exists
mkdir: cannot create directory ‘/etc/supervisor/conf.d’: File exists
Traceback (most recent call last):
File "/usr/bin/echo_supervisord_conf", line 5, in
from pkg_resources import load_entry_point
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 3191, in
@_call_aside
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 3175, in _call_aside
f(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 3204, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 583, in _build_master
ws.require(requires)
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 900, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'supervisor==3.2.0' distribution was not found and is required by the application
请输入默认用户名[默认admin]：
请输入默认登录密码[默认admin]：
请输入监听端口号[默认5000]：
chmod: cannot access '/etc/v2ray/config.json': No such file or directory
Traceback (most recent call last):
File "/usr/bin/supervisord", line 5, in
from pkg_resources import load_entry_point
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 3191, in
@_call_aside
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 3175, in _call_aside
f(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 3204, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 583, in _build_master
ws.require(requires)
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 900, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'supervisor==3.2.0' distribution was not found and is required by the application
安装成功！
面板端口：5000
默认用户名：admin
默认密码：admin
输入 v2ray 并回车可以手动管理网页面板相关功能
You have new mail in /var/mail/root
root@instance-2:/# ^C
root@instance-2:/# v2ray
Traceback (most recent call last):
File "/usr/local/bin/v2ray", line 5, in
import commands
ImportError: No module named 'commands'
root@instance-2:/#
问题描述
当修改服务器IP或设置后，面板状态里显示不正确，还是当初建立时的链接。
如何复现
<完整日志/报错>
其他问题
问题描述
二维码在BifrostV无法扫描，而且在页面上服务器ip为空，但是手动在客户端设置参数可以正常使用
如何复现
使用客户端扫描
<完整日志/报错>
其他问题
多用户？
Cloning into 'V2ray.Fun'...
remote: Counting objects: 238, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 238 (delta 0), reused 0 (delta 0), pack-reused 235
Receiving objects: 100% (238/238), 2.54 MiB | 2.16 MiB/s, done.
Resolving deltas: 100% (108/108), done.
Checking connectivity... done.
Collecting pip
Downloading https://files.pythonhosted.org/packages/0f/74/ecd13431bcc456ed390b44c8a6e917c1820365cbebcb6a8974d1cd045ab4/pip-10.0.1-py2.py3-none-any.whl (1.3MB)
100% |████████████████████████████████| 1.3MB 987kB/s
Installing collected packages: pip
Found existing installation: pip 8.1.1
Not uninstalling pip at /usr/lib/python2.7/dist-packages, outside environment /usr
Successfully installed pip-10.0.1
Traceback (most recent call last):
File "/usr/bin/pip", line 9, in
from pip import main
ImportError: cannot import name main
Traceback (most recent call last):
File "/usr/bin/pip", line 9, in
from pip import main
ImportError: cannot import name main
install.sh: line 72: echo_supervisord_conf: command not found
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 14 0 14 0 0 49 0 --:--:-- --:--:-- --:--:-- 49
请输入默认用户名[默认admin]： admin
请输入默认登录密码[默认admin]： admin
请输入监听端口号[默认5000]： 5000
install.sh: line 125: supervisord: command not found
安装成功！
面板登录地址：http://52.192.14.255:5000
默认用户名：admin
默认密码：admin
输入 v2ray 并回车可以手动管理网页面板相关功能
你好，感谢开发者做出的贡献。
目前我使用的是v2ray方式是caddy+vmess+tls+websocket/h2. 其中vmess开了多条端口对应不同协议。LETS证书则是caddy自动管理的。
在这种情况下，可不可以与v2ray.fun一起合用？需要做出什么修改吗？
感谢。
v2ray 好像默认是没有办法限制连接数目和流量大小，大佬是这样的吗
系统 Linux 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux
全部安装完成，端口打开了，还是打不开网页。
CentOS 7安装不成功
Debian 9成功
搬瓦工VPS
xshell操作是不是不能用这个啊，我是版瓦工的vps,用xshell操作后，打开面板并没有打开web,只是提示成功。。
一位没来得及fork以前项目的假面骑士路过´_＞`
Ubuntu 18.04
下面遇到
请选择：1
v2ray.fun: ERROR (spawn error)
启动成功!
的问题 ？ 求原因？
root@digitalocean:~# v2ray
欢迎使用 V2ray.Fun 面板 ---- By 雨落无声
当前面板用户名：xxx
当前面板密码：xxx
当前面板监听端口：xxx
请输入数字选择功能：
请选择：1
v2ray.fun: ERROR (abnormal termination)
启动成功!
谢谢开发者的工作！已经顺利运行，但是没看到在那里设置用户名和密码，能在什么地方设置一下呢？
Debian 9 无法安装成功 pip报错 v2ray命令执行失败
Ubuntu 14 无法安装成功
Ubuntu 16 安装成功 服务无法启动
centos 7 安装成功 服务一切正常 但是与bifrostv客户端不兼容
服务端怎么卸载啊 想卸载v2ray 这个命令卸载不了
问题描述
v2ray.fun 里面选择tcp连接后启动不了服务，重启也试过不行
如何复现
<完整日志/报错>
其他问题
域名已经解析到服务器。但是SSL始终说未解析到服务器，服务器OS debian9
Debian GNU/Linux 9 (stretch)Linux 2.6.32-042stab128.2 #1 SMP Thu Mar 22 10:58:36 MSK 2018 x86_64 GNU/Linuxii python 2.7.13-2 amd64 interactive high-level object-oriented language (default version)
ii python-dev 2.7.13-2 amd64 header files and a static library for Python (default)
ii python-meld3 1.0.2-2 all HTML/XML templating system for Python
ii python-minimal 2.7.13-2 amd64 minimal subset of the Python language (default version)
ii python-pkg-resources 33.1.1-1 all Package Discovery and Resource Access using pkg_resources
ii python2.7 2.7.13-2+deb9u2 amd64 Interactive high-level object-oriented language (version 2.7)
ii python2.7-dev 2.7.13-2+deb9u2 amd64 Header files and a static library for Python (v2.7)
ii python2.7-minimal 2.7.13-2+deb9u2 amd64 Minimal subset of the Python language (version 2.7)
ii python3 3.5.3-1 amd64 interactive high-level object-oriented language (default python3 version)
ii python3-minimal 3.5.3-1 amd64 minimal subset of the Python language (default python3 version)
ii python3.5 3.5.3-1 amd64 Interactive high-level object-oriented language (version 3.5)
ii python3.5-minimal 3.5.3-1 amd64 Minimal subset of the Python language (version 3.5)
ii bash 4.4-5 amd64 GNU Bourne Again SHell问题描述
如何复现
见“问题描述”
2018/11/04 16:12:55 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:13:25 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:13:34 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:15:28 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:15:34 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:16:27 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:16:33 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:20:29 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:20:37 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:20:52 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:20:54 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:20:58 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:24:52 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/04 16:24:59 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/05 11:14:07 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/05 11:14:16 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/05 11:32:41 [Warning] v2ray.com/core: V2Ray 4.0 started
2018/11/05 11:33:18 [Warning] v2ray.com/core: V2Ray 4.0 started
Response Headers：
HTTP/1.0 200 OK
Content-Type: text/html; charset=utf-8
Content-Length: 5
Server: Werkzeug/0.14.1 Python/2.7.13
Date: Mon, 05 Nov 2018 11:39:56 GMT
其他问题
无
问题描述
正常安装运行，第二天CPU持续100%，htop查看如图
https://i1.yuangezhizao.cn/Win-10/20190513125106.jpg!webp
如何复现
2019-11-16 16:18:07-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:09-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:11-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:13-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:15-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:17-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:19-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:21-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:23-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:25-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:27-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:29-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:31-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:33-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:35-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:37-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:39-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:41-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:43-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:45-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:47-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:49-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:51-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:53-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:55-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:57-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:18:59-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:02-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:04-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:06-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:08-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:10-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:12-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:14-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:16-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:18-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:20-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:22-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:24-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:26-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:28-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
2019-11-16 16:19:30-root-WARNING-Failed to get system status information: [Errno 107] Transport endpoint is not connected: '/proc/stat'
其他问题
版主大人，昨天我研究了半天你的脚本，只要你按我这样做，目前存在的Issues都可以close了。
1、不是所有服务器安装系统时都有pip命令，因此，建议在脚本加入如下安装pip命令
#Install git
curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python get-pip.py
rm -rf get-pip.py
（加在#Install acme.sh之前）
2、最好在脚本中把/etc/v2ray/config.json权限设置成777，否则会有一些奇葩问题发生，例如面板改了设置，实际上并没有按照面板设置修改
chmod 777 /etc/v2ray/config.json
3、重要！开机时一定要启动supervisord服务，否则通过v2ray命令无法启动面板。事实上，在脚本加入如下命令，在服务器启动后已可自动启动面板
echo "supervisord -c /etc/supervisor/supervisord.conf">>/etc/rc.d/rc.local
chmod +x /etc/rc.d/rc.local
4、app.py以及Config_Generator.py的所有open(...)地方，文件名全部应该为绝对路径，否则服务器重启后会出现修改设置无法生效的奇葩bug
例如：app.py第8行：panel_config_file = open("panel.config","r")
应为：panel_config_file = open("/usr/local/V2ray.Fun/panel.config","r")
5、Config_Generator.py第9行替换掉URL为http://ifconfig.me，不要用member.3322.org获取服务器公网IP，否则你懂的……
我用ESXi搭CentOS7.3跑了一遍，反复重启几次面板均能自动启动，修改设置也生效，基本完美了。
能不能开发一个像Shadowsocks-Manager一样的多用户功能？(〃'▽'〃)
问题描述
如何复现
2018/10/16 09:44:08 [Info] [3859324782] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > context canceled
2018/10/16 09:44:08 [Info] [3859324782] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2018/10/16 09:44:09 [Info] [1651368626] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:34244 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:10 [Info] [529990292] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:34498 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:13 [Info] [1566485987] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:34816 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:14 [Info] [2393514815] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:35075 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:17 [Info] [3968680868] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:35585 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:18 [Info] [1866546100] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:35776 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:19 [Info] [3229994120] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:35969 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:19 [Info] [557007524] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:36033 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:23 [Info] [2054473830] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:36480 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:23 [Info] [2214630173] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:36545 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:27 [Info] [2908889393] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:33280 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:27 [Info] [3105746473] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:33347 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:30 [Info] [2536487465] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:33731 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:34 [Info] [1412556857] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:34048 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:38 [Info] [1863009355] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:34816 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:40 [Info] [3546682566] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:35008 > v2ray.com/core/proxy/vmess/encoding: invalid user
2018/10/16 09:44:44 [Info] [455848922] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from 125.71.153.10:35649 > v2ray.com/core/proxy/vmess/encoding: invalid user
其他问题
重启后无法启动
错误提示为
v2ray.fun: ERROR (abnormal termination)
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.