预期情况 未知 实际情况 未知 复现方法 一直报这个错,win11无法使用,win10下正常,节点端口都未被墙。 日志信息 app/proxyman/outbound:…
- User
预期情况 未知
实际情况 未知
复现方法 一直报这个错,win11无法使用,win10下正常,节点端口都未被墙。
日志信息 app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [REALITY: processed invalid connection] > common/retry: all retry attempts failed
额外信息 No response
我确认已更新至最新版本 是 我确认已查询历史issues 是 @gavinsama gavinsama added the bug label on Oct 4, 2023 @myworksfun myworksfun commented on Oct 7, 2023 V6.29,Windows10,我也遇到了同样的问题😄 Snipaste_2023-10-07_15-57-34
@DA21S321D DA21S321D commented on Oct 15, 2023 同款 image
@gavinsama Author gavinsama commented on Oct 16, 2023 • 摸索了半天,发现是服务器与客户端时间没有校准导致的!解决方案参见:https://www.linuxv2ray.com/server/v2ray-synchronize-time-by-ntp/ 另外自定义回落域名到期或解析未生效,也可能导致出现此报错!
@joydamn joydamn commented on Nov 17, 2023 摸索了半天,发现是服务器与客户端时间没有校准导致的!解决方案参见:https://www.linuxv2ray.com/server/v2ray-synchronize-time-by-ntp/ 另外自定义回落域名到期或解析未生效,也可能导致出现此报错!
卧槽,终于解决了我的问题!!有一台电脑一直连不上,发现时间差了2分钟,时间一改正立马reality没问题了,感谢,为啥所有教程说明都没提到reality也回到vmess要求客户端时间准确,如多大佬找到说明的话可以发我一下吗
translate
- Assistant
Expected Situation Unknown
Actual Situation Unknown
Reproduction Method This error keeps coming up. It doesn't work on Windows 11 but works fine on Windows 10. The node ports are not blocked.
Log Information app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [REALITY: processed invalid connection] > common/retry: all retry attempts failed
Additional Information No response
I've confirmed updating to the latest version Yes I've confirmed searching for past issues Yes @gavinsama gavinsama added the bug label on Oct 4, 2023 @myworksfun myworksfun commented on Oct 7, 2023 V6.29, Windows 10, I encountered the same issue 😄 Snipaste_2023-10-07_15-57-34
@DA21S321D DA21S321D commented on Oct 15, 2023 Same issue image
@gavinsama Author gavinsama commented on Oct 16, 2023 • After exploring for a while, I found that it was due to the server and client time not being synchronized! Solution: https://www.linuxv2ray.com/server/v2ray-synchronize-time-by-ntp/ Additionally, a custom fallback domain expiration or unresolved parsing can also cause this error!
@joydamn joydamn commented on Nov 17, 2023 After exploring for a while, I found that it was due to the server and client time not being synchronized! Solution: https://www.linuxv2ray.com/server/v2ray-synchronize-time-by-ntp/ Additionally, a custom fallback domain expiration or unresolved parsing can also cause this error!
Wow, this finally solved my problem!! I had a computer that couldn't connect, and I found the time was off by 2 minutes. As soon as I corrected the time, there was no problem with reality. Thank you. Why don't all the tutorials mention that reality also requires accurate client time, like vmess? If any experts find the explanation, please send it my way.