解决proxy/vmess/inbound: invalid request from xxx ＞ proxy/vmess/encoding:failed to read request header

于 2024-09-04 17:45:01 发布
阅读量609 收藏 3
点赞数 6
分类专栏： 日常错误 文章标签： linux proxy vmess inbound unexpected EOF request header
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u014374009/article/details/141898417
版权

解决 proxy/vmess/inbound: invalid request from 49.7.51.5:24347 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF。

在这里插入图片描述

客户端报错信息如下：

2024/09/04 16:59:23 [Warning] [547491954] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available: > read tcp 10.57.86
destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39ws://149.248.39.152:12
.152:12347/airdrome/): > read tcp 10.57.86.154:5739->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to dial WebSocket > transpernet/websocket: faile
ort/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5741->149.248.39.152:12347: i/o timeout transed to dial WebSocket >
port/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp t transport/internet/w
10.57.86.154:5743->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to d99->149.248.39.152:123
ial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5745->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to
dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5751->149.248.39.152:1e destination > common
2347: i/o timeout] > common/retry: all retry attempts failed: > read tcp 10.57.86
2024/09/04 17:00:06 [Warning] [397421476] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an availablews://149.248.39.152:12
destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39ernet/websocket: faile
.152:12347/airdrome/): > read tcp 10.57.86.154:5753->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to dial WebSocket > transped to dial WebSocket >
ort/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5755->149.248.39.152:12347: i/o timeout transt transport/internet/w
port/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp 23->149.248.39.152:123
10.57.86.154:5757->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to d
ial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5761->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to e destination > common
dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5765->149.248.39.152:1: > read tcp 10.57.86
2347: i/o timeout] > common/retry: all retry attempts failedws://149.248.39.152:12
2024/09/04 17:00:49 [Warning] [2046012441] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an availablernet/websocket: faile
e destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.3ed to dial WebSocket >
9.152:12347/airdrome/): > read tcp 10.57.86.154:5775->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to dial WebSocket > transt transport/internet/w
port/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5779->149.248.39.152:12347: i/o timeout tran39->149.248.39.152:123
sport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp
10.57.86.154:5781->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to estination > common/re
dial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5785->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to> read tcp 10.57.86.15
dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5789->149.248.39.152://149.248.39.152:12347
12347: i/o timeout] > common/retry: all retry attempts failedet/websocket: failed t
2024/09/04 17:01:32 [Warning] [172719071] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an availableto dial WebSocket > tr
destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39ransport/internet/webs
.152:12347/airdrome/): > read tcp 10.57.86.154:5793->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to dial WebSocket > transp>149.248.39.152:12347:
ort/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5795->149.248.39.152:12347: i/o timeout trans
port/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp e destination > common
10.57.86.154:5799->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to d: > read tcp 10.57.86
ial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5805->149.248.39.152:12347: i/o timeout transport/internet/websocket: failed to ws://149.248.39.152:12
dial WebSocket > transport/internet/websocket: failed to dial to (ws://149.248.39.152:12347/airdrome/): > read tcp 10.57.86.154:5807->149.248.39.152:1ernet/websocket: faile
2347: i/o timeout] > common/retry: all retry attempts failed

服务端报错信息如下：

tail -300f /var/log/v2ray/error.log

