Facebook
Twitter- Server operating system version
- almalinux
- Plesk version and microupdate number
- last
What is the correct procedure to edit the global custom directive files when running Plesk and Almalinux? Any change we make in the conf files is overwritten by Plesk
Any direct changes we make to the configuration files are overwritten by Plesk when it rebuilds the configs. We tried placing our modified directives (e.g. adding reuseport to listen) under:
/usr/local/psa/admin/conf/templates/custom/
This works temporarily, but every time Plesk itself is updated or upgraded, the update fails unless we delete the custom templates first. As a result, our changes are lost after every update.
Is there an official way to add or persist such global nginx directives so they survive config regeneration and Plesk upgrades without breaking the updater?
Any direct changes we make to the configuration files are overwritten by Plesk when it rebuilds the configs. We tried placing our modified directives (e.g. adding reuseport to listen) under:
/usr/local/psa/admin/conf/templates/custom/
This works temporarily, but every time Plesk itself is updated or upgraded, the update fails unless we delete the custom templates first. As a result, our changes are lost after every update.
Is there an official way to add or persist such global nginx directives so they survive config regeneration and Plesk upgrades without breaking the updater?
