• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Search results

  1. A

    Resolved IP Whitelist in ModSecurity: Found another rule with the same id

    Thank you for your help. It wasn't a Plesk issue after all. It was my dumb mistake. I misunderstood the modsecurity's whitelist syntax. I thought by adding id:210280 that it would whitelist the IP for that particular rule's ID instead of being just the whitelist rule's ID. Everything works fine...
  2. A

    Resolved IP Whitelist in ModSecurity: Found another rule with the same id

    My server configuration is Plesk Onyx 17.8.11 on Debian 9.5 with Comodo ModSecurity (subscription). When trying to whitelist one IP serverwide in ModSecurity with a rule such as: SecRule REMOTE_ADDR "^192\.168\.1\.1$" phase:1,id:210280,nolog,allow It throws the following error: "Invalid...
Back
Top