解决 invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received.

最新推荐文章于 2024-06-10 12:44:22 发布
最新推荐文章于 2024-06-10 12:44:22 发布
阅读量4.1k 收藏 1
点赞数 4
分类专栏： 日常错误 文章标签： VMessAEAD
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u014374009/article/details/128818051
版权

2023/01/31 10:27:56 111.181.19.37:45288 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:27:57 111.181.19.37:45268 rejected common/drain: common/drain: drained connection > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:00 111.181.19.37:45273 rejected common/drain: common/drain: drained connection > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:02 111.181.19.37:45279 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:15 111.181.19.37:45147 rejected common/drain: common/drain: drained connection > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:23 111.181.19.37:45258 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:25 111.181.19.37:45194 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:39 111.181.19.37:45170 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:39 111.181.19.37:45242 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:40 111.181.19.37:45117 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:44 111.181.19.37:45131 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:44 111.181.19.37:45104 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:28:45 111.181.19.37:45296 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:29:05 111.181.19.37:45110 rejected common/drain: common/drain: unable to drain connection > read tcp 10.0.0.12:12345->111.181.19.37:45110: i/o timeout > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:29:05 111.181.19.37:45275 rejected common/drain: common/drain: unable to drain connection > read tcp 10.0.0.12:12345->111.181.19.37:45275: i/o timeout > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:29:10 111.181.19.37:45175 rejected common/drain: common/drain: unable to drain connection > read tcp 10.0.0.12:12345->111.181.19.37:45175: i/o timeout > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:29:17 111.181.19.37:45122 rejected common/drain: common/drain: unable to drain connection > read tcp 10.0.0.12:12345->111.181.19.37:45122: i/o timeout > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:31:25 111.181.19.37:45099 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:31:27 111.181.19.37:45195 rejected common/drain: common/drain: drained connection > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:31:29 111.181.19.37:45214 rejected common/drain: common/drain: drained connection > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:31:51 111.181.19.37:45118 rejected common/drain: common/drain: drained connection > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:32:07 111.181.19.37:45247 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:32:07 111.181.19.37:45310 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:32:07 111.181.19.37:45170 rejected common/drain: common/drain: unable to drain connection > read tcp 10.0.0.12:12345->111.181.19.37:45170: i/o timeout > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:32:12 111.181.19.37:45258 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.
2023/01/31 10:32:12 111.181.19.37:45162 rejected common/drain: common/drain: unable to drain connection > EOF > proxy/vmess/encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. You can still disable this security feature with environment variable v2ray.vmess.aead.forced = false . You will not be able to enable legacy header workaround in the future.

解决方法：

方法一
将服务端和客户端的 alterID 改成 0 。

方法二
下面操作都在服务端进行，也就是设置环境变量，关闭 AEAD，就这么简单。

首先下面命令，查看v2ray的systemd的详细路径和内容：

systemctl cat v2ray

然后会看到类似下面内容：

# /etc/systemd/system/v2ray.service
[Unit]
Description=V2Ray Service
Documentation=https://www.v2fly.org/
After=network.target nss-lookup.target

[Service]
User=nobody
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
AmbientCapabilities=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
NoNewPrivileges=true
ExecStart=/usr/bin/v2ray -config /etc/v2ray/config.json
Restart=on-failure
RestartPreventExitStatus=23

[Install]
WantedBy=multi-user.target

可以看到上面有文件路径：

vi /etc/systemd/system/v2ray.service

然后修改一下，在 Service 区块添加一行：

Environment="V2RAY_VMESS_AEAD_FORCED=false"

然后更新一下systemd服务：

systemctl daemon-reload

最后重启一下v2ray就好了。

