• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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