Not off the the top of my head. If memory serves, each Hestia template consists of a .tpland an .spl file. You might run a find command to see what turns up.
Found it!
It is /usr/local/hestia/data/templates/web/nginx/proxy_ip.tpl.
Thanks a lot for your support, patience, and time! 
In my particular case, since the server is solely used for hosting that SaaS application, I managed to get it working by replacing include /etc/nginx/conf.d/*.conf; from /etc/nginx/nginx.conf with specific includes for each .conf file from /etc/nginx/conf.d but the one named with the server IP.
It seems that this way, the domain that hosts the SaaS application became the default and started handling all requests that does not match other hosted domains in the same server.
The original question remains tho: why it was working well before the upgrade? 
Anyways, thank you a lot.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.