Resolved Fail2Ban Causes 502 Bad Gateway

[misterblack]

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

 

[Bitpalast]

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.

 

[misterblack]

That done the trick. Thanks very much!