• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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 Fail2Ban Causes 502 Bad Gateway

misterblack

New Pleskian
I am running Plesk 12.5.30 Update #56 on CentOS 7.

This morning I started getting 502 Bad Gateway errors for all websites hosted on my VPS. If I disable Fail2Ban the error goes away.

I think the Plesk CP may have been updated last night.

I have tried rereading ip but stil whenever I re-enable Fail2Ban I get the 502 Bad Gateway errors.

Ideas anyone? Server admin is not my speciality so please be nice.

Thanks
 
The cause of this issue is that fail2ban reads all these requests from the reverse proxy and interprets it as a hacker attack. It then blocks access for Nginx to Apache, because it thinks, it is a brute force attack.

Solution: Please add your host's public IPv4 address and the IP address 127.0.0.1 to fail2ban's whitelist.
 
Back
Top