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.
VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
-
- Posts: 11
- Joined: Sat Mar 09, 2019 5:37 pm
- Os: Ubuntu 17x
- Web: apache + nginx
VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
Hello,
Just wondering when VestaCP will be compatible with Ubuntu 18.10.1. Right now i am getting an Bad Gateway nginx error when trying to login to my admin panel after i updated from 16.04.
I updated because Wordpress now supports PHP 7.3 and i figured that might as well do the whole thing. The websites are running fine it's just the admin panel that is not running.
Maybe i configured something wrong but my linux skills are limited and google was no help.
Thanks in advance.
Just wondering when VestaCP will be compatible with Ubuntu 18.10.1. Right now i am getting an Bad Gateway nginx error when trying to login to my admin panel after i updated from 16.04.
I updated because Wordpress now supports PHP 7.3 and i figured that might as well do the whole thing. The websites are running fine it's just the admin panel that is not running.
Maybe i configured something wrong but my linux skills are limited and google was no help.
Thanks in advance.
Re: VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
Vesta admin area actually installs its own version of PHP, which it keeps in /usr/local/vesta/php/bin
You might find some information in the server logs at /usr/local/vesta/log (obviously you can't see the logs through the admin interface)
Maybe running these commands might dislodge something
sudo v-update-sys-vesta 'vesta'
sudo v-update-sys-vesta 'vesta-nginx'
sudo v-update-sys-vesta 'vesta-php'
sudo v-update-sys-vesta 'vesta-ioncube'
sudo v-update-sys-vesta 'vesta-softaculous'
You might find some information in the server logs at /usr/local/vesta/log (obviously you can't see the logs through the admin interface)
Maybe running these commands might dislodge something
sudo v-update-sys-vesta 'vesta'
sudo v-update-sys-vesta 'vesta-nginx'
sudo v-update-sys-vesta 'vesta-php'
sudo v-update-sys-vesta 'vesta-ioncube'
sudo v-update-sys-vesta 'vesta-softaculous'
-
- Posts: 11
- Joined: Sat Mar 09, 2019 5:37 pm
- Os: Ubuntu 17x
- Web: apache + nginx
Re: VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
Hey thanks for the reply.
Unfortunately these commands do not work.
v-update-sys-vesta: command not found.
Am i doing it wrong? I've Ran v-update-sys-vesta-all and then ran apt-cache show vesta this is the result
Package: vesta
Source: vesta
Version: 0.9.8-23
Maintainer: Serghey Rodin <[email protected]>
Homepage: http://vestacp.com
Architecture: amd64
Depends: bash, awk, sed
Priority: optional
Section: admin
Filename: pool/vesta/v/vesta/vesta_0.9.8-23_amd64.deb
Size: 1977040
this is the result of my nginx-error.log
2019/03/20 22:56:24 [crit] 1541#0: *14 connect() to unix:/var/run/vesta-php.sock failed (2: No such file or directory) while connecting to upstream, client: ***.***.***.***, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/vesta-php.sock:", host: "domain.com:8083"
Unfortunately these commands do not work.
v-update-sys-vesta: command not found.
Am i doing it wrong? I've Ran v-update-sys-vesta-all and then ran apt-cache show vesta this is the result
Package: vesta
Source: vesta
Version: 0.9.8-23
Maintainer: Serghey Rodin <[email protected]>
Homepage: http://vestacp.com
Architecture: amd64
Depends: bash, awk, sed
Priority: optional
Section: admin
Filename: pool/vesta/v/vesta/vesta_0.9.8-23_amd64.deb
Size: 1977040
this is the result of my nginx-error.log
2019/03/20 22:56:24 [crit] 1541#0: *14 connect() to unix:/var/run/vesta-php.sock failed (2: No such file or directory) while connecting to upstream, client: ***.***.***.***, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/vesta-php.sock:", host: "domain.com:8083"
Re: VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
Hmm, is the vesta service actually running?
What happens when you do
systemctl status vesta.service
And if its stopped, try
systemctl restart vesta.service
(you might need to sudo if you're admin user)
Or, you could just reboot the server if you prefer.
What happens when you do
systemctl status vesta.service
And if its stopped, try
systemctl restart vesta.service
(you might need to sudo if you're admin user)
Or, you could just reboot the server if you prefer.
-
- Posts: 11
- Joined: Sat Mar 09, 2019 5:37 pm
- Os: Ubuntu 17x
- Web: apache + nginx
Re: VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
Hey,
This is the result of what i get trying to start Vesta.
Job for vesta.service failed because the control process exited with error code.
See "systemctl status vesta.service" and "journalctl -xe" for details.
So i ran the command system status vesta.service and this is the result.
So i did further digging and i tried this command (apt policy *curl* | grep -v "(none)" | grep -A1 -B1 Installed )to see what versions of curl i had. And this was the result. Maybe it can be of some help to you
libcurl4:
Installed: 7.61.0-1ubuntu2.3
Candidate: 7.61.0-1ubuntu2.3
--
php7.3-curl:
Installed: 7.3.3-1+ubuntu18.10.1+deb.sury.org+1
Candidate: 7.3.3-1+ubuntu18.10.1+deb.sury.org+1
--
python3-pycurl:
Installed: 7.43.0.1-0.2build1
Candidate: 7.43.0.1-0.2build1
--
php-curl:
Installed: 2:7.3+69+ubuntu18.10.1+deb.sury.org+2+php7.3
Candidate: 2:7.3+69+ubuntu18.10.1+deb.sury.org+2+php7.3
--
curl:
Installed: 7.61.0-1ubuntu2.3
Candidate: 7.61.0-1ubuntu2.3
--
libcurl3-gnutls:
Installed: 7.61.0-1ubuntu2.3
Candidate: 7.61.0-1ubuntu2.3
Thanks
This is the result of what i get trying to start Vesta.
Job for vesta.service failed because the control process exited with error code.
See "systemctl status vesta.service" and "journalctl -xe" for details.
So i ran the command system status vesta.service and this is the result.
Code: Select all
vesta.service - LSB: starts the vesta control panel
Loaded: loaded (/etc/init.d/vesta; generated)
Active: failed (Result: exit-code) since Thu 2019-03-21 10:57:30 EDT; 46s ago
Docs: man:systemd-sysv-generator(8)
Process: 15767 ExecStart=/etc/init.d/vesta start (code=exited, status=1/FAILUR
Tasks: 2 (limit: 4915)
Memory: 6.2M
CGroup: /system.slice/vesta.service
├─1539 nginx: master process /usr/local/vesta/nginx/sbin/vesta-nginx
└─1541 nginx: worker process
Code: Select all
Mar 21 10:57:30 systemd[1]: vesta.service: Found left-over process 1541 (vesta-nginx) in control group while starting unit. Ignoring.
Mar 21 10:57:30 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 21 10:57:30 systemd[1]: Starting LSB: starts the vesta control panel...
Mar 21 10:57:30 vesta[15767]: * Starting vesta-nginx vesta-nginx
Mar 21 10:57:30 vesta[15767]: ...done.
Mar 21 10:57:30 vesta[15767]: * Starting vesta-php vesta-php
Mar 21 10:57:30 vesta[15767]: /usr/local/vesta/php/sbin/vesta-php: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /usr/local/vesta/php/sbin/vesta-php)
Mar 21 10:57:30 systemd[1]: vesta.service: Control process exited, code=exited status=1
Mar 21 10:57:30 systemd[1]: vesta.service: Failed with result 'exit-code'.
Mar 21 10:57:30 systemd[1]: Failed to start LSB: starts the vesta control panel.
libcurl4:
Installed: 7.61.0-1ubuntu2.3
Candidate: 7.61.0-1ubuntu2.3
--
php7.3-curl:
Installed: 7.3.3-1+ubuntu18.10.1+deb.sury.org+1
Candidate: 7.3.3-1+ubuntu18.10.1+deb.sury.org+1
--
python3-pycurl:
Installed: 7.43.0.1-0.2build1
Candidate: 7.43.0.1-0.2build1
--
php-curl:
Installed: 2:7.3+69+ubuntu18.10.1+deb.sury.org+2+php7.3
Candidate: 2:7.3+69+ubuntu18.10.1+deb.sury.org+2+php7.3
--
curl:
Installed: 7.61.0-1ubuntu2.3
Candidate: 7.61.0-1ubuntu2.3
--
libcurl3-gnutls:
Installed: 7.61.0-1ubuntu2.3
Candidate: 7.61.0-1ubuntu2.3
Thanks
Re: VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
My suspicions are with the LIBCURL 3 failure. Lets try to install it.
sudo apt install libcurl3
Now try to start vesta again with
sudo systemctl restart vesta.service
For the record, I've got an 18.04 server here which doesn't have libcurl3 installed, and vesta is running fine. But if that's what it says it wants, lets feed it. PS. Also try a search on the forum for libcurl3. There are a few people with this problem it appears.
Update. Here's what I have related to curl on a working 18.04 install
sudo apt install libcurl3
Now try to start vesta again with
sudo systemctl restart vesta.service
For the record, I've got an 18.04 server here which doesn't have libcurl3 installed, and vesta is running fine. But if that's what it says it wants, lets feed it. PS. Also try a search on the forum for libcurl3. There are a few people with this problem it appears.
Update. Here's what I have related to curl on a working 18.04 install
Code: Select all
apt policy *curl* | grep -v "(none)" | grep -A1 -B1 Installed
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
libcurl4:
Installed: 7.58.0-2ubuntu3.6
Candidate: 7.58.0-2ubuntu3.6
--
php7.2-curl:
Installed: 7.2.15-0ubuntu0.18.04.1
Candidate: 7.2.15-0ubuntu0.18.04.1
--
php-curl:
Installed: 1:7.2+60ubuntu1
Candidate: 1:7.2+60ubuntu1
--
curl:
Installed: 7.58.0-2ubuntu3.6
Candidate: 7.58.0-2ubuntu3.6
--
libcurl3-gnutls:
Installed: 7.58.0-2ubuntu3.6
Candidate: 7.58.0-2ubuntu3.6
-
- Posts: 11
- Joined: Sat Mar 09, 2019 5:37 pm
- Os: Ubuntu 17x
- Web: apache + nginx
Re: VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
Hey, This is the response from the server.
Package libcurl3 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
libcurl4
E: Package 'libcurl3' has no installation candidate
It's as if Vesta is not compatible with libcurl4 maybe we can tell vesta it can be by changing the code in a file or something?
Package libcurl3 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
libcurl4
E: Package 'libcurl3' has no installation candidate
It's as if Vesta is not compatible with libcurl4 maybe we can tell vesta it can be by changing the code in a file or something?
Re: VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
Total guess here but how about installing libcurl3-gnutls which is on my working 18.04 server. And check out some of the other discussions, by searching for libcurl3 in the searchbox at the top of the page ....
-
- Posts: 11
- Joined: Sat Mar 09, 2019 5:37 pm
- Os: Ubuntu 17x
- Web: apache + nginx
Re: VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
Hey, Just wanted to thank you for the help.
This is what i get :
This is what i get :
Code: Select all
libcurl3-gnutls is already the newest version (7.61.0-1ubuntu2.3).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
-
- Posts: 11
- Joined: Sat Mar 09, 2019 5:37 pm
- Os: Ubuntu 17x
- Web: apache + nginx
Re: VestaCP 18.10.1 Compatibility ETA & Bad gateway nginx after updating.
I think the problem is that Libcurl3 and libcurl4 cannot co-exist on the same server. :( Hopefully Vesta updates their cpanel soon to support libcurl4.