Code: Select all
###block "The Knowledge AI" bot SetEnvIfNoCase User-Agent "The Knowledge AI" bad_bot Deny from env=bad_bot
Yes, I can see that the tech support for the hosting service has added similar code to the .htaccess file, but it must not have worked. I know this because (a) the site is back down again after they said they reactivated it, and (b) part of the email thread included an admin from their side saying a different IP address was now the issue. (More on that, below. Yes, I know blocking IPs isn't terribly helpful.)
Yes, the hosting service doesn't apportion Apache cpu time to individual sites, so if it takes Apache more cpu time, I don't care.
(Oops, my bad. I didn't realize there had been a change in the nomenclature.)I would add that doing this within phpBB using an extension (phpBB does not use MODs any more) is that you will still have the problems that you have now with the bot hitting your board.
Yeah, that's what I thought, too. Clearly, that hasn't been enough.
Thanks. I hadn't heard of the last two, but CloudFlare was one of the suggestions that came from the host. I've got my top men working on it. (Yes, "top men".)
I do have access logs, but not real-time. Since HostGator shuts off the site after 90s of cpu usage >50%, log files that are batched up into 24-hour blocks isn't very useful.
Ooo, this looks interesting. I would still have to use the [n].htaccess[/b] version, but I will check it out. Thanks, Solid.</Solidjeuh> wrote: ↑Fri Jun 14, 2019 11:21 amSee this
https://github.com/mitchellkrogza/apach ... ot-blocker
Only good bots follow that. It won't solve this issue.
Then what would be the use for the bot blockerJohn connor wrote: ↑Mon Jun 17, 2019 4:17 amOnly good bots follow that. It won't solve this issue.
Disallow:/function if they don't follow it ... ? Then the .htaccess would be better?