• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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