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

  1. S

    Resolved Node.JS panel suddenly blank for domains with a subdomain

    Hi @Peter Debik , What if we can't update right now due to the debian version (We are migrating but need this to work right now). My version of Plesk is 18.0.44. How can I downgrade the NodeJs extension to the previous version that was working fine (auto update was on and as you can see is not...
  2. S

    Resolved Node.JS panel suddenly blank for domains with a subdomain

    Hi, Any news on this. This is very impacting for us as we rely on node on several instance of Plesk and multiple servers. And if no fix is found how can I revert to the previous version of the Node.js Toolkit. Thanks
  3. S

    Issue No sodium extension for PHP 7.4.30 FPM

    Hi, I can confirm that the solution in the KB article does not solve the problem for me. The sodium.ini files were already removed from /opt/plesk/php/7.4/etc/php.d/ /opt/plesk/php/8.0/etc/php.d/ /opt/plesk/php/8.1/etc/php.d/ so no need to move them to the /root directory (which is very strange...
  4. S

    Issue No sodium extension for PHP 7.4.30 FPM

    Hi @IgorG I have the same issue with PHP 7.4, PHP 8.0 and PHP 8.1 (I know that php is now compiled with the --with-sodium flag). De-commenting the ;extension=sodium => extension=sodium raises an error in PHP saying that it can't find the extension). The sodium.ini has been delete from php module...
See more
Back
Top