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

Request on feature of Clash API and safety defaults #468

Open
kunori-kiku opened this issue Feb 9, 2025 · 1 comment
Open

Request on feature of Clash API and safety defaults #468

kunori-kiku opened this issue Feb 9, 2025 · 1 comment
Labels
enhancement New feature or request low periority To be deployed during the time to deploy Considerable for implementation

Comments

@kunori-kiku
Copy link

Is your feature request related to a problem? Please describe.
In previous versions, there was a clash api option in experimental section, but now it is gone.

Describe the solution you'd like
I hope clash API can be added back, as it is quite convenient to perform remote flow controling.

Describe alternatives you've considered
No

Additional context
The listen address by default for clash API better be 127.0.0.1, and hopefully the panel and the subscription service can also listen to 127.0.0.1.

@kunori-kiku kunori-kiku added the enhancement New feature or request label Feb 9, 2025
@kunori-kiku kunori-kiku changed the title Request on feature Request on feature of Clash API and safety defaults Feb 9, 2025
@alireza0
Copy link
Owner

alireza0 commented Feb 9, 2025

There is a structral problem in Sing-Box which you can not use more than one traffic collector in a same time.
I have reported to the core here and it seems they dont want to fix it.

In S-UI we need the traffic collector to be active for the panel itself. Therefore adding v2ray or Clash API is not possible with curret core codes.

I will try in the future again to put it in panel codes instead of using core codes

@alireza0 alireza0 added to deploy Considerable for implementation low periority To be deployed during the time labels Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low periority To be deployed during the time to deploy Considerable for implementation
Projects
None yet
Development

No branches or pull requests

2 participants