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

  1. M

    Issue SPF check fails (Reason=Mechanism) due to combination of local rule and redirect

    Question and potential issue about email delivery and local spf rules. Hi everyone, We are facing a problem with the SPF check in Plesk that is affecting several of our customers. Our Setup: We use the spamexperts anti-spam cloud to filter incoming emails. To ensure these emails pass the SPF...
  2. M

    Question Try our new tool to upgrade your old MariaDB server from Plesk UI

    Hi, upgrades are also offered for mariadb docker cts : You can still start the upgrade which then leads to localhost mariadb being upgraded. In my case 10.11.5 => 10.11.6. I belive this is an error and should not be possible.
  3. M

    Resolved Git Deployment Action Error: /opt/plesk/php/8.0/bin/php: No such file or directory

    Total guess but do you use a chrooted shell for this account ? Maybe try setting in to "/bin/bash" without "(chroot)" in your hosting settings.
  4. M

    Issue Keep nginx from binding to specific IPs

    hi, afaik the only way to do that is by blacklisting the unwanted ips in your panel.ini [ip] blacklist="192.168.1.1,192.168.1.2" You will need to "reread" the plesk ip pool afterwards : sudo plesk bin ipmanage --reread That was the trick for me when somehow my nginx tried to bind to my local...
Back
Top