This Forum Post is all about working with BBQ patterns. If you have questions about the patterns used by BBQ to block bad requests, or if you have ideas or suggestions, you may post them publicly using the form below, or contact us directly to share privately. Thank you!
Browse support forums for BBQ Pro »
Forum : Patterns
There are 8 posts in this forum.
I checked my site’s access log and found thousands of entries like this:
Unknown robot, identified by User Agent:
bot 1234:Does BBQ Pro block these unknown or bad bots? These unknown bots are hogging all of my CPU resource. Any help would be appreciated.
Glad to help. There are millions of bad bots out there, and BBQ blocks a lot of the worst, but there always will be new/rare bots that creep up. The good news is that you can add your own patterns to block bad bots via BBQ’s Custom Patterns screen. In your case, the pesky bot is reporting a User Agent of “bot 1234:”. So with this information, you can visit the Custom Patterns screen and add the following under the “User Agents” section:
That will block all future requests from that bot. Using this technique you can block any bot that may be causing issues. Note: make sure that “Custom Patterns” are enabled in the plugin settings.
Learn more about blocking nuisance requests »
I was wondering why you added “revslider” as a pattern? It breaks my site with some css?
The plugin was hacked last year, resulting in endless malicious scans, as explained here:
https://perishablepress.com/block-revslider-scans/
Thus it is blocked in BBQ Pro, but you can disable the pattern and all revslider requests will be allowed.
Thanks, is there any version where this exploit is fixed? I can update to the latest version. Id rather not allow it if it is a risk
Personally I do not use the plugin so no idea. But I would recommend contacting the developers and asking them, or maybe asking around in the WP forum or similar. Hopefully someone on the revslider team will respond.
I am getting search spam on my wordpress search that looks like the following:
Is there a pattern that I can use to block these?
You can block the first two patterns by adding
invokefunctionto the BBQ Custom rules. For the others, it depends on which string always is present in the request. Here is a guide that explains more about how to block nuisance requests.