I’m using HestiaCP on a Debian 10 server with Nginx + PHP-FPM.
While the domain’s Web TemplateNGINX is saving fine, the Backend Template PHP-FPM doesn’t save and always loads the “default” template.
This template seems to be overridden on panel updates (or periodically, since my changes made to it keep disappearing). This results in getting some of my websites unreachable that require a particular “open_basedir” path.
The best approach is to make my own templates as I did for the Nginx web templates. However, since the Backend PHP-FPM template is not saving, I don’t know what other options I have.
Is this a known bug or something that has to do with my configuration?
I have a similar problem:
In the /etc/php/7.4/fpm/pool.d folder, edit the domain.conf
I put pm.max_children = 24, but after a while pm.max_children = 8, or again by default.
Did not update the system, it turns out that when you restart pm.max_children = by default!? And the site crashes because of pm.max_children.
And how to be here !?
Tried both old and creating new templates. Anyway, the domain.conf file in the /etc/php/7.4/fpm/pool.d folder is reverted to the original
pm.max_children = 8
pm.max_requests = 4000
Maybe for default templates you need to additionally register the path to the file? More detailed documentation is needed.