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
admin@admin.test account locked out, changing password with cake doesn't work #3716
Comments
You have tripped over the bruteforce protection (tried too many times). Either wait 5 minutes or do this: mysql -u misp -p misp
|
Hi, no it's not a brutefore problem, it's something with the login that's not working correctly, as noted by Note1+2. I just tried to login again, and checked the bruteforces table:
Yet, it just says admin@admin.test is locked out due to invalid login attempts. |
I could either debug the problem but I would need to get better logging to be able to see what's going wrong here, or, This a fresh install so there is nothing in the instance that's of importance |
Ok, found the underlying problem! |
I seem to have the same problem, do you happen to know what triggered the config update with the missing values? I am still very new to MISP and can't figure out why my working config was overwritten |
Work environment
Expected behavior
At first it worked as expected, I could login and manage to change password for admin@admin.test.
Actual behavior
The the session timed out, and I try to login with admin@admin.test I get this message on the first login attempt:
"You have reached the maximum number of login attempts. Please wait seconds and try again.
Error: The requested address '/users/login' was not found on this server."
Note1: I've never seen "invalid username/password" message before the message above.
Note2: There isn't a value printed out for the seconds
Steps to reproduce the behavior
I've tried to reset the admin@admin.test password too via:
sudo /var/www/MISP/app/Console/cake Password admin@admin.test Password1234
as explained by #1160 and other Issues,
but that doesn't help....
Logs
The only thing that's written in /var/www/MISP/app/tmp/logs/error.log:
But that doesn't help much... :(
The text was updated successfully, but these errors were encountered: