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

  1. S

    Resolved Plesk Upgrade failed to 502

    What the heck... i found the solution by myself... :-) i was reading in psa_service log: Starting sw-engine-fpm: [23-Sep-2018 15:11:14] ERROR: failed to open error_log (/var/log/sw-cp-server/sw-engine.log): No such file or directory (2) [23-Sep-2018 15:11:14] ERROR: failed to post process the...
  2. S

    Resolved Plesk Upgrade failed to 502

    Hey Guys, i was using my plesk installation since 2013 and did an upgrade in late 2016. last week i tried to do the same but it fails and my plesk interface isnt reachable anymore. here is what happens when i try to do [root@s17790938 ~]# plesk repair installation Reconfiguring the Plesk...
  3. S

    Upgraded and now PSA service will no longer start

    Just a simple beginner question in this context... i never used plesk command line tool before the upgrade failed. so how do i close and save my changes in the tool (plesk conf php.ini) ?
Back
Top