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

How to prevent new inbounds from being accessible to all users? #1657

Open
q1LLa opened this issue Feb 15, 2025 · 5 comments
Open

How to prevent new inbounds from being accessible to all users? #1657

q1LLa opened this issue Feb 15, 2025 · 5 comments

Comments

@q1LLa
Copy link

q1LLa commented Feb 15, 2025

When adding a new account to a system with a new host (node), the new inbound is automatically opened to all existing users by default.

How can I add new inbounds without making them accessible to all users?

Is there a setting for this?

@mishablokhin
Copy link

Uncheck this checkbox while adding new node in Marzban Settings:

Image

@q1LLa
Copy link
Author

q1LLa commented Feb 15, 2025

Uncheck this checkbox while adding new node in Marzban Settings:

Image

It's not about that. I add exactly the inbounds via the configuration in "inbounds": [. And immediately this inbox becomes available to all users.

My working principle is as follows: 1 panel on one server and many nodes on other servers. 1 inbound = 1 node/server, so that X people can be distributed to each server. But as soon as you create a new inbound, all existing users are allowed to use it.

@P1nk-L0rD
Copy link

It's not about that. I add exactly the inbounds via the configuration in "inbounds": [. And immediately this inbox becomes available to all users.

My working principle is as follows: 1 panel on one server and many nodes on other servers. 1 inbound = 1 node/server, so that X people can be distributed to each server. But as soon as you create a new inbound, all existing users are allowed to use it.

Unfortunately, now it is not possible in Marzban because when you create a user with a limited amount of inbounds, the panel does not save the allowed inbounds, but it saves the excluded inbounds. So, when you create a new inbound, it is not automatically added to the list of excluded inbounds and is available for all users.

@mdjvd
Copy link

mdjvd commented Feb 20, 2025

Not possible. but you can use Marzban integrated Telegram Bot to exclude the inbound for all users at once (but it's really slow)
another option is to use this script (thanks MO3ED):
https://github.com/M03ED/Marzban_Inbound_Updater

@q1LLa
Copy link
Author

q1LLa commented Feb 20, 2025

Not possible. but you can use Marzban integrated Telegram Bot to exclude the inbound for all users at once (but it's really slow) another option is to use this script (thanks MO3ED): https://github.com/M03ED/Marzban_Inbound_Updater

Why is marzban working so slowly with the database?

There are very simple SQL queries that are executed in a fraction of a second.

It feels like the requests go into 1 thread for each user.

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

4 participants