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

节点显示问题 #48

Open
ainy0293 opened this issue Apr 24, 2023 · 3 comments
Open

节点显示问题 #48

ainy0293 opened this issue Apr 24, 2023 · 3 comments

Comments

@ainy0293
Copy link

请回答下列问题。不按模板发的 issue 将直接被关闭。

  1. 如果你没有遇到任何错误和不正常,请在此处回答你想发表的内容:
    节点显示问题,目前我使用的服务商提供了很多节点,但用这个GUI界面,只显示了一部分
  2. 你正在使用哪个版本的 V2RayXS,你的 macOS 系统版本?
    CNY版本, MacOS 10.15.7 (19H1419)
  3. 如果你在操作 V2RayXS 的时候遇到程序崩溃/无反应,请描述你的操作,之后在命令行(终端.app)里运行/Applications/V2RayXS.app/Contents/MacOS/V2RayXS,重复上述操作直至软件崩溃,把终端里的输出贴到下面指定的地方。
无崩溃行为
  1. 如果 V2RayXS 没有发生崩溃,但是有一些不正常行为,比如上次勾选了 mux,再次打开,mux 的钩没有了。请描述你遇到的不正常行为。

  2. 如果 V2RayXS 一切正常,但网络依然不如你所预料,请首先把 log level 切换到 debug,再次访问你想访问的网站。然后点击 V2RayXS 的 view current config.json,将弹出的浏览器内的配置文件粘贴到下面指定的地方,但是隐藏掉ip/端口/id等信息。

在这里粘贴配置文件内容

然后点击 V2RayXS 的view log,把 error.log 中的输出贴到下方:

在这里贴上 error.log
  1. 其他你认为可以帮助开发者和你一起解决问题的信息:
    节点显示问题, 目前我使用的服务商提供了很多节点,但用这个GUI界面,只显示了一部分,如图:

image

实际上我的节点数比这要多很多

@tzmax
Copy link
Owner

tzmax commented Apr 25, 2023

@ainy0293 It is possible that the sharing connection protocol obtained by your subscription address does not support parsing. One of the links that failed to import (not the full subscription address) to share with me? note, remember to replace sensitive information such as ip port uuid

@ainy0293
Copy link
Author

Hi, @tzmax I use the service provided by ikuuu and they have many nodes. Url is https://ikuuu.eu/, my subscription address is https://api.sub-100.one/link/*******?sub=3&extend=1. Their service also has free nodes, but the number of nodes is very small, maybe it can't reproduce my problem

@iKuuuVPN
Copy link

iKuuuVPN commented May 4, 2023

Hello everyone. This is iKuuu VPN.

We apologize for the inconvenience caused to our client and the developers due to the recent issue.

To provide a brief summary, the issue was caused by the sub=3 query, which only sends V2ray nodes(but we're now moving to ss protocol, so new nodes will not ship to the customer). However, we have now resolved this by sending both SS and V2ray nodes to the customers who are using sub=3.

We want to clarify that this was not a client issue but rather an issue on our end. We are actively working to prevent such issues in the future.

Lastly, we would like to thank the developers for creating a tool that simplifies anti-censorship and thank them for their patience and understanding towards our customers.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants