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

selective blocking of 4643 and 8443 on hwnode or sve

C

cah4i

Guest
I'm having PCI compliancy issues with Plesk and the Virtuozzo Control Panel. On my hosted node, I have 12 ips. Is there any reason that on either the HW node or on the Service container access to ports 4643/8443 can be blocked for the selected IPs I'm trying get compliancy for? I would then access Plesk and Virtuozzo via one of my unblocked IPs. I'm thinking something like

iptables -t filter -I FORWARD 1 -d 1.2.3.4 -p tcp -m multiport --dport 4643,8443 -j DROP on the SVE or HWnode is all that is needed.

My provider who would have to implement these rules is claiming that this will not work but I don't see why not. Is this baloney or not?

Thanks!
 
Back
Top