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

  1. B

    Plesk Panel update failed 11.5.30

    I have to files source.list and sources.list.ai_back source.list contains the following entries. # See sources.list(5) for more information, especialy # Remember that you can only use http, ftp or file URIs # CDROMs are managed through the apt-cdrom tool. deb...
  2. B

    Plesk Panel update failed 11.5.30

    Got an error message that the Panel update failed. Any suggestions how to overcome this problem? Partial Log file from the Panel/Action Log 127.0.0.1 admin [2014-02-01 03:08:48] 'New patch available' ('Update version': '30' => '31') 91.66.216.71 admin [2014-02-01 17:20:15] 'CP User...
  3. B

    Postfix own certificate

    Thanks but the mail servers address is the same as the website (so sitename.de) and I use postfix as mta. For me it seems to be somehow strange that I still get warning for the default plesk certificate which I don't use at all. Do you have an explanation for that?
  4. B

    Postfix own certificate

    I've configured postfix to use my own certificate. /etc/postfix/main.cf smtpd_tls_cert_file = /etc/postfix/myveryowncertificate.pem the certifcate file includes the private key, myveryowncertificate, the intermediate certificate, and the root certificate. I use the certificate also for...
See more
Back
Top