Skip to content
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

[Bug]: 7.2.3版本不能实时显示上下行速度 #6236

Open
2 tasks done
zhuhr213 opened this issue Dec 6, 2024 · 1 comment
Open
2 tasks done

[Bug]: 7.2.3版本不能实时显示上下行速度 #6236

zhuhr213 opened this issue Dec 6, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@zhuhr213
Copy link

zhuhr213 commented Dec 6, 2024

预期情况

应该显示,如之前版本一样

实际情况

右下角不显示上下行速度了,设置中已经将该功能开启,该功能还是蛮重要的,能够检测流量在走直连还是代理

复现方法

无操作,在某一次更新之后不显示了

日志信息

2024-12-06 00:23:39.3102-INFO Current_SessionEnding
2024-12-06 00:23:39.3146-INFO MyAppExit Begin
2024-12-06 00:23:39.3535-INFO OnExit
2024-12-06 09:41:42.5975-INFO v2rayN start up | v2rayN - V7.2.3 - X64 - 2024/11/29 | C:\Users\zhuhr\Desktop\v2rayN-With-Core\v2rayN.exe
2024-12-06 09:41:42.5975-INFO Microsoft Windows NT 10.0.26100.0 - 64
2024-12-06 09:41:43.0363-INFO UpdateTaskRunGeo
2024-12-06 09:42:43.0367-INFO UpdateTaskRunSubscription
2024-12-06 09:43:44.4252-INFO MyAppExit Begin
2024-12-06 09:43:44.5489-INFO MyAppExit End
2024-12-06 09:43:44.5732-INFO OnExit
2024-12-06 09:43:44.8814-INFO v2rayN start up | v2rayN - V7.2.3 - X64 - 2024/11/29 | C:\Users\zhuhr\Desktop\v2rayN-With-Core\v2rayN.exe
2024-12-06 09:43:44.8814-INFO Microsoft Windows NT 10.0.26100.0 - 64
2024-12-06 09:43:45.2997-INFO UpdateTaskRunGeo
2024-12-06 09:44:45.3005-INFO UpdateTaskRunSubscription

似乎没有一场

额外信息

No response

我确认已更新至最新版本

我确认已查询历史issues

@zhuhr213 zhuhr213 added the bug Something isn't working label Dec 6, 2024
@OnceUponATimeInAmerica
Copy link
Contributor

OnceUponATimeInAmerica commented Dec 6, 2024

This is probably due to merging of http and socks local inbounds (into a single socks inbound which can now also accept http proxy connections). I don't think this merging (where v2rayN now listens on a single port) was a good idea. Because so many settings in so many places (including custom configs, env variables, ssh configs, ...) get broken with this change and have to be changed!

I strongly suggest to bring back the old inbound config (socks_proxy at default port of 10808, http_proxy=socks+1)

Also another reason could be the changing of dokodemo api inbound port (for stats) in the latest builds (which could also break stats display for custom/json configs).

Thanks you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants