-
Notifications
You must be signed in to change notification settings - Fork 611
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
Comments
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. |
Not possible. but you can use Marzban integrated Telegram Bot to exclude the inbound for all users at once (but it's really slow) |
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. |
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?
The text was updated successfully, but these errors were encountered: