• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Fail2ban and Firewalld

Nadeem Aslam

New Pleskian
Hi

On my server I'm running firewalld on centos7 after which I installed plesk

I have now installed Fail2ban and also did the plesk firewall which I found to just be iptables and not firewalld so I uninstalled that

I want to know if the plesk Fail2ban will be aware of firewalld and will be able to ban ip's successfully

I have made all changes in options in plesk I need for Fail2ban

As I'm a bit of novice I don't want to think I'm protected by Fail2ban and when it comes to crunch it actually fails

I prefer firewalld over iptables - just seems easier for a novice like me

Thanks
 
digging deeper and looking at the jail for apache say i see it's set with

action = iptables-multiport[name=apache, port="http,https,7080,7081"]

which means it will use iptables - which i'm not running so can i just amend that to the action required for firewalld

There must be someone else with similar configuration
 
I think you are a bit confused. Firewalld is just a newer management interface for managing iptables. It still sends all its commands to iptables. My suggestion is to re-install the Plesk firewall and use it in conjunction with fail2ban. Firewalld is more suited to workstations anyway.
 
Back
Top