In the following lines of code, prepare_backend is not called, hence $backend_proxy is empty and the conf file for older domain still exist at the php-fpm pool folder.
# Delete backend
if [ -n "$BACKEND" ]; then
delete_web_backend
fi
Tell us how to replicate the bug
After executing this command, run v-delete-user which will delete all the files related to the "new" domain, leaving the old config behind. At this point, restart of php-fpm fails.
Describe the bug
In the following lines of code,
prepare_backend
is not called, hence$backend_proxy
is empty and the conf file for older domain still exist at the php-fpm pool folder.Tell us how to replicate the bug
After executing this command, run
v-delete-user
which will delete all the files related to the "new" domain, leaving the old config behind. At this point, restart of php-fpm fails.Which components are affected by this bug?
Control Panel Command Line Interface
Hestia Control Panel Version
1.6.8
Operating system
Ubuntu 20.04
Log capture
No response