• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

STILL no suPHP support in Plesk 8.2 -- SWsoft R U listening?

Thanks to Ivalics assistance we're able to resolve this issue.

The issue was due to changes being made to the /conf directory for the domain when installing an Application via the Application Vault (specifically Joomla pkg from http://www.apsstandard.org/). When installing this package it creates a sub-folder in the users conf directory called /siteapp.d which contains conf files for specified packages altering the php handlers for the specific folder and breaking suphp, hashing out this conf file corrects suphp.

As a global solution we've altered the affected packages on the server so that they:
-Don't create the conf file
-Don't change permissions to 777 for folders/files so applications will work under suphp

We did this by editing the APP-META.xml located in the pkg directory: /opt/psa/var/cgitory/<packagename>

As per this Parallels forum thread (http://forum.parallels.com/showthread.php?t=97843), excluding the permissions/handler sections in the <mapping> area allows the pkg's to install correctly for suphp requirements.
 
Back
Top