2024/09/04 16:18:25 [Info] [767874187] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:56264 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:18:25 [Info] [3696885437] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:23208 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:20:26 [Info] [4221344530] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:56338 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:20:26 [Info] [577208599] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:23293 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:22:26 [Info] [2832035742] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:23419 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:22:26 [Info] [3511725584] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:56396 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:24:26 [Info] [3878801062] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:23528 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:24:27 [Info] [1856030228] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:56464 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:26:27 [Info] [2449446009] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:56594 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:26:27 [Info] [3036634259] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:56560 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:28:27 [Info] [1719241090] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:56681 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:28:27 [Info] [2857112505] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:56638 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:30:28 [Info] [63252895] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:56764 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:30:28 [Info] [1076795733] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:23705 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:32:28 [Info] [5817728] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:56850 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:32:28 [Info] [3116858484] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:23806 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:34:28 [Info] [2997903288] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:23962 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:34:28 [Info] [1051944168] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:23890 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:36:29 [Info] [1750680467] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:24136 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:36:29 [Info] [3405468640] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:24039 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:38:29 [Info] [3640373694] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:24412 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:38:29 [Info] [519052976] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:24347 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:40:29 [Info] [175662879] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:24481 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:40:29 [Info] [1887035456] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:57461 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:42:30 [Info] [4150112350] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:57579 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:42:30 [Info] [3255727391] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:24511 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:44:30 [Info] [2194702911] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:57647 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:44:30 [Info] [3163118596] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:57614 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:46:30 [Info] [1401944381] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:57767 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:46:30 [Info] [780661157] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:57701 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:48:31 [Info] [3952463421] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:57854 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:48:31 [Info] [3649895609] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:57825 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:50:31 [Info] [70303008] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:57945 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:50:31 [Info] [4256505564] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:57902 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:52:32 [Info] [2579522723] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:58022 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:52:32 [Info] [2124025492] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:24968 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:54:32 [Info] [3578435301] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:58080 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:54:32 [Info] [2624015629] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:58067 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:56:32 [Info] [1705424793] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.4:58174 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:56:32 [Info] [2843625529] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 49.7.51.5:25113 > proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF

tail -300f /var/log/v2ray/access.log

2024/09/04 16:18:25 49.7.51.4:56264 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:18:25 49.7.51.5:23208 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:20:26 49.7.51.4:56338 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:20:26 49.7.51.5:23293 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:22:26 49.7.51.5:23419 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:22:26 49.7.51.4:56396 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:24:27 49.7.51.5:23528 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:24:27 49.7.51.4:56464 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:26:27 49.7.51.4:56594 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:26:27 49.7.51.4:56560 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:28:27 49.7.51.4:56681 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:28:27 49.7.51.4:56638 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:30:28 49.7.51.4:56764 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:30:28 49.7.51.5:23705 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:32:28 49.7.51.4:56850 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:32:28 49.7.51.5:23806 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:34:28 49.7.51.5:23962 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:34:28 49.7.51.5:23890 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:36:29 49.7.51.5:24136 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:36:29 49.7.51.5:24039 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:38:29 49.7.51.5:24412 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:38:29 49.7.51.5:24347 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:40:29 49.7.51.5:24481 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:40:29 49.7.51.4:57461 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:42:30 49.7.51.4:57579 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:42:30 49.7.51.5:24511 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:44:30 49.7.51.4:57647 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:44:30 49.7.51.4:57614 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:46:30 49.7.51.4:57767 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:46:30 49.7.51.4:57701 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:48:31 49.7.51.4:57854 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:48:31 49.7.51.4:57825 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:50:31 49.7.51.4:57945 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:50:31 49.7.51.4:57902 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:52:32 49.7.51.4:58022 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:52:32 49.7.51.5:24968 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:54:32 49.7.51.4:58080 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:54:32 49.7.51.4:58067 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:56:32 49.7.51.4:58174 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:56:32 49.7.51.5:25113 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:58:33 49.7.51.4:58288 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/04 16:58:33 49.7.51.5:25213 rejected proxy/vmess/encoding: failed to read request header > websocket: close 1006 (abnormal closure): unexpected EOF

解决方法：

新版V2抛弃了额外id(alterId)这个参数，如果客户端仍有这个选项，建议填0。

禁用selinux：

setenforce 0

检查 客户端 和 服务端 时间是否一直的，可以通过 ntp 命令同步时间：

ntpdate ntp1.aliyun.com

配置超时时间，0 表示不限制：

在这里插入图片描述

重启服务端和客户端，可以正常连接上网。

