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.
Bug report
Bug report
Is there a path change of vstats?
ิbefore :
lastest :
After installing vestcp ( nginx with php-fpm ), nginx is not working.
ิbefore :
nginx worklocation /vstats/ {
alias /home/admin/web/host.domain.in.th/stats/;
include /home/admin/web/host.domain.in.th/stats/auth.conf*;
}
lastest :
nginx not worklocation /vstats/ {
alias /home/sygnus/web/host.domain.in.th/stats/;
include /home/sygnus/conf/web/host.domain.in.th.auth
}
After installing vestcp ( nginx with php-fpm ), nginx is not working.
Re: Bug report
ah! I had the exact same happening to me! Phew ... feel a bit better now :-) as I read on the frontpage how the update is supposed to be flawless. Well ... not quite. I got around the nginx error by writing this script:
which is a modification of /usr/local/vesta/upd/fix_nginx_auth.sh
Only by commenting out that auth line I got nginx to work again. However had other issues thereafter where all my db users created on vestacp level lost access to WP. Matter of re-granting user privileges on MySQL level? I bypassed that issue by changing all my wp-config.php with DB root access. To then find out how any changes or adding new domains in vestacp gave php-fpm errors. And after hours of troubleshooting found out other problems. Long story short? I've reinstalled all my servers from scratch.
Code: Select all
#!/bin/bash
source /etc/profile.d/vesta.sh
source /usr/local/vesta/conf/vesta.conf
sed -i "s|include %home%/%user%/conf/web/%domain%.auth|#include %home%/%user%/conf/web/%domain%.auth|" \
$VESTA/data/templates/web/nginx/*/*tpl >/dev/null 2>&1
if [ "$WEB_SYSTEM" != 'nginx' ]; then
exit
fi
$VESTA/bin/v-rebuild-web-domains admin no >/dev/null 2>&1
$VESTA/bin/v-restart-service nginx
Only by commenting out that auth line I got nginx to work again. However had other issues thereafter where all my db users created on vestacp level lost access to WP. Matter of re-granting user privileges on MySQL level? I bypassed that issue by changing all my wp-config.php with DB root access. To then find out how any changes or adding new domains in vestacp gave php-fpm errors. And after hours of troubleshooting found out other problems. Long story short? I've reinstalled all my servers from scratch.
Re: Bug report
Fixed