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

Php.ini for vhosts

VinnyT

Regular Pleskian
I have noticed that each of my vhosts contains an etc/php.ini file which is a replica of my main php.ini. Any changes that I make changes to the vhost php.ini files will be overwritten if I reconfigure the domains (httpdmng).

1) Why is the entire php.ini file copied to each vhost? Isn't there a way to just use the vhost php.ini file as a way to introduce custom settings?
2) How can I stop the custom php.ini file from being overwritten?


Thanks!
 
Hello. :)

You can customise a specific domain's PHP settings in Plesk. Click on the domain, then the PHP Settings Tab then at the bottom it says:

Additional directives

If you cannot find particular PHP parameters, add them to the field below. The directives will be included in the final PHP configuration. Use the same syntax as you use for php.ini. For example, if you want to automatically load the mSQL extension, add the line: extension=msql.so.


That's where you can safely put your php.ini directives.

Warmest Regards,

Brian
 
Back
Top