• 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 Bug in plesk firewall script /opt/psa/var/modules/firewall/firewall-active.sh

PeterKi

Regular Pleskian
TITLE:
Bug in plesk firewall script /opt/psa/var/modules/firewall/firewall-active.sh​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onys 17.8.11 on vServer with Ubuntu 16.04.5 LTS​
PROBLEM DESCRIPTION:
There is a bug in the version checking part of the firewall script /opt/psa/var/modules/firewall/firewall-active.sh
The line: iptables_version=`/sbin/iptables --version | awk -F '.' '{print $2$3}'`
does give the value 60 on version 1.6.0
Thus the version check if [ $iptables_version -gt 420 ] does the comparison [60 -gt 420 ] which of course leads to unwanted behavior.
The else part does the job too but results in an unnecessary longer run time of the script.
Version checking is not an easy task and it is implemented too simple.
Instead of adding a full fledged version comparison it may be it is easier to just check if the -w option is available e.g. by using something like man iptables | grep -- --wait​
STEPS TO REPRODUCE:
run script with version 1.6.0​
ACTUAL RESULT:
always ignores the -w option of iptables on version 1.6.0​
EXPECTED RESULT:
use the -w option of iptables​
ANY ADDITIONAL INFORMATION:
see suggested solution​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Thank you for this report.
Bug was confirmed and submitted as PPPM-9487
 
Back
Top