• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Firewall rules not applied after reboot

Deagan

New Pleskian
TITLE:
Firewall rules not applied after reboot​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx 17.5.3 Update #47, CentOS 7.5 / Virtual machine running under Virtuozzo 7 latest version / kernel 3.10.0-693.17.1.vz7.43.10​
PROBLEM DESCRIPTION:
After updating to CentOS 7.5 the Plesk firewall rules are not applied after a reboot. CentOS 7.4 worked without problems.​
STEPS TO REPRODUCE:
- Install Plesk / CentOS 7.4
- Update os to CentOS 7.5: yum update
- Reboot​
ACTUAL RESULT:
Firewall rules are not applied.

After reboot clicking modify firewall rules > apply > applies the firewall rules again, then fail2ban > apply to create fail2ban rules

I did install this bugfix, but this did not resolve the issue:
Plesk Firewall rules are not active if restart/reload iptables​
EXPECTED RESULT:
Plesk firewall rules applied after reboots to prevent unexpected downtime.​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Back
Top