WPChef

Let us know if you have any caching plugin installed. Also, can you share information from the debug page of the plugin?

Thank you for you feedback. We agree this part of the plugin can be streamlined better. We’ll add this project to our roadmap.

If you have issues (temporary or ongoing) with file permissions, the mentioned file might not have updated, while the other ones have. This is one way the file got outdated. Another way could be during its update there was a glitch (network related, server overloaded, out of disk space etc) and the bottom part of the file got lost (got written incompletely to the file). You can try to delete the plugin, install it again and check if the file is complete after that. If it is, you should see the error.

Hi Paoloeuvard,

Thank you for sharing your feedback, and I’m truly sorry to hear about the frustration you experienced with Limit Login Attempts Reloaded. We can understand how overwhelming a high volume of email notifications can be and the impact it had on your workflow and website management.

Here are a few steps and solutions that might help address the issues you encountered:

1. Adjusting Notification Settings:
   To prevent your inbox from being overwhelmed, you may turn off email notifications in the plugin settings. This way, you can reduce the frequency of alerts or disable them altogether while still keeping your site secure.
2. False Positives and Fine-Tuning:
   A high number of detections may sometimes be attributed to aggressive bots or even  settings within your hosting provider that generate false positives. You can adjust the thresholds for login attempts and lockout periods in the plugin settings to better suit your website’s activity. We’ve created a blog to help our users better understand “fake” login attempts – https://www.limitloginattempts.com/blogs/could-these-failed-login-attempts-be-fake/. 
3. Support for Unique Scenarios:
   We would love to investigate why the plugin detected such a high volume of activity and help ensure your site has correct settings. If you’re open to it, please reach out to our support team directly at [email protected] so we can look into this for you.

We’re sorry to see you go, but we’re committed to learning from your experience to improve Limit Login Attempts Reloaded. If there’s anything we can do to regain your trust or assist further, please don’t hesitate to let us know. Wishing you the best with your website security going forward,
LLAR Team

We believe this article would have been helpful to you: https://www.limitloginattempts.com/blogs/could-these-failed-login-attempts-be-fake/ and yes, there’s an easy way to turn the notifications off.

Let me clarify how Limit Login Attempts Reloaded operates and address your concerns.

LLAR is designed to limit repeated login attempts from a single IP address by blocking further attempts once the limit is reached. However, there are factors to consider:

Hackers and bots often use dynamic IP addresses or networks of compromised devices (botnets), making it seem like attacks are not being blocked. While LLAR blocks login attempts from specific IPs after they exceed the threshold, new IPs within the network can continue trying.

Unlike some plugins that might hide or aggregate data on login attempts, LLAR displays all failed attempts—even those from blocked IPs. This transparency helps site admins monitor activity and detect patterns that might affect site performance, such as an unusually high volume of login traffic.

A high number of login attempts, even if blocked, can still strain server resources. That’s why LLAR alerts you to the activity—it’s an opportunity to consider additional protections, such as firewalls or CDN services, to mitigate potential performance issues.

Our premium version integrates a real-time database of millions of known malicious IP addresses. This feature proactively identifies and blocks threats based on global attack patterns, offering a level of protection beyond what standard plugins provide.

To better understand what happened in your case, I recommend reviewing your raw access logs. These logs can reveal the exact nature of incoming login traffic and confirm whether blocked IPs are continuing attempts or if new IPs are initiating attacks.

While Wordfence is a great tool, it operates differently. LLAR’s focus is on login-specific security, providing detailed visibility into login attempts while offering advanced, database-backed protection in its premium version. For comprehensive security, many users pair LLAR with broader security solutions to cover all aspects of site protection.

We are happy to research further if you wish to do so.

Do you use a custom login page? Can you provide more details on it?
Also, the LLAR plugin counts the number of lockouts which is made of the number of attempts.

Hi Raullanza,

Thank you for taking the time to share your feedback. We take your concerns seriously and want to address them directly.

This particular question has come up in our support forum, and we’ve created an article to explain it further: https://www.limitloginattempts.com/blogs/guides/could-these-failed-login-attempts-be-fake/

To clarify, we do not, under any circumstances, share backend information or generate attacks. Our free version doesn’t even provide us access to your IP data, as it operates entirely on your local database. The increased visibility of attacks through our plugin simply reflects the ongoing threats that websites face daily, rather than any action initiated by us.

For users with a higher risk profile, we offer premium tools designed to provide additional protection. However, the decision to upgrade is entirely up to you.

Thank you for trusting us to assist in keeping your website secure. If you have further questions or concerns, please don’t hesitate to reach out.

-LLAR Team