• 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.

Resolved No Firewall changes possible with 18.0.52

Hi all,
after the upgrade to 18.0.52 I tried to confirm the Firewall changes but I get always the following issue:
View attachment 23204

Also deleting all manual added rules and just deploying the standard settings is no longer possible.
Anyone else with the same issue?
Same problem here unfortunately after updating to 18.0.52.
Is this a known bug for the firewall?
 
Are you using the latest Firewall extension version 2.0.3?
Have you set longer timeouts in panel.ini, e.g.
Code:
[ext-firewall]
confirmTimeout = 120
confirmTimeoutCli = 120
 
My server still has the issue.
I suspect that the problem may be related with fail2ban which also modifies the iptables.
My last 2 attempts to reload the firewall rules with the 18.0.52 version resulted in the inaccessibility of my server and I needed to restore my vserver from the latest backup image.
Unfortunately, I only have a reseller license and Plesk does not offer support for it.
I am also going on vacation and thus cannot administer my server for a while.
So I am going to wait until Plesk comes up with a working solution.
As the problem did come up with the 18.0.52 and do see a changed GUI for the firewall, I strongly believe that the issue is a bug in the new revision and I would suggest rolling back to the previously working firewall module until the problem is understood and solved.
 
Thank you PeterKI
I disabled Fail2Ban,
Then applied the new firewall rules, this succeeded.
than i enabled Fail2Ban again.

Maybe its excessive, but we have 3474 Banned IP's.
Nevertheless, Disable/Enable Fail2Ban could be integrated in the script when applying new FirewallRules.
 
Back
Top