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

Enabling suphp disables php.ini

U

unsichtbarre

Guest
Hi all,
I have installed suphp, now when I enable it by making the following changes to /etc/httpd/conf.d/suphp.conf PHP seems to run only with default values, not respecting my php.ini in any way:
LoadModule suphp_module modules/mod_suphp.so

# To use suPHP to parse PHP-Files
AddHandler x-httpd-php .php
#AddHandler x-httpd-php .php .php4 .php3 .phtml

# This option tells mod_suphp if a PHP-script requested on this server (or
# VirtualHost) should be run with the PHP-interpreter or returned to the
# browser "as it is".
suPHP_Engine on


# This option tells mod_suphp which path to pass on to the PHP-interpreter
# (by setting the PHPRC environment variable).
# Do *NOT* refer to a file but to the directory the file resists in.
#
# E.g.: If you want to use "/path/to/server/config/php.ini", use "suPHP_Config
# /path/to/server/config".
#
# If you don't use this option, PHP will use its compiled in default path.
suPHP_ConfigPath /etc


# If you compiled suphp with setid-mode "force" or "paranoid", you can
# specify the user- and groupname to run PHP-scripts with.
# Example: suPHP_UserGroup foouser bargroup
# suPHP_UserGroup apache apache~
~
"suphp.conf" 32L, 1253C

Aside from not finding my php.ini, suphp seems to work with this configuration. Does anybody know what I am missing? Any and all hints appreciated-
-John
 
Back
Top