• 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 Adrian I

  1. A

    Resolved API call failed: HTTP Error 500: Internal Server Error

    I disabled the extension, which didn't work, then removed it, which *did* work. Thanks.
  2. A

    Resolved API call failed: HTTP Error 500: Internal Server Error

    Good call. I'll give that a try, and report back.
  3. A

    Resolved API call failed: HTTP Error 500: Internal Server Error

    As I understand it, dgri-report is a Docker process. But I have completely removed Docker from my server and the issue persists, with hourly errors. I'm convinced that the issue stems from last night's 140+ component updates.
  4. A

    Resolved API call failed: HTTP Error 500: Internal Server Error

    Sadly not, removed Docker but error persists.
  5. A

    Resolved API call failed: HTTP Error 500: Internal Server Error

    Same error from Cron at 22 minutes past the hour here, Plesk 18.0.26 on Centos v7.
  6. A

    Error: Connection to the database server failed: Operation CREATE USER failed for

    Nothing is logged to the mysql error log or the general query log (which I temporarily enabled). Nothing in sw-cp-server/error_log either. Which is unhelpful, I know. Adrian.
  7. A

    Error: Connection to the database server failed: Operation CREATE USER failed for

    I'm experiencing this issue when creating a mysql database and user together, or when adding a user to a database: Error: Connection to the database server failed: Operation CREATE USER failed for 'db-user-name'@'localhost' Probably related, if I try; plesk repair mysql from ssh, I get errors...
See more
Back
Top