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

Feature Request: Add Custom Inbound Configuration Field to Host Settings #1611

Open
sahmadiut opened this issue Jan 17, 2025 · 1 comment
Open

Comments

@sahmadiut
Copy link

I would like to suggest a new feature for the Marzban panel. It would be helpful to add a field in the host settings that allows users to define a complete custom inbound configuration (such as VLESS, VMESS, Trojan, etc.). This custom configuration should allow Marzban to only replace the uuid and remark of the user in the custom configuration, while the rest of the settings remain as defined by the user.

This feature is intended to simplify the setup process for configurations like V2Ray. By providing a fully pre-configured inbound configuration, users wouldn't need to manually set other options. Marzban can use this custom configuration field if it exists, otherwise, it will fall back to the default settings.

For example, consider the following configuration:

vless://[email protected]:2083?encryption=none&security=none&type=xhttp&path=%2F&mode=stream-up&extra=%7B%0D%0A%20%20%22downloadSettings%22%3A%20%7B%0D%0A%20%20%20%20%22address%22%3A%20%22node.second.address%22%2C%20%0D%0A%20%20%20%20%22port%22%3A%202083%2C%20%0D%0A%20%20%20%20%22network%22%3A%20%22xhttp%22%0D%0A%20%20%7D%0D%0A%7D#Xhttp%20US%20%F0%9F%87%BA%F0%9F%87%B8%20%2838989487.9%29

This configuration includes specific options for a VLESS setup, and the only changes Marzban would need to make are updating the uuid and remark fields. All other settings would remain untouched.

Additional Notes:

Adding this feature seems relatively straightforward but offers significant benefits in terms of flexibility. It allows users to customize configurations easily and handle unforeseen settings or features introduced in future versions of the Xray core. Since the Xray core is constantly evolving with new settings and options, this field would ensure Marzban remains adaptable and compatible with such updates without requiring frequent changes to the UI or backend logic.

Image

@M03ED
Copy link
Collaborator

M03ED commented Jan 17, 2025

Xray core is not the only goal for marzban , gozargah is planning to add other cores to marzban , also marzban provide multiple client support and implementing this have 2 side , add this option for every client in host settings or make a reverse engineering, this pr will say open but I don't think we see this soon or ever.

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

2 participants