• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

PCI Compliance SSL Port 8443

stevenlawlor

New Pleskian
Hi there

We've recently failed on a PCI compliance for a domain which has its own dedicated IP and SSL, but because of port 8443 having a signed certificate, it is failing the PCI Compliance scan.

I've put a new SSL certificate on the server itself and clicked 'Secure the panel' in order to assign the new SSL cert, but whenever I go to port 8443, then I'm still getting the signed certificate error.
 
Back
Top