vikarti.anatra/nginx-ultimate-bad-bot-blocker
1
0
Fork 0
mirror of https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker.git synced 2025-09-02 18:50:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Readme Updated

Browse source
This commit is contained in:
Mitchell Krog 2017-02-11 16:31:51 +02:00
parent 8dcb54767e
commit f8b5feb8a3
1 changed files with 14 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
README.md
View file

@ -8,23 +8,18 @@
</table>
# Nginx Bad Bot and User-Agent Blocker, Spam Referrer Blocker, Anti DDOS, Bad IP Blocker and Wordpress Theme Detector Blocker
## The Ultimate Nginx Bad Bot, User-Agent, Spam Referrer Blocker, Adware, Malware and Ransomware Blocker, Clickjacking Blocker, Click Re-Directing Blocker and Bad IP Blocker with Anti DDOS System, Nginx Rate Limiting and Wordpress Theme Detector Blocking
##### The Ultimate Nginx Bad Bot, User-Agent, Spam Referrer Blocker, Adware, Malware and Ransomware Blocker, Clickjacking Blocker, Click Re-Directing Blocker and Bad IP Blocker with Anti DDOS System, Nginx Rate Limiting and Wordpress Theme Detector Blocking
### Version 2.2017.03
### Created by: https://github.com/mitchellkrogza
### Copyright Mitchell Krog <mitchellkrog@gmail.com>
##### Created by: https://github.com/mitchellkrogza
##### Copyright Mitchell Krog <mitchellkrog@gmail.com>
#### For Nginx Web Server - https://www.nginx.com/
### Recommend to be saved as: /etc/nginx/conf.d/globalblacklist.conf
Why? .... because all files located in /conf.d/ are automatically loaded by Nginx in the main nginx.conf file.
### See sample Nginx Vhost config at: (Please read full instructions too) https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/blob/master/NGINX-SSL-Site-Config-Example.md
#### Includes the creation of a google-exclude.txt file for creating filters / segments in Google Analytics (see instructions lower down)
#### Includes the creation of a google-disavow.txt file for use in Google Webmaster Tools (see instructions lower down)
- Configuration instructions are here [configuration](#configuration)
- For Nginx Web Server - https://www.nginx.com/
- See sample Nginx Vhost config at: (Please read full instructions too) https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/blob/master/NGINX-SSL-Site-Config-Example.md
- Includes the creation of a google-exclude.txt file for creating filters / segments in Google Analytics (see instructions lower down)
- Includes the creation of a google-disavow.txt file for use in Google Webmaster Tools (see instructions lower down)
### WHY BLOCK BAD BOTS ?
@ -125,6 +120,7 @@ A test with curl using one of the test command line's documented in the /conf.d/
For bot's or spiders that you still want to allow but want to limit their visitation rate, you can use the built in rate limiting functions I have included. The file is extensively commented throughout so you should figure it out otherwise simply message me if you are having problems.
#CONFIGURATION OF THE NGINX BAD BOT BLOCKER:
### PLEASE READ CONFIGURATION INSTRUCTIONS BELOW THOROUGHLY
@ -192,6 +188,10 @@ Add your own ip addresses to make sure they are whitelisted (one per line as per
- `limit_conn_zone $binary_remote_addr zone=addr:50m;`
**Make sure** that your nginx.conf file contains the following include directive
- `include /etc/nginx/conf.d/*`
**PLEASE NOTE:** The above rate limiting rules are for the DDOS filter, it may seem like high values to you but for wordpress sites with plugins and lots of images, it's not. This will not limit any real visitor to your Wordpress sites but it will immediately rate limit any aggressive bot. Remember that other bots and user agents are rate limited using a different rate limiting rule at the bottom of the globalblacklist.conf file.
The server_names_hash settings allows Nginx Server to load this very large list of domain names and IP addresses into memory.