• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/

Recent content by Martbean

  1. Martbean

    Resolved Disable access to Plesk via IP address

    Hi, I've tried the changes you suggested but it's still not redirecting. Here's the contents of /etc/sw-cp-server/conf.d/plesk.conf: server_names_hash_bucket_size 64; server { listen xx.xx.xx.xx:8443 ssl; listen xx.xx.xx.xx:8880; listen...
  2. Martbean

    Resolved Disable access to Plesk via IP address

    Awesome, thanks for this! I'm going away for a few days but will give it a go when I get back.
  3. Martbean

    Resolved Disable access to Plesk via IP address

    Hi, I was thinking that too, that I'd still see the warning, but that might be enough. I'm not using the address nor publicising it but since it's a PCI scan, they are simply looking for common open ports on the IP address. The scan fails because there's a Plesk login on a "insecure"...
  4. Martbean

    Resolved Disable access to Plesk via IP address

    Hi, I'm trying to achieve PCI compliance for a server and it's failing because Plesk can be accessed with an invalid/self-signed certificate using the IP address, ie. xxx.xxx.xxx.xxx:8443 I've managed to get Plesk to use the cert from my domain name so https://domain.com:8443 works fine, but I...
Back
Top