Vesta Control Panel - Forum

Hello,

HUGE problem !! After update, i did a restart and nginx stopped working.

v-list-sys-vesta-updates
PKG VER REL ARCH UPDT DATE
--- --- --- ---- ---- ----
vesta 1.0.0 5 x86_64 yes 2021-11-30
vesta-php 1.0.0 1 x86_64 yes 2021-11-30
vesta-nginx 1.0.0 1 x86_64 yes 2021-11-30
vesta-ioncube 1.0.0 1 x86_64 yes 2021-11-03
vesta-softaculous 1.0.0 1 x86_64 yes 2021-11-03

I tried: sudo service nginx restart
Active: failed (Result: exit-code) since Wed 2021-12-01 09:48:23 CET; 33s ago
Docs: http://nginx.org/en/docs/
Process: 4385 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)

Dec 01 09:48:23 CentOS-79-64-minimal nginx[4385]: nginx: [emerg] open() "/home/d../conf/web/de**.ro.auth" failed (2: No such file or directory) in /home/d*/conf/web/de**.ro.nginx.conf:59
Dec 01 09:48:23 CentOS-79-64-minimal systemd[1]: nginx.service: control process exited, code=exited status=1
Dec 01 09:48:23 CentOS-79-64-minimal systemd[1]: Failed to start nginx - high performance web server.
Dec 01 09:48:23 CentOS-79-64-minimal systemd[1]: Unit nginx.service entered failed state.
Dec 01 09:48:23 CentOS-79-64-minimal systemd[1]: nginx.service failed.

It has some issues with SSL

If I rebuild all webdomains same result. What just happened? Please help. My websites are offline for 2 days.

You have two ways to choose (1) downgrade the vesta packages or (2) manually fix the /home/d*/conf/web/de**.ro.nginx.conf files.

On my servers I chose option 1 while waiting for the new version to be stable.

For that you need to downgrade all Vesta packages to version 0:0.9.8-26.

In my CentOS servers I use this commands:

# yum downgrade vesta (I had to repeat it 3 times to get the correct version)
# yum downgrade vesta-php
# yum downgrade vesta-nginx
# yum downgrade vesta-softaculous
# yum downgrade vesta-ioncube (I needed to manually delete this directory '/usr/local/vesta/ioncube/ioncube.sh/' before running this command)

After that I disabled the Vesta auto-update in the admin panel.

And include 'exclude=vesta vesta-php vesta-nginx vesta-ioncube vesta-softaculous' at the end of the file /etc/yum.conf.

And that's it, everything started working again.

In option 2 the first step is to comment out line 59 of your /home/d*/conf/web/de**.ro.nginx.conf files and try to restart nginx.

Or you can try creating the /home/d../conf/web/de**.ro.auth files, as the error says the file no longer exists. To create an empty file, you can use the command "touch /home/d../conf/web/de**.ro.auth", for example.

More information can be found in these topics:
viewtopic.php?f=11&t=20691
viewtopic.php?f=10&t=20722

Hello, sandro ! Thanks for reply.

I tried something as you described in the second option.
I have commented all the

ssl on;
and
include /home/v*/conf/web/v*.auth;

After that I have managed to start nginx but on the main domain I have the following issue.
When I try to use https i get the ERR_SSL_PROTOCOL_ERROR on chrome.
If i use only HTTP is working.
How should i fix this??
Thank you

I believe the problem is with the /home/*/conf/web/*.nginx.ssl.conf files.

Some people here on the forum reported that they had to delete the "default_server" parameter from the "listen" variable.

On my server the variable "listen" looks like this:

listen IP:443 ssl;

If you have few sites, try changing it manually.

I'm sure there is a Vesta script to automate this, but I don't know. (LOL)

Thank you very much, sandro.
You are right.

The issue was at the "listen" variable.
I had only listen IP:443;
I added ssl after your model ( listen IP:443 ssl; ) and now works https. Thnak you

It seems that the update has an error code or error message on your Computer or Laptop
I recommend that you uninstall the current update, then disable the automatic updates for the time being and wait for the next updates.
Follow the instructions in the link to turn off automatic updates.

I had this problem after installing and renewing SSL.

I managed to solve it by removing the code in the template itself.

Now I expect NGINX to restart normally after an SSL install and renewal.

Here is the link to my solution, hope it helps: viewtopic.php?f=11&t=20899#p85916