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.
Need advice debugging ERR_CONNECTION_TIMED_OUT
Need advice debugging ERR_CONNECTION_TIMED_OUT
I have a VestaCP install which has been working fine for all the domains that are hosting. I just added a new domain for an existing user, and for some odd reason, only that domain is getting an ERR_CONNECTION_TIMED_OUT.
Other domains for the same user work fine. I checked and the IP address is resolving correctly, nginx and apache2 configs look correct yet I'm getting a connection timeout.
Is there a way to tell if nginx is loading the config for the domain in question?
Other domains for the same user work fine. I checked and the IP address is resolving correctly, nginx and apache2 configs look correct yet I'm getting a connection timeout.
Is there a way to tell if nginx is loading the config for the domain in question?
Re: Need advice debugging ERR_CONNECTION_TIMED_OUT
Try load just a TXT file ( no PHP )mericson wrote: ↑Tue Jul 23, 2019 4:27 amI have a VestaCP install which has been working fine for all the domains that are hosting. I just added a new domain for an existing user, and for some odd reason, only that domain is getting an ERR_CONNECTION_TIMED_OUT.
Other domains for the same user work fine. I checked and the IP address is resolving correctly, nginx and apache2 configs look correct yet I'm getting a connection timeout.
Is there a way to tell if nginx is loading the config for the domain in question?
And of course, test if is a DNS problem, try point that domain to your server using your hosts file in your PC and discard dns problem.
Re: Need advice debugging ERR_CONNECTION_TIMED_OUT
Yes, I was trying a plain text file also. The issue was that no connection was being established for any resource.
I discovered the problem, I had my floating IP (behind NAT) configured incorrectly.
I discovered the problem, I had my floating IP (behind NAT) configured incorrectly.