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

  1. DigitalExit

    Forwarded to devs Error: Call to a member function process() on null (RemoteSettings.php:95)

    Here's how to change your log levels as required. How to enable/disable Plesk debug mode panel.log can be found at /usr/local/psa/admin/logs/panel.log Source: Plesk for Linux services logs and configuration files
  2. DigitalExit

    Resolved Setting default client_max_body_size

    This actually isn't correct. You need to add "nginxClientMaxBodySize" without a value to the panel.ini to make it work. [webserver] nginxClientMaxBodySize = Without a value you now have the freedom to set ClientMaxBodySize for each domain in the Plesk panel. This is also stated here: Invalid...
  3. DigitalExit

    Resolved "Dump failed; The following domains were not found on the host"

    Is one report enough? I have the same problem since the latest Plesk update (Version 17.5.3 Update #14).
  4. DigitalExit

    Question Plesk Onyx + WAF + Atomicorp + nginx = ???

    I have the same situation, I'm using nginx (non proxy mode) with Plesk Onyx and looking for a way to use the web application firewall. I tried the suggested test at http://wiki.atomicorp.com/wiki/index.php/Atomic_ModSecurity_Rules#Step_10:_Test_your_web_server and I get a 404 error, which means...
See more
Back
Top