Hangover2
Regular Pleskian
- Server operating system version
- Debian 12
- Plesk version and microupdate number
- 18.0.61 #6
Hello,
If the "Hosting performance settings management" is disabled in a service plan, users can still override settings like memory_limit or max_execution_time, e.g., via the .user.ini file in their subscriptions.
I think many Plesk users disable that feature and believe that clients are not able to raise the limits set, as it can make shared hosting quite unstable. On top of that, sold packages based on those values can easily use more resources than actually allowed.
In our case (Dedicated PHP-FPM), a possible solution would be to set in "/var/www/vhosts/system/domain.example/etc/php-fpm.conf" e.g.:
Instead of using:
Is this intended by Plesk, or am I missing something here before I make a bug report?
As a workaround, we are using automated configuration management to monitor those config files and update them if our changes are overridden by Plesk.
If the "Hosting performance settings management" is disabled in a service plan, users can still override settings like memory_limit or max_execution_time, e.g., via the .user.ini file in their subscriptions.
I think many Plesk users disable that feature and believe that clients are not able to raise the limits set, as it can make shared hosting quite unstable. On top of that, sold packages based on those values can easily use more resources than actually allowed.
In our case (Dedicated PHP-FPM), a possible solution would be to set in "/var/www/vhosts/system/domain.example/etc/php-fpm.conf" e.g.:
Code:
php_admin_value[memory_limit] = 512M
Code:
php_value[memory_limit] = 512M
Is this intended by Plesk, or am I missing something here before I make a bug report?
As a workaround, we are using automated configuration management to monitor those config files and update them if our changes are overridden by Plesk.