• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Two questions about the Firewall. Where are the config files and about Extension

Kroptokin

Regular Pleskian
Hi

The documentation (http://kb.parallels.com/en/111283) gives this information about psa-firewall:

Configuration:
/usr/local/psa/var/modules/firewall/firewall-active.sh
/usr/local/psa/var/modules/firewall/firewall-emergency.sh
/usr/local/psa/var/modules/firewall/firewall-new.sh

However on my Plesk 11.5 on Centos 6.4 this path does not exist. (/usr/local/psa/var/modules/ is empty).

My second question is about the Firewall Extension. I see I can install this by going to Updates and Upgrades and it is then available through the Extension Manager. My question is: is this just a GUI for psa-firewall; or is it a new/different firewall?

With thanks

--Justin Wyllie
 
However on my Plesk 11.5 on Centos 6.4 this path does not exist. (/usr/local/psa/var/modules/ is empty).

Make sure you have the extension installed.

My second question is about the Firewall Extension. I see I can install this by going to Updates and Upgrades and it is then available through the Extension Manager. My question is: is this just a GUI for psa-firewall; or is it a new/different firewall?

The extension is just a frontend to the system firewall colloquially known as iptables on Linux. Installing it through Parallels Installer will in fact install psa-firewall package.
 
Firewall Exstension

Hi

Also; just out of interest - before having installed the Firewall Extension psa-firewall is already running as a process. Presumably it is running with a default or zero configuration?

Thanks again

--Justin Wyllie
 
Last edited:
Back
Top