Fix Config Link in Readme

This commit is contained in:
Mitchell Krog 2017-03-26 12:09:50 +02:00
parent e9ee243973
commit f33357c528

View file

@ -15,7 +15,7 @@
##### Created by: https://github.com/mitchellkrogza
##### Copyright Mitchell Krog <mitchellkrog@gmail.com>
# [Configuration instructions are here](# configuration-of-the-nginx-bad-bot-blocker)
# [Configuration instructions are here](#configuration-of-the-nginx-bad-bot-blocker)
- 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)
@ -113,7 +113,8 @@ 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:
# CONFIGURATION INSTRUCTIONS
#CONFIGURATION OF THE NGINX BAD BOT BLOCKER:
### PLEASE READ CONFIGURATION INSTRUCTIONS BELOW THOROUGHLY
**If you miss one step you will get an nginx EMERG error. This is normally a result of not downloading either blockbots.conf, ddos.conf, whitelist-ips.conf, whitelist-domains.conf or blacklist-user-agents.conf into your /etc/nginx/bots.d folder. If any of the include files are missing Nginx will EMERG and will not reload.**