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

Bug #1200

Open
mahdiismailpuri opened this issue Jul 29, 2024 · 8 comments
Open

Bug #1200

mahdiismailpuri opened this issue Jul 29, 2024 · 8 comments
Assignees
Labels
T: Bug Something isn't working

Comments

@mahdiismailpuri
Copy link

mahdiismailpuri commented Jul 29, 2024

The client whose status was changed to limited mode, after increasing the data limit and changing its status to active mode, xray still rejected its connection. After re-editing the user with the same previous list [edit user], the problem was solved

This problem only happened once and I reproduced it

V 0.6.0 dev

@mahdiismailpuri mahdiismailpuri added the T: Bug Something isn't working label Jul 29, 2024
@erfjab
Copy link
Contributor

erfjab commented Jul 30, 2024

Did you make this change with the Marzban Front or the Marzban official bot?

@DrAmirB
Copy link

DrAmirB commented Jul 30, 2024

You can edit disabled users with telegram bot for now. I have the same issue.

@erfjab
Copy link
Contributor

erfjab commented Jul 30, 2024

You can edit disabled users with telegram bot for now. I have the same issue.

The user's inbound editing has a front-end bug that will be fixed soon.

@mahdiismailpuri
Copy link
Author

The first change was made by the bot through the API But edit the user to fix the problem through the front

@erfjab
Copy link
Contributor

erfjab commented Jul 30, 2024

The first change was made by the bot through the API But edit the user to fix the problem through the front

So your bot has a problem.

@mahdiismailpuri
Copy link
Author

The first change was made by the bot through the API But edit the user to fix the problem through the front

So your bot has a problem.

no After increasing the data, the user status limit was active in the panel But it prevented the user from connecting The bot has been working through the API for a long time, and this issue arose from the new DEV update

@erfjab
Copy link
Contributor

erfjab commented Jul 30, 2024

The first change was made by the bot through the API But edit the user to fix the problem through the front

So your bot has a problem.

no After increasing the data, the user status limit was active in the panel But it prevented the user from connecting The bot has been working through the API for a long time, and this issue arose from the new DEV update

Well, I'll check his commits and let you know the result.
Added to Tasks ✅

@erfjab erfjab self-assigned this Aug 7, 2024
@sons-of-liberty
Copy link

I have the same issue. I think it happened after i added a new inbound and disabled it for all users. Though it doesnt happen for all users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants