Urgent ! The latest update broke ALL the websites!

Post Reply
gn7
Posts: 9
Joined: Wed Jul 13, 2022 4:51 am

[NOTE: This problem is SOLVED! See last comment below. IT was not the recent Vesta Update, but rather a nginx config that caused the issue]
update appears to breakALL the websites on my server....
Even when I try and put a simple static HTML page on the website, no browser can get to it. They all say:
"This site can’t be reached www.(mysite).com refused to connect."
The myVesta error log is also empty. How to fix?
Last edited by gn7 on Wed Feb 22, 2023 11:59 pm, edited 1 time in total.
gn7
Posts: 9
Joined: Wed Jul 13, 2022 4:51 am

Also I tried creating a NEW site, and it also can't be reached by any browser. I also checked my domain registrar,... everything is pointing correctly. And all my sites on other servers work, only the MyVesta sites can't be reached. the update has broken everything
User avatar
myVesta
Site Admin
Posts: 928
Joined: Fri Jun 19, 2020 9:59 am
Has thanked: 8 times
Been thanked: 6 times

run in your SSH:

Code: Select all

sudo /usr/local/vesta/bin/v-list-sys-services
to see what service failed.
I'm pretty sure we didn't touch any service in the last update.
gn7
Posts: 9
Joined: Wed Jul 13, 2022 4:51 am

I restarted my server from the VPS panel before posting here, but that didn't solve the problem.
So I entered your SSH code; it turns out nginx was not running!!
So as root, I tried 3 commands:
# systemctl restart nginx
and then: systemctl start nginx.service
and: service nginx start
each one gave me: "Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.
gn7
Posts: 9
Joined: Wed Jul 13, 2022 4:51 am

Serverfault site says this problem arises when: "Some other process is already running and bound to ports 80/443, thus systemd cannot start nginx. This is almost always because the process was started manually instead of via systemd"
But I had not manually started anything until just now. The services running as per the ssh command:
nginx off 0 0 0
php7.4-fpm running 0 34 995
exim4 running 0.2 15 995
dovecot running 0 0 995
mariadb running 0 378 995
vsftpd running 0 0 995
cron running 0 25 995
ssh running 0 1 995
vesta-nginx running 0 0 995
vesta-php running 0 4 995
iptables running 0 0 0
fail2ban running 0.2 135 995
gn7
Posts: 9
Joined: Wed Jul 13, 2022 4:51 am

The logs are empty: /var/log/nginx/error.log
Command: netstat -plant | grep 80 gives me:
tcp 0 0 [my ip address]:25 80.94.95.205:12050 ESTABLISHED 132461/exim4
tcp 0 0 [my ip address]:25 80.94.95.205:25366 ESTABLISHED 132512/exim4
so I guess exim4 is blocking nginx??
But.. disabling exim4 and dovecot did NOT solve the issue, as nginx would not start
I then used this to kill the processes that are using 80 or 443:
sudo fuser -k 80/tcp
sudo fuser -k 443/tcp
and then: sudo service nginx restart
But still, all fails.
I have not done anything to the server nor even logged in for months, so that is why I think the auto update must have made this change?
The update apparently blocks the ability for nginx to run.
gn7
Posts: 9
Joined: Wed Jul 13, 2022 4:51 am

Problem SOLVED! :)
And it was my fault, NOT the update. I forgot that a month or so ago I added a quick site for some notes, which I never used. And I hadn't run the nginx -t test command. It turns out there was an error in its config., that blocked nginx. So all is well now, thanks much.
Post Reply