• 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 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