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

Python27 permission access

ShamirP

New Pleskian
Hi all

I'm fairly new to plesk and am just baffled on a problem which has been occurring in recent weeks.

Plesk come's with Python 2.4 installed, however a client had created a Django sites using python 2.7. So using the "Web Platform Installer" i had installed python 2.7.

As default this installed Python2.7 in the root of the C:

Once Python2.7 was installed and running, to get the website to run I had to make sure usergroup psacln would have access to the python.27 directory. Otherwise i would see a server error.

The permissions seem to reset weekly, which baffled me. The only conclusion i came to was that plesk was set to install updated automatically and when these updated get installed, permissions set to anything not in the plesk installation directory are revoked.


Has anyone else had this problem? if so, how did you over come this.
 
To resolve this problem you need to re-install your Python 2.7 to Plesk directory %plesk_dir%\Additional. This folder is allowed for psacln group and permissions are never changed.
 
Back
Top