• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

fail2ban config gone after reboot

Thomas Runte

New Pleskian
Hi folks,
I am using fail2ban in the plesk (12.5.30 Update #27, with Ubuntu 14.04) admin interface . Whenever I reboot my server I can see that the iptables configuration of fail2ban is gone. I am wondering if this might be due to iptables-persistent because what I find after reboot is the configuration from the /etc/iptables/rules.v4 file.
I have had a look at /etc/init.d/fail2ban which has a reference to iptables-persistent:

# Should-Start: $time $network $syslog iptables firehol shorewall ipmasq arno-iptables-firewall iptables-persistent ferm

My understanding of this is that iptables-persistent should start before fail2ban (correct ??) which sounds right.
When I go to plesk and save the fail2ban settings again my fail2ban configuration is restored. I have tried to look at boot.log and dmesg to reveal in what sequence services are started but was not successful. boot.log is empty and dmesg only contains firewall logs.
Has anybody seen this problem or has an idea how to solve it ?
Cheers Thomas
 
Last edited:
Back
Top