search

mitchellkrogza / nginx-ultimate-bad-bot-blocker

Nginx Block Bad Bots, Spam Referrer Blocker, Vulnerability Scanners, User-Agents, Malware, Adware, Ransomware, Malicious Sites, with anti-DDOS, Wordpress Theme Detector Blocking and Fail2Ban Jail for Repeat Offenders
Other
3.81k stars 472 forks source link

Same guide for Engintron 2+. With many years gone by? #460

Open ingenuitor opened 2 years ago

ingenuitor commented 2 years ago

Hello guys, do you follow the same guide for Engintron 2+. With many years gone by, I want to make sure I do not bring down the entire working world. Thanks so much, seems like a great much needed solution that even paid solutions don't offer.

I know this as I have a paid solution and it not even close to this powerful in theory. I can't even add a simple Bot block list, it has to be ip by ip, one by one, "quoted direct from their tech support" No way to import and or just hard overwrite to make life easier.

I'm excited to try this and perhaps drop the other solution, if I can get it to work, while being stable and limit false positives.

Originally posted by @ingenuitor in https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/issues/29#issuecomment-1023609857

itoffshore commented 2 years ago

@ingenuitor - it's always recommended to read the changelog whenever you upgrade software.

You may need to change the configuration paths to point to wherever they live now under /opt/engintron (unless they are still under /etc/nginx ?)

The upgrade notes show that engintron does create backups of existing configuration.

ingenuitor commented 2 years ago

@itoffshore So it's ok to run the same as seen here https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/issues/29#issuecomment-1023609857 I'm unsure of what to do and again do not want to break what works. My environment is also Cloud Linux > Imunify 360, sadly i360 doesn't do a very good job or controlling bots with Engintron 2. Thanks again.

itoffshore commented 2 years ago

@ingenuitor all you have to do is make sure the GLOBAL variables at the top of the helper scripts point to wherever the nginx configuration lives under engintron v2

Running the ubbb helper scripts with -h will show where they currently point to.

ingenuitor commented 2 years ago

Hello this is what I got back, thanks nginx -t

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
itoffshore commented 2 years ago

if the config is still under /etc I do not think anything needs to be changed