No Plesk Firewall rules are loaded after server reboot

Created:

2016-11-16 13:17:04 UTC

Modified:

2017-08-19 03:09:13 UTC

0

Was this article helpful?


Have more questions?

Submit a request

No Plesk Firewall rules are loaded after server reboot

Applicable to:

  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux

Note: This article has the reference to the issue with the fix available:

  • #PPPM-3993 "Plesk firewall rules sometimes failed to load after server restart, which could result in the server becoming inaccessible."
    Fixed in:
Please consider updating your server:

Symptoms

No actual rules are present in iptables after server reboot on CentOS 7.2 and Ubuntu 12.04.

All rules were configured using Plesk Firewall extension.

fail2ban is also installed and enabled for auto start.

It is possible to find these errors in system journal:

 psa-firewall[975]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
psa-firewall[975]: psa-firewall: failed to apply firewall configuration

Cause

fail2ban was not completely loaded when psa-firewall started applying iptables rules.Only one app can add rules to iptables at one time.

Bug PPPM-3993 . It is fixed in Plesk 12 MU #81, Plesk 12.5 MU #26 and Plesk Onyx .

Resolution

Install the latest microupdates or upgrade to the latest Plesk version .

Have more questions? Submit a request
Please sign in to leave a comment.