• 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 Aleksandr Mezin

  1. A

    Issue Emails that are sent locally inside the server are rejected – PPPM-7190 not fixed with 18.0.79

    Yes, that's the correct checkbox. Only the sender domain matters though (the one you called svr.example.com) No, it's being re-read for every message, you don't even have to reload postfix. It looks like you need to open a support ticket.
  2. A

    Issue recurring issue notice automatic updating system packages

    Hi @Harun The bootloader isn't managed by Plesk - the only time they interact is when Plesk runs package updates. But even in this case, Plesk just asks the package manager of your OS (Debian/Ubuntu) to perform the update. It looks like your disk configuration has changed (probably worth...
  3. A

    Issue Emails that are sent locally inside the server are rejected – PPPM-7190 not fixed with 18.0.79

    Hi @King555 PPPM-7190 was a combination of multiple issues, which were fixed across multiple releases. Recently, we reviewed and re-tested it, and found that DMARC works correctly for local e-mails, except a few known issues: 1. QMail 2. Bounces/delivery notifications between local mailboxes...
  4. A

    Issue Selinux-related errors in /var/log/messages

    Hi @Kaspar For the log from the first message - "sshd access denied to mysql.sock", most likely, the source of the error is Plesk's PAM module (sshd loads it during authentication process/session startup). PPPM-7228 correctly identified by @Sebahat.hadzhi . The error appears in audit log...
Back
Top