it’s not
then we are not able to modify domain confs, but only template? i thougt confs with cutom tpl not replaced
Yes, only template because when the certificate is renewed, it executes this v-rebuild-web-domains ‘www-root’ ‘no’ and that rebuild, is the one rewriting the conf of your web domain using the assigned template. So, if you need to add the include, etc, you must do it in the custom template (custom.tpl and custom.stpl)
I forgot to mention that you can add an nginx.ssl.conf_whatever file with the configuration you need, and it won’t be overwritten. However, keep in mind when this config file is loaded, since some directives may take precedence depending on where they appear in the configuration file.
there is inc with analytics with php sock directives and it must bu on top of first location. of course it could be in nginx.hsts.conf, but this file is not for this purpose as i understand
Then add the conf to the template.
Correct, that file will be overwritten too.
one more, where should i make changes for /etc/php/7.4/fpm/pool.d/domain.com.conf
because it’s overwritten too
Create a new backend template based on PHP 7.4:
cd /usr/local/hestia/data/templates/web/php-fpm/
cp PHP-7_4.tpl custom-PHP-7_4.tpl
Make your changes to custom-PHP-7_4.tpl, then, edit your web domain and assign the new template (custom-PHP-7_4) as backend template, save and you are done.