• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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