-
Notifications
You must be signed in to change notification settings - Fork 510
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
IP blocking not working for failed logins #2135
Comments
Fixed in the Too many login attempts. Please try again in 30 seconds. Also a "Locked out" record is added to the Manage > Logs > Users. |
Would it be possible to lock it for at least 1 hour? 30 seconds it really too little and it won't slow down possible brute force login attack form multiple IP addresses. |
We've changed it to 10 minutes. |
10 minutes sounds like too little, we would prefer at least 1 hour or even 12 hours. Could you please add it as a setting or at least a hidden config file preference? Could it also count the bad login attempts per user? If you only ban based on IP addresses it might not be effective. One of our websites was targeted by a botnet attack recently. It made 200,000 login attempts in 17 hours using 10,000 unique IP addresses. So each IP address only made 20 attempts in 17 hours and nothing got banned. So we are looking for a solution to show captcha if the login is for use who had more than 20 bad login attempts in last day or so. That would prevent password guessing for large-scale botnets. Thanks, |
I tried to make several bad login attempts to see if Freescout will block my IP address.
Unfortunately nothing happened, I only saw this in my browser:
So I checked public_html/storage/logs/laravel-2022-08-04.log and this is what is says
So it seems Freescout has the code to ban IP addresses trying to guess the password, but it's not working.
app-logs/users
show all the good and bad login attempt properly.Our Freescout version is 1.8.21.
Hopefully you will be able to fix this.
The text was updated successfully, but these errors were encountered: