vps交流

[疑问] V2问题手机连接正常,电脑死活不能连接?


本帖最后由 yxasi 于 2022-1-12 23:59 编辑

https://www.moe.am/2241.html

照着大佬搞得以前手机电脑都可以正常连接,
这几天我用aws轻量和甲骨文的就手机可以连接,电脑死活不能连接。

同一台电脑的用以前一样搭建的可以手机电脑连接,现在搭建了就是手机可以连接,电脑死活不能连接。

toot 发表于 2022-1-13 00:18
大佬似乎更新了。去看看

2022/01/13        v2最近强制启用了VMessAEAD,小火箭用户需要在客户端“额外ID”填入0,安卓客户端默认就是0,不受影响,服务端不用做更改

电脑还是不行,手机正常连接。

请大佬指导一下。
你倒是贴个错误出来啊。。
"alterId": 64 这一行删掉

micms 发表于 2022-1-12 23:26
你倒是贴个错误出来啊。。

2022/01/12 23:33:36 tcp:127.0.0.1:64712 accepted tcp:us-east-1.prod.pr.analytics.console.aws.a2z.com:443 [proxy]
2022/01/12 23:33:36 tcp:127.0.0.1:64714 accepted tcp:mtalk.google.com:443 [proxy]
2022/01/12 23:33:41 tcp:127.0.0.1:65151 accepted tcp:p.api.pc120.com:80 [proxy]
2022/01/12 23:33:41 tcp:127.0.0.1:65154 accepted tcp:www.有图比.com:443 [proxy]
2022/01/12 23:33:41 tcp:127.0.0.1:65155 accepted tcp:www.有图比.com:443 [proxy]
2022/01/12 23:33:41 [Warning] failed to handler mux client connection > “v-2-r-a-y”.com/core/proxy/vmess/outbound: connection ends > “v-2-r-a-y”.com/core/proxy/vmess/outbound: failed to read header > “v-2-r-a-y”.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
2022/01/12 23:33:42 tcp:127.0.0.1:55625 accepted tcp:ap-southeast-1.lightsail.aws.amazon.com:443 [proxy]
2022/01/12 23:33:42 tcp:127.0.0.1:64712 accepted tcp:ap-southeast-1.console.aws.amazon.com:443 [proxy]
2022/01/12 23:33:42 tcp:127.0.0.1:65152 accepted tcp:p.api.pc120.com:80 [proxy]
2022/01/12 23:33:42 tcp:127.0.0.1:65154 accepted tcp:www.有图比.com:443 [proxy]
2022/01/12 23:33:42 tcp:127.0.0.1:65155 accepted tcp:www.有图比.com:443 [proxy]
2022/01/12 23:33:43 [Warning] failed to handler mux client connection > “v-2-r-a-y”.com/core/proxy/vmess/outbound: connection ends > “v-2-r-a-y”.com/core/proxy/vmess/outbound: failed to read header > “v-2-r-a-y”.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
2022/01/12 23:33:44 tcp:127.0.0.1:60917 accepted tcp:ap-southeast-1.console.aws.amazon.com:443 [proxy]
2022/01/12 23:33:44 tcp:127.0.0.1:60918 accepted tcp:ap-southeast-1.lightsail.aws.amazon.com:443 [proxy]
2022/01/12 23:33:44 tcp:127.0.0.1:55177 accepted tcp:us-east-1.prod.pr.analytics.console.aws.a2z.com:443 [proxy]
2022/01/12 23:33:45 tcp:127.0.0.1:55191 accepted tcp:www.有图比.com:443 [proxy]
2022/01/12 23:33:45 [Warning] failed to handler mux client connection > “v-2-r-a-y”.com/core/proxy/vmess/outbound: connection ends > “v-2-r-a-y”.com/core/proxy/vmess/outbound: failed to read header > “v-2-r-a-y”.com/core/proxy/vmess/encoding: failed to read response header > read tcp 192.168.1.157:60919->13.251.74.0:443: wsarecv: An existing connection was forcibly closed by the remote host.
2022/01/12 23:33:46 tcp:127.0.0.1:55337 accepted tcp:us-east-1.prod.pr.analytics.console.aws.a2z.com:443 [proxy]
2022/01/12 23:33:46 tcp:127.0.0.1:59934 accepted tcp:ap-southeast-1.lightsail.aws.amazon.com:443 [proxy]
2022/01/12 23:33:47 [Warning] failed to handler mux client connection > “v-2-r-a-y”.com/core/proxy/vmess/outbound: connection ends > “v-2-r-a-y”.com/core/proxy/vmess/outbound: failed to read header > “v-2-r-a-y”.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
2022/01/12 23:33:48 tcp:127.0.0.1:50229 accepted tcp:ap-southeast-1.lightsail.aws.amazon.com:443 [proxy]
2022/01/12 23:33:48 tcp:127.0.0.1:49318 accepted tcp:ap-southeast-1.console.aws.amazon.com:443 [proxy]
2022/01/12 23:33:49 tcp:127.0.0.1:49336 accepted tcp:p.api.pc120.com:80 [proxy]
2022/01/12 23:33:49 tcp:127.0.0.1:49338 accepted tcp:www.有图比.com:443 [proxy]
2022/01/12 23:33:49 tcp:127.0.0.1:49339 accepted tcp:www.有图比.com:443 [proxy]
2022/01/12 23:33:49 [Warning] failed to handler mux client connection > “v-2-r-a-y”.com/core/proxy/vmess/outbound: connection ends > “v-2-r-a-y”.com/core/proxy/vmess/outbound: failed to read header > “v-2-r-a-y”.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
2022/01/12 23:33:50 tcp:127.0.0.1:65198 accepted tcp:ap-southeast-1.console.aws.amazon.com:443 [proxy]
2022/01/12 23:33:50 tcp:127.0.0.1:49363 accepted tcp:ap-northeast-1.lightsail.aws.amazon.com:443 [proxy]
2022/01/12 23:33:51 [Warning] failed to handler mux client connection > “v-2-r-a-y”.com/core/proxy/vmess/outbound: connection ends > “v-2-r-a-y”.com/core/proxy/vmess/outbound: failed to read header > “v-2-r-a-y”.com/core/proxy/vmess/encoding: failed to read response header > websocket: close 1000 (normal)
2022/01/12 23:33:51 tcp:127.0.0.1:49379 accepted tcp:www.有图比.com:443 [proxy]
2022/01/12 23:33:52 tcp:127.0.0.1:54894 accepted tcp:ap-northeast-1.lightsail.aws.amazon.com:443 [proxy]

服务器alterId改0,客户端也改0

yhl 发表于 2022-1-12 23:34
"alterId": 64 这一行删掉

大佬那里删除?

"alterId": 0

yxasi 发表于 2022-1-12 23:34
2022/01/12 23:33:36 tcp:127.0.0.1:64712 accepted tcp:us-east-1.prod.pr.analytics.console.aws.a2z.c …

首先看看配置真的没错  就看看额外id改0了没  还有电脑时间是不是正确的 误差少于1分钟

micms 发表于 2022-1-12 23:37
首先看看配置真的没错  就看看额外id改0了没  还有电脑时间是不是正确的 误差少于1分钟 …

时间和id是0都是对的

赞(0)
版权声明:本贴采用知识共享 署名4.0国际许可协议 [BY-NC-SA] 进行授权
帖子名称:《[疑问] V2问题手机连接正常,电脑死活不能连接?》
帖子链接:https://bbs.toot.su/66186.html

相关推荐