shouldn't all the php options be set manually to the OS's default php? i've just installed a new standalone ispconfig server, ubuntu20.04, ispconfig 3.2.7p1. automated install. install command used --use-php=7.4,8.0 double checking all the settings, php and php-cgi are manually set to 7.4, php-cgi-bin is auto (8.0), i also had another recent test install, where php-fpm.sock was also auto (/run/php/php8.0-fpm.sock) Code: root@test:/etc/alternatives# ls -l php* lrwxrwxrwx 1 root root 15 Dec 14 15:53 php -> /usr/bin/php7.4 lrwxrwxrwx 1 root root 19 Dec 14 15:53 php-cgi -> /usr/bin/php-cgi7.4 lrwxrwxrwx 1 root root 23 Dec 14 15:53 php-cgi-bin -> /usr/lib/cgi-bin/php8.0 lrwxrwxrwx 1 root root 35 Dec 14 15:53 php-cgi.1.gz -> /usr/share/man/man1/php-cgi7.4.1.gz lrwxrwxrwx 1 root root 24 Dec 15 15:02 php-fpm.sock -> /run/php/php7.4-fpm.sock lrwxrwxrwx 1 root root 31 Dec 14 15:53 php.1.gz -> /usr/share/man/man1/php7.4.1.gz Code: root@test:/etc/alternatives# update-alternatives --config php There are 3 choices for the alternative php (providing /usr/bin/php). Selection Path Priority Status ------------------------------------------------------------ 0 /usr/bin/php.default 100 auto mode 1 /usr/bin/php.default 100 manual mode * 2 /usr/bin/php7.4 74 manual mode 3 /usr/bin/php8.0 80 manual mode Press <enter> to keep the current choice[*], or type selection number: root@test:/etc/alternatives# update-alternatives --config php-cgi There are 2 choices for the alternative php-cgi (providing /usr/bin/php-cgi). Selection Path Priority Status ------------------------------------------------------------ 0 /usr/bin/php-cgi8.0 80 auto mode * 1 /usr/bin/php-cgi7.4 74 manual mode 2 /usr/bin/php-cgi8.0 80 manual mode Press <enter> to keep the current choice[*], or type selection number: root@test:/etc/alternatives# update-alternatives --config php-cgi-bin There are 2 choices for the alternative php-cgi-bin (providing /usr/lib/cgi-bin/php). Selection Path Priority Status ------------------------------------------------------------ * 0 /usr/lib/cgi-bin/php8.0 80 auto mode 1 /usr/lib/cgi-bin/php7.4 74 manual mode 2 /usr/lib/cgi-bin/php8.0 80 manual mode Press <enter> to keep the current choice[*], or type selection number: root@test:/etc/alternatives# update-alternatives --config php-fpm.sock There are 2 choices for the alternative php-fpm.sock (providing /run/php/php-fpm.sock). Selection Path Priority Status ------------------------------------------------------------ 0 /run/php/php8.0-fpm.sock 80 auto mode * 1 /run/php/php7.4-fpm.sock 74 manual mode 2 /run/php/php8.0-fpm.sock 80 manual mode Press <enter> to keep the current choice[*], or type selection number: also, on a php related, but separate issue.. in jk_init.ini Code: [php] comment = default php version and libraries paths = /usr/bin/php includesections = php_common, php7_3 shouldn't this last section be php7_4, at least on ubuntu 20.04?, i realize the debian and ubuntu installs use the same script, debian may still need to be 7_3. also shouldn't php8.1 be added into this jailkit config and as a php install option for the automated installer?
Yes, it should either set the correct default or allow specifying a version. This is more or less https://git.ispconfig.org/ispconfig/ispconfig-autoinstaller/-/issues/52 php-cgi path is noted https://git.ispconfig.org/ispconfig/ispconfig-autoinstaller/-/issues/56 .. I added a further note on php-fpm socket, though I don't know if the installer tries to set that or not. (In a separate issue, I've seen where the socket path could not be set because the socket didn't exist at the time that update-alternatives was run - that's not an ISPConfig issue, but the autoinstaller could work around it by creating the symlink directly, rather than using update-alternatives.) Yes, definitely need some improvement here; there is currently no code in the installer which configures jk_init.ini differently for different OS releases. This is related to (would probably be fixed by) https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6211 and possibly some other issues. Yes; I don't see an issue for that one yet. https://git.ispconfig.org/ispconfig/ispconfig-autoinstaller/-/issues/61
Sorry, been very busy and forgot to pick this up. It's on the top of my list for tomorrow - so hopefully implemented next week.