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

  1. L

    Issue All Domains Apache2/Error 500

    I've done this - which solved the issue. I'm a typical non-tech person and applied the easiest solution, which I think this is. I hope Plesk will update the KB once they're done with the fix, and to guide what actions to take based on the various "work-arounds" that have been applied.
  2. L

    Issue All Domains Apache2/Error 500

    It worked for me too! Although it appears to be a different solution from: Website suddenly started to show 500 error: AH10292: Invalid proxy UDS filename. Hope this wouldn't give any long term issues!
  3. L

    Issue All Domains Apache2/Error 500

    What can we do to prevent such issues from happening again?
See more
Back
Top