• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved NGINX 502 bad gateway after activating fail2ban

LaurentR2D2

Plesk Certified Professional
Plesk Certified Professional
OS‪CentOS Linux 7.4.1708 (Core)‬ProduitPlesk Onyx
Version 17.5.3 Mise à jour n° 23, dernière mise à jour le 2 Oct 2017 03:51

Hello,

I can't activate fail2ban, since I always get a NGINX 502 bad gateway error on my websites when I do it. Should I reinstall it like it was suggested for Debian/Ubuntu systems ? ModSecurity is activated with Atomic Basic ModSecurity, and intermediate settings.

Thank you
 
Hi LaurentR2D2,

did you probably forget to insert "localhost" your server IP's on your server to the whitelist of Fail2Ban?

Should I reinstall it like it was suggested for Debian/Ubuntu systems ?
This is never a bad idea, to solve ( possible ) issues/errors/problems, but from my point of view, you should rather investigate the root cause of your issue, as you might experience the very same issues/errors/problems again afterwards. :(
 
Hi LaurentR2D2,

did you probably forget to insert "localhost" your server IP's on your server to the whitelist of Fail2Ban?


This is never a bad idea, to solve ( possible ) issues/errors/problems, but from my point of view, you should rather investigate the root cause of your issue, as you might experience the very same issues/errors/problems again afterwards. :(

I've added the ip of my server, and the problem is solved. There was 127.0.0.1/8 in the whitelist, but obviously it was not enough. Thank you :)
 
Back
Top