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

  1. C

    Question Lowest cost protection solution?

    Worst part its not as easy to change, if even possible. I gave up on it. With Atomicorp you just change the custom error documents. Since I assume most are behind cloudflare, or something similar, thats my favorite, though everyone´s setup is different.
  2. C

    Question Lowest cost protection solution?

    Honestly, you are just better off getting Atomicorp Advance. I have tried Bitninja, Imunify and Atomicorp. Bitninja has a good chat support, Atomicorp good email support. I didnt need the Imunify support. Bitninja activates and controls a lot of things by default, and changing and editing is...
  3. C

    Resolved ModSecurity don't work

    I fixed the issue by doing 1. Find the current config: bashgrep -r "SecDataDir" /etc/modsecurity/ /etc/apache2/ /etc/httpd/ 2>/dev/null 2. Create a new directory: bashmkdir -p /var/cache/modsecurity chown www-data:www-data /var/cache/modsecurity chmod 770 /var/cache/modsecurity 3. Update...
  4. C

    Resolved ModSecurity don't work

    I tried that workaround but it doesnt work. Looks like the issue is presistent for a year now. This is Plesk bug with ID #PPPM-6202 which will be fixed in future updates.
See more
Back
Top