We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Disable nginx?
Disable nginx?
Sorry guys, if this is a repeated topic discussed because I couldn't really find the related topic in the forum.
I've recently encounter the "upstream timed out (110: Connection timed out) while reading upstream...." and planning to switch off Nginx support to determine if it is the cause...
I'm running VestaCP on CentOS 6.5 (with nginx support).
Can anyone pls advise if I can disable Nginx support simply by un-selecting "Nginx Support" for the particular web domain in VestaCP? Would it cause any configuration to break?
Thanks for any advice!
Kind regards,
Marcus
I've recently encounter the "upstream timed out (110: Connection timed out) while reading upstream...." and planning to switch off Nginx support to determine if it is the cause...
I'm running VestaCP on CentOS 6.5 (with nginx support).
Can anyone pls advise if I can disable Nginx support simply by un-selecting "Nginx Support" for the particular web domain in VestaCP? Would it cause any configuration to break?
Thanks for any advice!
Kind regards,
Marcus
Re: Disable nginx?
You can, but this is not good idea. Now you have nginx + apache (httpd) and problem with webserver? Need to dig in logs to understand, what's going on.
Re: Disable nginx?
Thanks Skurudo, for your reply.
Yes, it is currently on nginx + apache. I'm getting intermittent connection timed out error "upstream timed out (110: Connection timed out)" which leads to Internal Server Error..
When I check the Top outputs, the server load, CPU wait I/O seems ok. There is plenty of available memory too.
I'm trying to narrow down what would be the root problem..and I'm thinking to disable nginx support for the web domain to determine if this error is caused by nginx..
Yes, it is currently on nginx + apache. I'm getting intermittent connection timed out error "upstream timed out (110: Connection timed out)" which leads to Internal Server Error..
When I check the Top outputs, the server load, CPU wait I/O seems ok. There is plenty of available memory too.
I'm trying to narrow down what would be the root problem..and I'm thinking to disable nginx support for the web domain to determine if this error is caused by nginx..
Re: Disable nginx?
Marcz, it may me not your vps work not right, neighbors may be get too much resources from server
Re: Disable nginx?
Thanks skurudo.
That was my first suspicion too. I check the server load, memory, etc. All seems fine...
That was my first suspicion too. I check the server load, memory, etc. All seems fine...
Re: Disable nginx?
Marcz, afaik you can check LA / mem only on your server, but not on general server or other vps. No? )
May be in logs is something? Errors before connection timeouts? (apache/nginx)
May be in logs is something? Errors before connection timeouts? (apache/nginx)
-
- Posts: 31
- Joined: Wed Oct 18, 2017 6:34 am
Re: Disable nginx?
Same problem here
Tried to fix "upstream prematurely closed connection while reading response header from upstream" error and landed in this topic...
Did you manage to solve it somehow?
Tried to fix "upstream prematurely closed connection while reading response header from upstream" error and landed in this topic...
Did you manage to solve it somehow?