I have some experience installing myVestacp into Debian 13 (I know it's still not fully supported) at IPv6-only VPS (i know iPv6 is not supported yet).
Installation is by default.
First problem: install crashes at
Code: Select all
grep: /usr/local/vesta/data/ips/*: No such file or directory
grep: /usr/local/vesta/data/ips/*: No such file or directory
Error: no IP is available
Quick fix: create a file named 127.0.0.1 with default contents (subnet 255.255.255.0 etc).
Full fix: v-update-sys-ip should process the situation when no IPv4 address detected, and IPv4 file names should not cause parse errors and cut to the first octet before ":". Particularly v-update-sys-ip line 33
ips=$(/sbin/ip addr |grep 'inet ' |grep global |awk '{print $2}' |cut -f1 -d/)
returns empty line, and the following count returns 1 (e.g. ip_num) instead of 0. Here muat be either check for empty string and correct 0 ips, or full IPv6 support.
In case the IP is empty, virtuial host configs must not be changed (i.e. currupted)! IMHO there should be additional condition check.
Second problem: panel does not open at the specified port. I don't remember if I fixed nginx.conf of vesta manually or not, but the issue is NOT with then nginx, but with internal PHP-FPM. This PHP 8.4 (ok, I hate all 8.x bulls**t) does NOT return anything to FPM and it's probably an issue not related to IPv6, but to Debian 13 or PHP 8.4 support.
Temporary debug fix: I switched fastcgi_pass path to the "normal" FPM and it worked (either with test phpinfo.php file in /usr/local/vesta/web, or show me index.php - the login page of MyVesta). Of course login failed due to exec(), basedir etc restrictions for security reasons.
Technically I have fully functional web server with LAMP with semi-manually editing of virtual host configs. But without the beautiful panel and GUI.
Any ideas how to fix vesta fpm?
To be continued...