代码讲故事
关注
  • 6
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
【区块链】量子链命令行qtum-cli全命令详解
Code Metaverse
10-11 1万+
量子链命令行qtum-cli全命令详解== Blockchain ==callcontract “address” “data” ( address )调用智能合约getaccountinfo “address”获取账户信息getbestblockhash获取最长链的hashgetblock “blockhash” ( verbose )获取块的信息getblockchaininfo获取区块的信息{
开发随笔-关于支付
霍力强的专栏
02-28 6398
一篇老外的文章,感兴趣的可以研究下,里面有源代码的,呵呵,别说您英文看不懂了.http://www.west-wind.com/presentations/aspnetecommerce/aspnetecommerce.asp Integrating Electronic Payment Processing into ASP.NET Webapplications by Rick Strahlw
xray问题排查，curl: (35) Encountered end of file（已解决）
liu289747235的专栏
03-16 887
经过了好几次排查，都没找到问题，先说问题的排查过程，多次确认了user信息，包括用户id和alterid，都没问题，头大的一逼。
NATAPP - 连不上 / 错误信息等问题解决汇总
热门推荐
牧码的博客
02-11 2万+
先看1分钟新手教程，每一步都要确保正确。如果再连不上，参考以下常见问题，看能不能自己解决。如不能解决，再与我们联系，联系时不要仅问为什么连不上，natapp怎么用之类无意义的问句。应该尽量把详细信息，尽量将隧道类型，错误信息截图，debug信息，等都发给我们，我们才好判断问题，帮助解决。 这里列举常见错误，以及自助解决办法 "认证错误 请登录 https://natapp.cn...
/proc/net参数介绍（三）
bingyu的博客
06-19 3002
/proc/net参数介绍（三） 官网参考地址：https://www.cyberciti.biz/files/linux-kernel/Documentation/networking/ip-sysctl.txt 参数介绍： /proc/sys/net/ipv4/* Variables: ip_forward - BOOLEAN 0 - disabled (default) not 0 -...
Node.js v12.16.2 Documentation HTTP/2
BLOG域名:programb.blog.csdn.net
04-16 556
Index View on single page View as JSON View another version ▼ Edit on GitHub Table of Contents HTTP/2 Core API Server-side example Client-side example Class: Http2Ses...
异常解决: org.apache.ibatis.binding.BindingException: Invalid bound statement (not found)
Given Wu
12-15 260
MyBatis 抛出异常如下: org.apache.ibatis.binding.BindingException: Invalid bound statement (not found): com.threegrand.urdm.system.dao.UserDao.saveUser at org.apache.ibatis.binding.MapperMethod$SqlComma
Istio超时与重试
Micky_Yang的博客
07-24 5063
一、理解超时与重试 　　超时的原理是，如果程序请求长时间无法返回结果，则需要设置超时机制，超过设置的时间则返回错误的信息；这样做既可以节约等待时消耗的资源，也可以避免由于级联错误引起的一系列问题。设置超时的方式也有很多种，比如通过修改代码在应用程序侧设置请求超时时间，但是这样非常的不灵活，也很容易出现遗漏的现象，而Istio则可以在基础设施层解决这一问题。 　　重试的原理是，在网络环境不稳定的情况下，会出现暂时的网络不可达的现象，这时就需要重试机制，通过多次的尝试来获取正确的返回信息。 　　 二、配置超时
Linkerd2 proxy destination 学习笔记
ServiceMesher
10-29 473
作者: 哗啦啦 mesh团队，热衷于kubernetes、devops、apollo、istio、linkerd、openstack、calico 等领域技术。Linke...
system 相关的配置 /etc/sysctl.conf
中国奥特曼
02-07 359
sysctl root@B:/etc/sysctl.d# sysctl --h sysctl: unrecognized option: h BusyBox v1.28.3 () multi-call binary. Usage: sysctl -p [-enq] [FILE...] / [-enqaw] [KEY[=VALUE]]... Show/set kernel parameters -p Set values from FILEs (default /etc/sys
Linux字符设备驱动 -- regulator子系统
xi_xix_i的博客
09-01 766
Linux驱动之Regulator子系统Linux 内核之电源篇(加载流程)regulator，翻译就是调节器。一些可以输出电流电压的设备可以使用该子系统。举个例子，一个PMIC有多路输出，每一路输出都可以给很多外设、芯片供电。那么每一路输出，我都可以认为他是一个regulator。
Linux下UDP编程
热土程序园，利他愉己~
08-28 1999
Linux下UDP编程 socket（套接字）本质上是一个抽象的概念，它是一组用于网络通信的 API，提供了一种统一的接口，使得应用程序可以通过网络进行通信。在不同的操作系统中，socket 的实现方式可能不同，但它们都遵循相同的规范和协议，可以实现跨平台的网络通信。
在linux 中如何将.c 文件转换为可执行文件
千千道的博客
08-29 1795
在 Linux 环境下进行 C 语言编程时，将.c文件转换为可执行文件是一个关键的步骤。这个过程涉及到使用编译器和一些相关的工具，本文将详细介绍在 Linux 系统中如何将.c文件转换为可执行文件的方法。
Linux 命令行快捷键
sun007700的专栏
08-30 623
涉及在linux命令行下进行快速移动光标、命令编辑、编辑后执行历史命令、Bang(!Ctrl+y: 粘贴Ctrl+u或ctrl+k剪切的内容。Alt – d ：由光标位置开始，往右删除单词。Alt – d: 先按住 Alt 键，然后再按 d 键；Ctrl+u：删除当前光标前面的文字 (还有剪切功能)Ctrl+k：删除当前光标后面的文字 (还有剪切功能)M – k：先单击 Esc 键，然后再按 k 键。Ctrl+w: 删除光标前面的单词。Ctrl+左右键:在单词之间跳转。Ctrl+a: 跳到本行的行首。
实时Linux性能监控脚本：周期性自动统计CPU、内存和IO使用情况
promise524的博客
08-30 997
Shell脚本实现每3秒钟监控系统的 CPU 占用率、内存使用情况、IO使用情况、每个 CPU 核心的占用率、CPU 占用率最高的前10个进程以及/opt目录的磁盘空间变化。
linux查找mysql日志
爱思考的People
08-30 569
MySQL的日志文件通常存储在数据库服务器的数据目录下，具体位置取决于MySQL的配置文件。# 查找MySQL配置文件# 查找MySQL日志文件。
Linux下IO多路复用—select，poll，epoll
热土程序园，利他愉己~
08-29 1473
Linux下IO多路复用—select，poll，epoll IO多路复用是一种操作系统的技术，用于在单个线程或进程中管理多个输入输出操作。它的主要目的是通过将多个IO操作合并到一个系统调用中来提高系统的性能和资源利用率，避免了传统的多线程或多进程模型中因为阻塞IO而导致的资源浪费和低效率问题。 在IO多路复用中，通常使用的系统调用有 select()、poll()、epoll() 等，它们允许程序等待多个文件描述符（sockets、文件句柄等）中的任何一个变为可读或可写，然后再进行实际的IO操作。
[Linux] 项目自动化构建工具-make/Makefile
最新发布
水墨不写bug
09-03 711
[Linux] 项目自动化构建工具-make/Makefile
linux nc
xiaozhi
09-03 363
linux nc
v2ray.com/core/proxy/vmess/outbound: failed to find an available destination
05-23
这个错误通常是由于 V2Ray 配置文件中的 outbound 没有正确配置导致的。请确保您的 outbound 类型设置正确，目标地址和端口号正确，并且您的代理服务器正在运行并且可用。 您可以尝试检查以下配置参数： - protocol：协议类型，如 VMess。 - settings：与协议相关的设置，如服务器地址、端口、用户 ID 等。 - streamSettings：流设置，包括传输协议和加密方式等。 如果您仍然无法解决问题，请尝试查看 V2Ray 的日志，以获取更多详细信息。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

打赏作者

代码讲故事

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

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

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

打赏作者

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

抵扣说明：

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

余额充值