• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

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