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

Plan Add-Ons not working for existing domains

argonius

Basic Pleskian
I've created a Service Plan Add-On for Typo3. It just extends the default open_basedir path.
If i create a new subscription and selected the Service Plan Add-On "Typo3". It works fine:

# grep typo3 *
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"


but if i use a already created domain and add the service plan add-on "typo3" to it, a new httpd.include
is generated, but without the new open_basedir. maybe this is a bug?

thanks,

patrick
 
problem still occurs

hi,

i already have this problem. now i changed hosting settings from apache modul to fcgi in an add-on and also
in the assigned plan. but nothing changes. php is still running under apache modul.

i need really a fix for this! Parallels?!

greetz
patrick
 
Back
Top