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

Blocking access to port 8443 with Plesk Firewall

S

soopadoubled

Guest
I'm currently trying to configure my Plesk 8.6 installation (on CentOS 5.2) to meet PCI DSS requirements.

Having run a site scan, the only problems I have now is with the Apache instance that plesk runs on (port 8443). All of the 'security holes' that the Commodo scan have found state I need to upgrade the version of Apache.

http://img37.imageshack.us/img37/7995/8443p.jpg

I assume this is out of the question, I thought it would be easier to limit access to port 8443 to my IP address, unfortunately every time I try to activate a rule to do this in Plesk Firewall, I get a message saying my SMTP server has gone down and that it must be restarted, actively preventing me from employing this rule.

http://img22.imageshack.us/img22/4253/plesksmtp.png

Is this regular behaviour or am I doing something wrong?

Any ideas or advice would be greatly appreciated,

Thanks,

Ian
 
Back
Top