Before you submit
Problem
there are always more features on any core (xray, clash, etc) then on a panel and panels cannot keep up with the latest features nor can be as fast as core development
Proposed solution
when a new core is added, there would be a full support. Noting should be ignored. At the moment as I tested for example clients are ignored for inbounds. because it is managed by the panel.
With this feature, advanced users can benefit the core json editor to apply changes remotely. Also having several custom config and switch between them
Of course, no users, hosts, etc should be associated with this headless core
Alternatives considered
running standalone xray core in the server with json file
./xray run -c config.json
then connection from a core managed by panel to this standalone core
Area
Nodes
Impact
Important
Examples or references
No response
Additional context
No response
Before you submit
Problem
there are always more features on any core (xray, clash, etc) then on a panel and panels cannot keep up with the latest features nor can be as fast as core development
Proposed solution
when a new core is added, there would be a full support. Noting should be ignored. At the moment as I tested for example clients are ignored for inbounds. because it is managed by the panel.
With this feature, advanced users can benefit the core json editor to apply changes remotely. Also having several custom config and switch between them
Of course, no users, hosts, etc should be associated with this headless core
Alternatives considered
running standalone xray core in the server with json file
then connection from a core managed by panel to this standalone core
Area
Nodes
Impact
Important
Examples or references
No response
Additional context
No response