-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser Dialer lost connection after reloading browser websocket page on Xray-core v24.9.30 . #3882
Comments
configuration |
@Fangliding 你试下能不能复现 |
我都没用过 要config的原因很大一部分是我复现要用 然而99%的人全部把要求当耳旁风 修就算了别人就一句不能用还得自己写配置测有没有真的有点淦了 |
@PoneyClairDeLune I just saw that |
@mmmray Ouch, gotta see how to prevent multiple handlers from getting run when available. |
may you should prevent like :
|
I'm tempted to just revert addEventListener to |
XTLS#3882 (comment) This does not fix the linked issue, just a random bug I found.
XTLS#3882 (comment) This does not fix the linked issue, just a random bug I found.
opened a PR for that #3906, but while testing, I found that I cannot reproduce this issue at all (even on main) -- anyway, please test the linked PR, and/or figure out which version introduced the issue |
#3882 (comment) This does not fix the linked issue, just a random bug I found.
XTLS#3882 (comment) This does not fix the linked issue, just a random bug I found.
Integrity requirements
Description
If reopen websoket page , Broswer dialer will not work anymore .
and must reboot xray to work.
Reproduction Method
none
Client config
Server config
Client log
[Info] [3827992590] app/proxyman/outbound: app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [websocket: close 1001 (going away)] > common/retry: all retry attempts failed
Server log
The text was updated successfully, but these errors were encountered: