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

Recent content by loman

  1. L

    Resolved ModSecurity: Access denied with code 403 (phase 2). Match of "contains /wp-json/yoast/"

    Thanks for the help! This could be marked as resolved.
  2. L

    Resolved ModSecurity: Access denied with code 403 (phase 2). Match of "contains /wp-json/yoast/"

    Thanks for the suggestions Maarten. Well the odd thing is that I didn't install wordpress on my website (just mediawiki), this why I couldn't understand the error at the first time. Why yoast is causing the error if I am not using wordpress? Is there something I am missing?
  3. L

    Resolved ModSecurity: Access denied with code 403 (phase 2). Match of "contains /wp-json/yoast/"

    Thanks Maarten! Yes, it's my IP address that is triggering the rule. If I disable the rule, am I going to be more vulnerable to SQL injection attempt attacks?
  4. L

    Resolved ModSecurity: Access denied with code 403 (phase 2). Match of "contains /wp-json/yoast/"

    I forgot to add I have the Plesk Web Application Firewall active (on) with Comodo (free) running on Apache (ModSecurity 2.9).
  5. L

    Resolved ModSecurity: Access denied with code 403 (phase 2). Match of "contains /wp-json/yoast/"

    Hello, I have a mediawiki with the PageForms extension. When I try to create a new page using a form, everything crashes. In the logs I get this error: [client 2.47.215.233] ModSecurity: Access denied with code 403 (phase 2). Match of "contains /wp-json/yoast/" against "REQUEST_URI" required...
See more
Back
Top