这是什么意思啊？

最近多人反馈debug日志有些多，以后会做以下日志等级的调整。默认修改为error，如有建议可在此issue下留言。

• 保持原样
• debug
• info
• warning
• error
• none

自测速脚本不支持debian吗？求支持centos等其他的操作系统。
bash <(curl -L -s https://raw.githubusercontent.com/mack-a/v2ray-agent/master/find_best_cdn_ip.sh)

更新脚本后试了下Trojan-Go更新，到启动那一步提示失败。

---> Trojan-Go关闭成功
Trojan-Go启动失败
请手动执行【/etc/v2ray-agent/trojan/trojan-go -config /etc/v2ray-agent/trojan/config_full.json】,查看错误日志

查看日志提示

[FATAL] 2020/11/10 19:52:08 github.com/p4gefau1t/trojan-go/proxy.(*Option).Handle:option.go:29 open /etc/v2ray-agent/trojan/config_full.json: no such file or directory

分享一下我的设置，站长工具ping测试结果为全国平均130ms

移动 172.64.32.*（香港）
联通 104.16.80.*
国内 162.159.210.*（百度云加速合作节点）
默认 cloudflare.com

照这样配置，移动走香港直连，联通走104.16.80.*，电信走百度云合作节点。这是目前试出来最快而且还能用的，不知道能不能再更快。

都能用就是网站显示不安全

用您的脚本xray,选了0,1,4协议: vless+xtls, vless+ws, trojan-go
在第一次访问google和y2b时，Trojan可以立即连接上，vless+xtls, vless+ws则会有3-5秒的明显延迟；

尝试过启用/关闭脚本带的dns,结果一样
客户端是v2rayN 3.28+ xray 1.0

详细描述建议的内容
请问如何解除BT屏蔽

UPDATE FROM 2.1.26:

请选择:9

---> 没有检测到安装目录，请执行脚本安装内容

check the log，same issue。
only trojan in acount info。

/etc/v2ray-agent/xray folder in，v2ray in.
connect well.

• 1.去掉origin
• 2.多文件配置文件
• 3.ipv6的人机验证
• 4.兼容ipv6
• 5.添加多用户配置
• 6.自定义安装时选择trojan-go，只安装trojan-go不再安装回落【可能放到下一个版本，也可能不写】
• 7.自定义email地址

选择安装的是0,4，发现在某些VPS上，trojan-go启动时nginx还没启动，trojan-go就会启动失败，手动systemctl restart trojan-go才会启动成功，这种情况一般发生在系统重启后。在trojan-go.service里面的After=加上nginx.service就可以了，不知道有没有更好的解决办法

请问最新版本的脚本怎么切换core到xray-core？执行vasma选择8.core版本管理里面没有xray-core选择。谢谢

我的vps已经挂了博客网站的，使用脚本安装失败，报错如下：
请选择:1

功能 1/1 : 选择核心安装

==============================================================
1.Xray-core
2.v2ray-core
3.v2ray-core[XTLS]

请选择：3

进度 2/17 : 安装工具
---> 检查安装jq、nginx epel源、yum-utils
---> 检查、安装更新【新机器会很慢，耐心等待】

Transaction check error:
file /etc/my.cnf from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-config-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/Index.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/armscii8.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/ascii.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/cp1250.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/cp1251.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/cp1256.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/cp1257.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/cp850.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/cp852.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/cp866.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/dec8.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/geostd8.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/greek.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/hebrew.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/hp8.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/keybcs2.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/koi8r.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/koi8u.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/latin1.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/latin2.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/latin5.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/latin7.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/macce.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/macroman.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/charsets/swe7.xml from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-common-5.7.23-1.el7.x86_64
file /usr/share/mysql/czech/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/danish/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/dutch/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/english/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/estonian/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/french/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/german/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/greek/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/hungarian/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/italian/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/japanese/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/korean/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/norwegian-ny/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/norwegian/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/polish/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/portuguese/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/romanian/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/russian/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/serbian/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/slovak/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/spanish/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/swedish/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64
file /usr/share/mysql/ukrainian/errmsg.sys from install of mariadb-libs-1:5.5.68-1.el7.x86_64 conflicts with file from package appnode-mysql57-errmsg-5.7.23-1.el7.x86_64

Error Summary

---> 安装binutils

进度 3/17 : 初始化Nginx申请证书配置

请输入要配置的域名 例：blog.v2ray-agent.com --->
域名:store.**.io
---> 配置Nginx

检查IP是否设置为当前VPS
---> 检查ipv4中

当前域名的IP为 [******]，是否正确[y/n]？y

---> IP确认完成

检查Nginx是否正常访问
---> 无法正常访问服务器，请检测域名是否正确、域名的DNS解析以及防火墙设置是否正确--->

输入vasma里面没有v2ray状态、操作等选项。请问v2ray操作命令是什么啊？谢谢

VPS是openvz虚拟化，系统是debian8

脚本日志：
root@vm1601722352:~# ./install.sh
./install.sh: line 1707: rpm: command not found
（菜单省略）
请选择:1

进度 1/17 : 创建文件夹

进度 2/17 : 安装工具
---> 检查安装jq、nginx epel源、yum-utils
./install.sh: line 76: rpm: command not found
---> 检查、安装更新【新机器会很慢，耐心等待】
./install.sh: line 124: yum: command not found
---> 安装unzip
./install.sh: line 139: yum: command not found
---> 安装socat
./install.sh: line 145: yum: command not found
---> 安装crontabs
./install.sh: line 161: yum: command not found
---> 安装binutils
---> 安装nginx
./install.sh: line 178: yum: command not found
---> 安装sudo
./install.sh: line 184: yum: command not found
---> 安装acme.sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 201k 100 201k 0 0 2463k 0 --:--:-- --:--:-- --:--:-- 2487k
[Sat Oct 10 00:21:37 EDT 2020] It is recommended to install crontab first. try to install 'cron, crontab, crontabs or vixie-cron'.
[Sat Oct 10 00:21:37 EDT 2020] We need to set cron job to renew the certs automatically.
[Sat Oct 10 00:21:37 EDT 2020] Otherwise, your certs will not be able to be renewed automatically.
[Sat Oct 10 00:21:37 EDT 2020] Please add '--force' and try install again to go without crontab.
[Sat Oct 10 00:21:37 EDT 2020] ./acme.sh --install --force
[Sat Oct 10 00:21:37 EDT 2020] Pre-check failed, can not install.

进度 3/17 : 初始化Nginx申请证书配置
请输入要配置的域名 例：blog.v2ray-agent.com --->
域名:^C

root@vm1601722352:~# uname -romi
2.6.32-042stab145.3 x86_64 unknown GNU/Linux

root@vm1601722352:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.6 (jessie)
Release: 8.6
Codename: jessie

[[脚本生成的vmess格式地址，通过以下这个网页转换成clash格式后无法连接，用别的脚本生成的vmess链接转换后都没问题的，麻烦修正一下，谢谢
https://subcon.dlj.tf/

https://blog.v2ray-agent.com/test/

test1111112233 222333

请手动执行【/etc/v2ray-agent/v2ray/v2ray -config /etc/v2ray-agent/v2ray/config.json】,查看错误日志

详细描述建议的内容
大佬您好，想知道上述搭配是否可以搭配CDN，若不能，ip被封是不是就不能用了。我目前使用的VMESS+WS+CDN方案，好像无法再搭建VLESS+TLS/XTLS+TCP组合

使用这个脚本安装还没结束 vps就断开连接了 ，不知道是不是小鸡 硬件太差了

你好，升级Core有错误提示，升级后梯子正常。

XTLS/Go#9

v2ray/v2ray-core#2789 (comment)

• 根据以上两个issues所述，XTLS将来会在v2ray-core中移除，等他们正式分离后，脚本也会做相应的处理。

• 根据rprxx的新项目创建了对应的脚本项目，现在还没想好是合并到一块还是分离。

• rprxx新项目：https://github.com/XTLS/Xray-core 此项目是v2ray-core的超集，大概会支持v2ray-core的所有东西

• 脚本新项目：https://github.com/mack-a/Xray-agent

---> 配置Nginx
touch: cannot touch '/etc/nginx/conf.d/alone.conf': No such file or directory
/root/install.sh: line 499: /etc/nginx/conf.d/alone.conf: No such file or directory
nginx: [emerg] open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)
---> Nginx启动失败，请检查日志

下方留下相关的描述即可

1.描述出现的问题
人机代理配置成功，可以访问有图比，不能访问google.com

2.是否直接安装失败

• 否

3.直接安装失败的错误内容或者截图

• 此项没有可忽略

4.系统版本【例：Centos8】

下列系统版本需自己补全

• DEBAIN

5.脚本版本

• 2.2.6

6.安装类型

• 安装
• 个性化安装

7.安装的核心版本

version位置需自己替换

• Xray-core【version】
• v2ray-core【version】
• v2ray-core[XTLS]

8.出现问题的协议类型

• VLESS+XTLS
• VLESS+TLS+WS
• VMess+TLS+WS
• VMess+TLS+TCP
• Trojan
• Trojan-go+ws

9.尝试重装后是否100%复现

• 是

10.是否仔细检查客户端与服务端的配置是否相同

• 是

uninstall reboot后 80端口被nginx占用

不太清楚为什么一直报这个错误，但能通
使用的是xtls direct

[Warning] [2001959080] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vless/outbound: connection ends > v2ray.com/core/proxy/vless/outbound: failed to decode response header > v2ray.com/core/proxy/vless/encoding: failed to read response version > EOF

v2rayN 3.26
v2ray-core 4.31.0

用的azure，安装进程卡在检查IP是否设置为当前VPS

当服务器重启并删除了 /tmp/v2ray 文件夹， v2ray 服务启动会因为无法发现 /tmp/v2ray/v2ray_access_ws_tls.log 而失败，具体日志如下：

main: failed to create server > v2ray.com/core/app/log: failed to initialize access logger > open /tmp/v2ray/v2ray_access_ws_tls.log: no such file or directory

建议将日志文件放在 /var/v2ray或者v2ray服务启动时，检查一下 /tmp/v2ray 是否创建。

下方留下相关的描述即可

1.描述出现的问题

ipv6 无法安装
不识别ip，信息如下。

2.是否直接安装失败

• 是

3.直接安装失败的错误内容或者截图

• ---> 安装binutils
  ---> 安装ping6

进度 2/17 : 初始化Nginx申请证书配置

请输入要配置的域名 例：blog.v2ray-agent.com --->
域名:aa.suibianba02.cf

---> 配置Nginx

检查IP是否设置为当前VPS
ping: unknown host
IP查询失败，是否重试[y/n]？y
ping: unknown host
IP查询失败，是否重试[y/n]？y
ping: unknown host
IP查询失败，是否重试[y/n]？n

4.系统版本【例：Centos8】

• debian10

5.脚本版本

• 12月24日时间点最新版

6.安装类型

• 个性化安装/全部安装

7.安装的核心版本

• v2ray-core【version】

8.出现问题的协议类型

• ws cdn

9.尝试重装后是否100%复现

• 是

10.是否仔细检查客户端与服务端的配置是否相同

• 是

全新环净安装
进度 /17 : 初始化Nginx申请证书配置
域名不可为空--->

进度 /17 : 初始化Nginx申请证书配置
域名不可为空--->

进度 /17 : 初始化Nginx申请证书配置
域名不可为空--->

进度 /17 : 初始化Nginx申请证书配置
域名不可为空--->

进度 /17 : 初始化Nginx申请证书配置
域名不可为空--->

进度 /17 : 初始化Nginx申请证书配置
域名不可为空--->

进度 /17 : 初始化Nginx申请证书配置
域名不可为空--->

设置成Flexible速度会更快吗？

会不会出现什么问题？

作者你好，V2Ray版本管理更新可以增加更新时显示进度吗？谢谢

详细描述建议的内容
使用人机验证功能后，如果配置的ipv6隧道出问题了会导致无法访问谷歌,希望增加该功能使得此情况下能恢复访问谷歌

最后一步ngnix启动失败。以前安装的2.1.7版本可以用，换Debian8系统后，安装最新版本。ngnix启动失败。。

能不能出一个宝塔面板共存版？服务器上已经安装了宝塔面板，并且有网站正在运行。

我是小白，谁能告诉我怎么手动安装wget呢

如不支持，有考虑支持吗？

https://blog.v2ray-agent.com/2020-9-4-CloudFlare%E8%87%AA%E9%80%89ip/

技术笔记

进度 4/17 : 申请TLS证书
---> 安装TLS证书
[Fri Nov 13 07:21:32 EST 2020] 我的域名:Verify error:Fetching http://我的域名/.well-known/acme-challenge/sM7R-jOC2LuuBM-aeGNbrS2LkkmoX6l6cCs97iyU6fQ: Error getting validation d ata
[Fri Nov 13 07:21:32 EST 2020] Please add '--debug' or '--log' to check more details.
[Fri Nov 13 07:21:32 EST 2020] See: https://github.com/acmesh-official/acme.sh/wiki/How-to-debug-acme.sh
cat: /root/.acme.sh/我的域名_ecc/fullchain.cer: No such file or directory
---> TLS安装失败，请检查acme日志

刚申请的域名，在vps已经能ping通了

xtls要求服务端和客户端的版本一致，但是服务端的版本更新的太快了，现在已经是4.31.0，而能v2rayN和路由器上的依然是4.30，所以就上不了。