V2.2017.07 - MAJOR VERSION UPDATE !!!

32 views
Skip to first unread message

Mitchell Krog Photography

unread,
Apr 20, 2017, 10:38:44 AM4/20/17
to nginx-ultimate-...@googlegroups.com
A major version update has taken place today

Welcome to Version 2.2017.07 of the Nginx Ultimate Bad Bot Blocker

PLEASE READ UPDATED CONFIGURATION INSTRUCTIONS CAREFULLY !!!!

New include files have been introduced to allow more customization to users.

WITHOUT the new include files in your /etc/nginx/bots.d/ folder Nginx will EMERG❗️and fail on reloading Nginx.

Please make sure your /etc/nginx/bots.d/ folder includes all the following new ❗️required❗️ include files.

- bad-referrer-words.conf
- blacklist-ips.conf
- blacklist-user-agents.conf
- custom-bad-referrers.conf
- whitelist-domains.conf
- whitelist-ips.conf

All blacklisted IP's and Ranges including the Cyveillance and Berkeley Scanner sections have been moved into the include file blacklist-ips.conf

Each new include file is documented on how you can customize it.

PEOPLE USING THE AUTO UPDATE SCRIPT

You will run into and Nginx [EMERG] ❗️ error on your next update when it reload Nginx and finds missing include files. 
Please download the new include files to your /bots.d/ folder as per the configuration instructions. 

The new include files allow a whole lot more customization by users. 

- The Bad Referrers Words Scanning List can now be modified in bad-referrer-words.conf to your liking and will not be overwritten when updating.

- The Blacklisting of IP addresses and IP Ranges can now be customized using the include file blacklist-ips.conf and will not be overwritten with updates.

- A new include file custom-bad-referrers.conf file allows to add your own bad referrers to the the blocker that are not already included in the blocker, this once again will not be overwritten with updates.

- The whitelist-ips.conf file has been modified slightly it does not need to have 127.0.0.1 as a listed IP as it is covered elsewhere in the script. It's ok to have 127.0.0.1 in the whitelist-ips.conf file but unnecessary as Nginx will just complain to you about a duplication when you do an nginx -t

To quickly fix your server failing a reload simply run the following and reload nginx

cd /etc/nginx/bots.d
cd /etc/nginx/conf.d
sudo nginx -t
sudo service nginx reload

Apologies to anyone whose Nginx might have failed a reload during an update today. 
These changes are essential to the growth and improvement of the blocker.

Enjoy and please send feedback on the Issues System.



Reply all
Reply to author
Forward
0 new messages