I don’t have much time to investigate why Hestia doesn’t save additional rules and why it doesn’t use custom.sh script.
So I decided to add all my rules to separate script and added it autostart with delay. And my problem was resolved.
Any shell script could be put in debug mode by adding -x command before the name of that script. Using Hestia scripts, you do not need to enter sh or bash before the name of that script, because Hestia service is loaded and takes care of that.
However, you could force all Hestia scripts to enter in a debug mode to add bash -x in the cli as follows (as an example):
bash -x v-update-firewall
Then you can publish here the last lines of output in shell, where is begins processing of data related to firewall.
I am working on a custom rule for 8083 addresses with multiple IPs. I can put only 1 IP or 1 range only. However, I would like to have something like 126.96.36.199 and 188.8.131.52. So, I have created a custom.sh file but it is not showing 184.108.40.206 and 220.127.116.11. It is likely overridden by the setting in Control Panel. The habit is not alike VestaCP and myVestaCP. Please suggest whether I have done anything wrong.