• 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 Rene Hamburger

  1. R

    Question Upgrade postgres

    I've installed PostgreSQL 13.3 on my server and haven't seen any issues with the Plesk DB integration yet. Table stats, connection info and user details are shown as before.
  2. R

    Question Upgrade postgres

    Thanks for the quick response, Igor! Yes, that's what I would expect, too. I guess my question was, what exactly would be missing if the Plesk-PostgreSQL-integration broke. It seems that it's mostly db stats and db user management from within Plesk. I'll give it a try.
  3. R

    Question Upgrade postgres

    @IgorG, what would happen if I installed a newer version that the ones currently supported by Plesk? As far as I can see, Plesk does not use PostgreSQL for any of it's own data, so is the worst that would happen is that the connection info in the database overview would be wrong?
  4. R

    PHP error.log: failed to notify status to systemd

    I'm also getting this error every 10 seconds in the FPM-PHP log. This is the place in the PHP source code it originates from. This may not be a Plesk-specific issue, but I cannot find anything about it anywhere else on the web. Is anyone able to provide more input on this?
See more
Back
Top