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

Forwarded to devs Port input for firewall rules does not allow multiple (non-consecutive) ports

Lau

New Pleskian
TITLE:
Port input for firewall rules does not allow multiple (non-consecutive) ports​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx 17.5 Windows​
PROBLEM DESCRIPTION:
Plesk provides a frontend for the windows firewall, to setup custom rules. The windows firewall allows to state multiple consecutive and non-consecutive ports within a single rule, as in the following example:

50001-50003, 50006, 50008

The plesk frontend does not allow comma separated ports at all, but either a single port or a consecutive port range.​
STEPS TO REPRODUCE:
Try to input the following port range in a new firewall rule within plesk:

50001-50003, 50006, 50008​
ACTUAL RESULT:
An error message stating an invalid format is shown.​
EXPECTED RESULT:
The port range is correctly applied to the firewall rule.​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Back
Top