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

PCI Compliance - Panel Self-signed certificate

ShotgunFront

New Pleskian
Hi,

We are running a server with Plesk on and trying to pass a PCI scan.

This scan has an issue with Plesk's self signed SSL certificate.

Whilst Plesk should not enter into the remit of the PCI scan because it is accessible from the domain we are getting scanned at port 8443 it is showing up.

I see two options - firstly, we could actually use a valid SSL for Plesk but I dont see how, because we have multiple domains on this server, so can't specify a single domain to purchase the SSL for..

..The other thing is that this domain doesnt need access to plesk via port 8443. We access Plesk by using our servers IP with the port on the end - is there a way we could stop the domain being able to access this port, which would stop the PCI scanner accessing it?


Thanks,
Tim
 
Back
Top