Additional PHP Version setting does not work Debian 9, PHP 8.0

Discussion in 'General' started by David620, Jul 25, 2021.

  1. David620

    David620 New Member

    I have followed the steps here to add PHP 7.4 and PHP 8.0 to my slave server. (Haven't done anything to master).
    I am using ISPConfig 3.2.4 and Debian 9.13


    After adding the additional PHP, I went to a site and changed the PHP-FPM version from Default to 8.0. I waited until the settings synced, and then checked the PHP version in my site and it was still PHP 7.0.

    I have verified that changing between PHP-FPM and PHP-CGI has an effect but the PHP version loaded in still 7.0. After checking the site configuration file under, /etc/apache2/sites-available/site.conf, I saw that ISPConfig still uses PHP 7.0 socket when using PHP-FPM.

    I was able to get PHP8.0 for my site working by manually changing the socket from PHP7.0 to /run/php/php8.0-fpm.sock

    I have also tried disabling using socket for PHP-FPM in the settings, but the site still loads in PHP 7.0

    Is there anyway to find out why ISPConfig is not loading PHP8.0? I would like to get at least PHP 7.4 working on the server. I would appreciate any help.
  2. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    Retrace you steps in adding php7.4 and php8.0 as you could have neglected and made mistake(s) at any steps.

    The tutorial was followed by many including me and it simply works when it is followed correctly.

    Also please don't change your Debian 9 default php to other higher php version as it will definitely cause problems to your ISPConfig server.

    Please restore that default php if you did change it.

    Lastly, do follow troubleshooting FAQ (Read Before Posting) when asking for help especially when expected things are not working as it should be as those information will help us to help you better.
  3. David620

    David620 New Member

    I have retraced my steps and verified everything was installed correctly. Default PHP version was also set back to PHP 7.0 (If I set it to PHP 8.0, then PHP-CGI loads 8.0 for the site).

    I found the issue on gitlab #6181 and #6161.

    Will it be okay if I edit the code directly since the PR has not been approved yet. Can I still upgrade ISPConfig down the line after I modify the files?
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Sure, you can upgrade ISPConfig later. But the issues you referred to are not causing PHP to fail nor to cause it to use a wrong PHP version. Using the central PHP socket directory is perfectly fine and will stay the standard anyway. My guess is that you looked at the code of the host file and you found a number in a path let's say 5.6 or 7.0 or 7,4 and you thought that this number is related to a PHP version, but in fact, that's not the case. You can not see in the vhost file which PHP version is used by looking at the paths, any numbers you find there are completely unrelated to PHP versions, the only way to see the actual PHP version is by putting an info.php file into the website with phpinfo() command inside.
    Last edited: Jul 26, 2021
  5. David620

    David620 New Member

    Hi, I was checking using phpinfo() first before checking vhost.

    However I have found the issue and it is something that I overlooked. There are a few ispconfig slave servers and for some reason all of them were upgraded to 3.2.4 and just this slave was using 3.1.15p1 without being upgraded at all. I guess different versions of master/slave cause problem. I have upgraded all to 3.2.5 and they work as expected now.

    Thank you everyone for your help :)
    till and ahrasis like this.

Share This Page