Issue how to edit global custom directives?

[sergx]

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?

 

[LRLD]

Hi,
instead of deleting the custom templates, leave them in place, if they are no longer valid, they will be moved to to a different folder like...

/usr/local/psa/admin/conf/templates/<random>_broken

So just check for that after an update, if present, then recreate your templates.
In my opinion, Plesk should only warn about custom templates when the default ones have changed,
Anyway, I hope that helps.
Regards

LD

 

[scsa20]

Your best bet will be to read over this document: Changing Virtual Hosts Settings Using Configuration Templates

This will tell you how to properly make global server configuration changes which are PHP files to edit (it will make the required files needed for the hosts).

 

[sergx]

Yes, this is how we do it. But if the folder custom exists, Plesk refuses to update unless we delete it and recreate the customs templates.
We need to recréate these custom templetes each time the original templates changes

Is there a solution that doesn't require constant maintenance?

 

[scsa20]

You shouldn't need to delete the custom templates unless the templates are not set properly or if there's major changes and if anything like what @LRLD said it should just renamed the custom folder (or you can rename it yourself, there is no need to delete it), then just need to rename it back and update the templates accordingly if need to.