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

  1. G

    Missing release notes of MU #7

    There are no release notes of MU #7 at http://download1.parallels.com/Plesk/PP10/parallels-plesk-panel-10-linux-updates-release-notes.html
  2. G

    plesk 10.4.4 Key Update Error

    Since 10.4.4 I get a key update error every day. If updating the key manually in panel, it means the key is up to date.
  3. G

    Users can't login to Plesk 10.3.1

    Same Problem I posted here: http://forum.parallels.com/showthread.php?t=116003
  4. G

    client login fails

    Hi, since yesterday, logins of all clients fails with tho lower (german) error-message (inside the login-box): Try to translate: You entered user informations of a panel user-account, with is linked with a merchant account. For security-reasons, you cannot login to the system as this...
  5. G

    Customer and Business manager isn't working

    same here! worked well with 10.1.1
  6. G

    Login fails after update to 10.2.0

    working again with: /usr/local/psa/bin/sso --disable
  7. G

    Upgrade from 10.0.1 to 10.2.0 crashed the Plesk Panel

    Try: /usr/local/psa/bin/sso --disable
  8. G

    Login fails after update to 10.2.0

    Login fails after update to 10.2.0. It's only possible to login via vituozzo!
  9. G

    Error with Upgrade

    Works for me now. In my case I had to fix some issues in innodb tables because of an mysql-update to 5.1.xx the last days. After that I did the bootstrapper repair and finally rebooted the server. voila. Thanks
  10. G

    Error with Upgrade

    I did the bootstrapper repair just now, but no change. The login screen with user root and the message above afterwards appears again.
  11. G

    Error with Upgrade

    I'm already on 10.1.1. But like truendorf I cannot do an update anymore. There comes up the "Can't connect to backend: No such file or directory" message and no overview about installed components or options to select or install anything.
  12. G

    Error with Upgrade

    Same problem here after updating the php5-ioncube-loader patch described here: Link How to fix this? Regards, Robert
See more
Back
Top