systemctl restart v2ray
代码讲故事
关注
专栏目录
i2c子系统分析：源码2. kernel-3.18\drivers\i2c\i2c-core.c
zhigouliu的博客
05-25 1631
/* i2c_core.c 分析 postcore_initcall(i2c_init); module_exit(i2c_exit); #ifdef CONFIG_I2C_COMPAT // 此宏为关 重要的数据结构: struct i2c_driver { // 描述一个从设备驱动对象 int (*probe)(struct i2c_client *, const struc...
System Error Codes/系统错误代码
weixin_30666401的博客
08-10 4418
在windows上程序或脚本运行突然出现未知错误,没有错误信息只有一个code,怎样知道究竟是怎么回事呢？如果知道这个code的意思是多么重要的.这时错误代码(System Error Codes)可以帮上你的忙。 从MSDN 上找到关于如下信息(http://msdn.microsoft.com/en-us/library/ms681381.aspx),页面的build dat...
服务器重启之后，V2无法使用，查看日志出现drained connection ＞ proxy/vmess/encoding: invalid user:
ptmicky的博客
12-01 1万+
VMess MD5 认证信息 污染机制，解决办法参考。
Vue前端proxy代理解决完跨域问题后报错404(Not Found)
angrynouse的博客
07-28 3930
Vue前端proxy代理解决完跨域问题后报错404(NotFound)
WebSocket connection to 'ws://localhost:8080/xxx' failed: Error during WebSocket handshake...
热门推荐
青山师
11-09 22万+
WebSocket connection to ‘ws://localhost:8080/xxx’ failed: Error during WebSocket handshake: Unexpected response code: 200 websocket项目启动之后，页面控制台报错，后面发现是后台加了拦截器导致的,分享解决前后的代码情况。 (本文章分享在CSDN平台，更多精彩请阅读 东陆
常用网络通信协议介绍与对比
小凯的博客
06-04 1万+
常用网络通信协议的介绍与对比
Vmess协议是什么意思? VLESS与VMess有什么区别?
最新发布
qq_34623639的博客
06-10 4132
VMess 是一个基于 TCP 的加密传输协议，所有数据使用 TCP 传输，是由 V2Ray 原创并使用于 V2Ray 的加密传输协议，它分为入站和出站两部分，其作用是帮助客户端跟服务器之间建立通信。在 V2Ray 上客户端与服务器的通信主要是通过 VMess 协议通信。VMess客户端发起一个请求，服务器确定该请求是否来自一个合法的客户端。如果是，请求被转发，收到的响应被送回给客户端。VMess使用非对称格式，即客户端的请求和服务器的响应使用不同的格式。
阿里邮件API返回 InvalidUser.NotFound. The specified user does not found
new1024kb
03-19 1407
客官，留下你的赞；成为我的粉丝，一起上车哦！评论区欢迎你的留言 问题：在用阿里邮件推送服务的时候，第三方接口返回InvalidUser.NotFound. The specified user does not found。 出现的原因：选择了发送邮件的API服务地址，但是此API服务地址下并未配置相关的信息。 阿里邮件发送API服务地址有以下三个 每个API服务地址下都需要配置相应的信息（你想...
Win32 Error Codes(转)
阿荣的技术专栏
11-03 7967
  CodeDescriptionName0The operation completed successfully.ERROR_SUCCESS1Incorrect function.ERROR_INVALID_FUNCTION2The system cannot find the file specified.ERROR
使用SQLMonitor监视访问ORACLE的“服务”
tanwen1234的专栏
04-19 9869
  以前使用SQLMonitor抓捕“应用程序”访问ORACLE的SQL语句，用起来比较爽……这次遇到的应用是以WINDOWS服务的方式来运行的，尝试了一下SQLMonitor的监视服务功能，报错：error 2 installing monitor for the service process  到网上搜索解决方法，提到SQLMonitor缺少“unidbsrv.dll”文件。我用的是SQLMoniter2.4.3.6，到网上下载了个以前版本的DLL文件，尝试 依然报错：error 193 instal
CVPR2017论文摘要汇总
super_chicken的博客
04-09 1万+
1. Exclusivity-Consistency Regularized Multi-view Subspace Clustering Abstract: Multi-view subspace clustering aims to partition a set of multi-source data into their underlying groups. To boost the ...
webSocket连接失败，页面报错websocket connect ******faield
qq_31839075的博客
11-16 2万+
项目中需要开发一个即时通讯功能，因此用到了websocket来实现双向通信，起初websocket接入点是在service层，因为要从页面发起请求接入，因此把接入点搬到了web层，此时启动项目后，进行连接测试时报错：因为在service层时连接是正常的，所以只能是web项目的问题，花了我四个小时，一点点看web项目的各个配置文件，最终发现是在设置跨域请求时，请求的allowedOrigins没有设置为*，导致连接失败。原因是websocket通讯的建立阶段是依赖于http协议的。最初的握手阶段是http协议
（转）VMvare桥接网络连接不上解决办法
小蚯蚓的博客
12-07 2574
【转载原因：vm桥接无法连接网关，之前没有问题，ip/掩码/网关都没有问题，突然有问题，参考解决】 【转载地址：https://blog.csdn.net/gui951753/article/details/81060903】 版权声明：本文为博主原创文章，遵循CC 4.0 BY-SA版权协议，转载请附上原文出处链接和本声明。 本文链接：https://blog.csdn.net/...
VMware 虚拟机外网连接问题排查
JiekeXu的博客
05-11 1121
作者 | JiekeXu来源 |公众号 JiekeXu DBA之路（ID: JiekeXu_IT）大家好，我是JiekeXu,很高兴又和大家见面了,今天和大家一起来怎么让虚拟机可以上外网？欢迎点击上方蓝字关注我，标星或置顶，更多干货第一时间到达！今天使用 VMware 搭建完一台 CentOS7 的 Linux 虚拟机后，发现不能够使用 CRT 远程链接。报错“The r...
Nginx下反向代理部署Spring Boot后WebSocket链接失败问题
WuHao的博客
06-07 641
问题记录：本地socket测试无误后部署发现WebSocket connection to "xxx/x"failed
解决VMware虚拟机网络连接失败的问题:Errors during downloading metadata for repository ‘AppStream‘
sun_itbest的博客
02-22 4844
1. 首先在本地运行cmd查看本地网络连接信息 ipconfig /all 查看本机IP地址&子网掩码&默认网关&DNS地址 2.正确设置虚拟机网络模式 vmware为我们提供了三种网络工作模式，它们分别是：Bridged（桥接模式）、NAT（网络地址转换模式）、Host-Only（仅主机模式）。 打开vmware虚拟机，我们可以在选项栏的“编辑”下的“虚拟网络编辑器”中看到VMnet0（桥接模式）、VMnet1（仅主机模式）、VMnet8（NAT模式），那么这些都是有什么作用呢？
Understanding iptables
maimang1001的专栏
01-26 1389
Linux netfilter Hacking HOWTO: Information for Programmershttps://www.netfilter.org/documentation/HOWTO/netfilter-hacking-HOWTO-4.html#ss4.1 NextPreviousContents 4.Information for Programmers I'll let you in on a secret: my pet hamster did all the co...
ytb网站报错 “您没有联网，请检查网络连接”
weixin_42375356的博客
02-15 7万+
问题原因&解决办法：计算机时间有问题，在设置中“同步”时间。并且关闭路由器的Ipv6以绝后患 v2ray.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal) 2021/02/15 14:02:23 t cp:127.0.0.1:63859 accepted tcp:www.googleapis.com:443 [proxy] 2021/02/15 14:02
Spring Boot application.properties或application.yml相关配置
乐于学习、乐于分享、乐于总结
01-28 5万+
# =================================================================== # COMMON SPRING BOOT PROPERTIES # # This sample file is provided as a guideline. Do NOT copy it in its # entirety to your own appl
database. Cause: java.lang.IllegalArgumentException: invalid comparison: java.util.Date and java.lang.String 这个报错 怎么解决
12-21
根据提供的引用内容，报错信息是"java.lang.IllegalArgumentException: invalid comparison: java.util.Date and java.lang.String"，这个错误是由于在比较时，将java.util.Date类型和java.lang.String类型进行了比较，导致类型不匹配的异常。解决这个问题的方法是将比较的两个对象的类型统一为相同的类型。 解决方案如下： 1. 确保比较的两个对象的类型相同，可以使用类型转换将java.lang.String类型转换为java.util.Date类型，或者将java.util.Date类型转换为java.lang.String类型，以便进行比较。 2. 如果比较的两个对象分别是数据库中的日期字段和一个字符串，可以使用数据库的日期函数将字符串转换为日期类型，然后再进行比较。 3. 如果比较的两个对象分别是Java代码中的变量，可以使用SimpleDateFormat类将字符串解析为日期对象，或者将日期对象格式化为字符串，然后再进行比较。 下面是一个示例代码，演示了如何解决这个报错： ```java import java.text.ParseException; import java.text.SimpleDateFormat; import java.util.Date; public class DateComparison { public static void main(String[] args) { String dateString = "2021-01-01"; Date date = new Date(); SimpleDateFormat dateFormat = new SimpleDateFormat("yyyy-MM-dd"); try { Date parsedDate = dateFormat.parse(dateString); // 将字符串解析为日期对象 if (date.compareTo(parsedDate) > 0) { System.out.println("Date is after parsedDate"); } else if (date.compareTo(parsedDate) < 0) { System.out.println("Date is before parsedDate"); } else { System.out.println("Date is equal to parsedDate"); } } catch (ParseException e) { e.printStackTrace(); } } } ```
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

代码讲故事

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值