• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Blocking bad bots

Azurel

Silver Pleskian
I found this feature request
block bad bots by default

Alternatively, a tutorial on how to protect yourself with Plesk would be nice. IgorG wrote a little one
Instruction - Blocking extra bots using nginx
It would be nice if this becomes an official support example (plesk help center) with current agents and a little better explanation. The tutorial is already one year old and surely new agents appeared. See
atmire/COUNTER-Robots
or
monperrus/crawler-user-agents
or
- Bad Bots Bad Bots user-agent / bot
- Crawlers Crawlers user-agent / bot
- Scrapers Scrapers user-agent / bot

Where exactly should the entry be added, so that this block is for all domains?
So? Create a new "bad_bots.conf" in /etc/nginx/conf.d with
Code:
server {
    # List of scrapers and crawlers
    if ($http_user_agent ~ VALUE1|VALUE2) {
       return 444;
    }
}
 
Last edited:
Actually, Plesk WordPress Toolkit has Bot protection section in Security Check option. So, your WP sites can be protected out from the box.
 
Last edited:
Back
Top