-
-
Notifications
You must be signed in to change notification settings - Fork 859
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]: Can't login after leaving admin team #3422
Comments
seems like it should be handled when an admin leaves an admin team ? if an admin leaves should they still be allowed to login as user? if yes we can mark it as with application true however if an admin should not be allowed to login as normal user after he leaves this seems to be correct behaviour? |
This also happens when an instance is set to "Open Registration", users register and then the instance is set to "Closed Registration". Workaround: |
I still cant log-in, first 404 site ban then i stopped getting this error today, i cleared cache, used a new private tor window, reset my password, checked modlog, and nothing helped, my username is "MJB9000" , i think i was blocked as i have seen but i still haven't interacted or done anything in lemmy.world, i just created this account, something is not right, please look into it. contact: hi@mahmoudjbaydoun.com |
Me2 johannisp.123@gmail.com cannot login without any error message. It just does not happen anything when pressing login. |
Still cant log in, can someone please help? |
I encountered this after removing my everyday user from the server admin team to increase server security. I'm not sure if this was happening before the 0.18.3 upgrade but showed up after the upgrade. Confirmed by checking the API responses in the browser tools - you'll see "record not found" when trying to log in with this specific user. Used the following workaround, seems to be working for me:
|
Requirements
Summary
If the original administrator leaves the admin team, that user can no longer log in if the instance is set to require user registration applications.
Steps to Reproduce
Technical Details
Root Cause
utils.rs -
check_registration_application
requires the user to be admin or have an approved application.Since the user was created without an application, a "record not found" error is thrown, which prevents the login.
Error Log
Version
0.18.0
Lemmy Instance URL
No response
The text was updated successfully, but these errors were encountered: