tomdkat

I understand your points and I tend to agree with you. However, adding lots of IP address to the htaccess file can cause performance degradation in the web server since it must check each IP address against the ones in the “block” list and the longer the list, the more searching that must be done. I used to have a _lot_ of IP addresses in my htaccess file and about a month ago, I deleted those entries to give BruteProtect a chance to add these address to their “master” list.

I would certainly think BruteProtect, alone, wouldn’t be enough to prevent server overload so you would need to supplement it with another plugin or firewall of some kind. Your idea of having BruteProtect effectively “maintain” the htaccess file is interesting and one I would like the BruteProtect maintainers to comment on. 🙂

In the past, I also blocked IP addresses via the htaccess file but that can cause performance degradation if too many IP addresses are being blocked this way. I’ve since removed these IP address from the htaccess file to give BruteProtect a chance to capture whatever info it wants from hacking attempts from these addresses.

I don’t think BruteProtect is intended to actually “block” IP addresses in the manner rules in the htaccess file can. Blocking IP addresses via htaccess can prevent IP addresses from accessing the entire site, which can provide more “protection” than BruteProtect can.

Just my personal experience and two cents. 🙂

Thanks! I’m experiencing the same issue and changing the policy did the trick!

Peace…