• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Cannot update an existing firewall rule to allow all ips

gennolo

Basic Pleskian
Username:

TITLE

Cannot update an existing firewall rule to allow all ips

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.53 Update #1- Centos 7.9 x64

PROBLEM DESCRIPTION

I am encountering a problem with the Plesk Firewall interface after the latest updates.

I often need to "unblock" an already existing firewall rule binded to single IP or a group of IPs
and remove the IP block , but I have an unexpected behaviour from last weeks.

STEPS TO REPRODUCE

- I click on the name of a rule already having a block per IP ("Allow incoming from x.x.x.x ")
- I select Action > Allow from the lateral menu
- I click on "SAVE"

ACTUAL RESULT

I only get a success message "The rule is saved successfully" with no possibility to apply the actual changes.

EXPECTED RESULT

I would expect the rule to be changed to "Allow incoming from all" and for Plesk to offer me to apply the script to update the firewall.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
We found out that the issue was already reported (in a different wording though, so I did not find it before) as EXTPLESK-4720. It has already been fixed. The fix will be published this upcoming Monday.
 
Back
Top