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

  1. W

    Resolved Apache reload/graceful restart causes Apache segfault

    And now it hits me: I haven't had any log entries in mod_security until yesterday. That's why I didn't have any problems before with the same config. I suspect a new site is triggering mod_security.
  2. W

    Resolved Apache reload/graceful restart causes Apache segfault

    My server is also quite new (23 feb). What license are you running on? Trial or full license? I changed to a full license two weeks ago, because my trial would have expired yesterday (the same day the problems started...) First I thought it was related, because I didn't change anything Apache...
  3. W

    Resolved Apache reload/graceful restart causes Apache segfault

    That's 'funny', I have the exact same problem since yesterday. This morning, it happend for the second time. Same config (Debian 8.3, Plesk 12.5.30 Update #24). I've made the modification and will report back. Did you just install this server, or was it already running a while? Regarding...
Back
Top