Changing Template Breaks Site
Changing Template Breaks Site
I am having issues with some features on a site. I wanted to disable the NGNIX proxy but doing so breaks the site.
The same seems to be true no matter what template setting I change. I'm pretty much locked into the current configuration and changing anything template related breaks the site and nothing including rebooting the server fixes it until I put the setting back to what they were.
Any insights?
The same seems to be true no matter what template setting I change. I'm pretty much locked into the current configuration and changing anything template related breaks the site and nothing including rebooting the server fixes it until I put the setting back to what they were.
Any insights?
-
viraladmin
- Posts: 57
- Joined: Thu Apr 27, 2017 7:40 pm
- Os: Ubuntu 15x
- Web: apache + nginx
Re: Changing Template Breaks Site
Is this under the admin account or a user account?
Are you using the bind template for dns or the child template?
What I would recommend is as follows:
Set the bind template to default.
Turn on nginx and set it to the default template and save.
Use the default apache template
Then go bcak and disable nginx and see if that works.
I this does not work... log files are your friend. Nothing should fail to start without logging what the problem is.
Check your /var/log/nginx/error.log for specific issues and perhaps paste us the errors if its not obvious.
Are you using the bind template for dns or the child template?
What I would recommend is as follows:
Set the bind template to default.
Turn on nginx and set it to the default template and save.
Use the default apache template
Then go bcak and disable nginx and see if that works.
I this does not work... log files are your friend. Nothing should fail to start without logging what the problem is.
Check your /var/log/nginx/error.log for specific issues and perhaps paste us the errors if its not obvious.
Re: Changing Template Breaks Site
admin account and bind template
I have installed VestaCP for a few servers and never had this issue. I'll try your suggestion to see if I can get it to work but the immediate issue passed -- I was having issues with a site and suspected it was because of the ngnix proxy but I installed the same site on a local sever with just Apache and the same issue was present so it is actually a bug in the platform.
I have installed VestaCP for a few servers and never had this issue. I'll try your suggestion to see if I can get it to work but the immediate issue passed -- I was having issues with a site and suspected it was because of the ngnix proxy but I installed the same site on a local sever with just Apache and the same issue was present so it is actually a bug in the platform.