Warning! PHP-FPM configuration error found : No listen directive found in FPM config Click Save button below to update the PHP-FPM configuration and correct this error
I’m reopening another topic on that subject of loosing the php-fpm conf after upgrading Virtualmin, it happened again after the last upgrades to v8, all virtualhosts seems to loose the connection with their PHP-FPM conf and in the process loosing the specific settings made in Resource Limits.
When I say “all” it’s not accurate, it seems to me (after upgrading more than 20 servers) that serveurs that were set to use the default PHP version are not affected (PHP8.2 on debian 12), those using PHP7.4 or PHP8.4 are affected ….
I saw that v8 introduced the capability of adding from Virtualmin new versions of PHP so maybe next upgrades will go through no problem, I’m just opening this to mention the problem, all previous threads having been closed without a solution (I read all of them but maybe I missed something).
The good point of all this is that virtualhost still works no problem but still it’s annoying …
No, that’s unrelated to whatever issue you’re having. That’s just a page that allows installation.
Since both reports of this issue are on Debian, I guess there’s something happening related to that, and maybe not a Virtualmin thing.
Were there PHP updates at the same time as the Virtualmin update? I’m theorizing the package is doing something with the php-fpm config directories that’s breaking stuff..
I’ll note this theory isn’t unprecedented…the Debian mod_php package is particularly destructive on updates, in ways that are difficult to deal with (this isn’t the only reason to not have mod_php installed, but it’s the most obvious reason people have for realizing they made the mistake of installing mod_php).
Humm difficult to say. The flow of PHP updates is uninterrupted so I cannot be sure if there was a PHP update just before … My feeling (because this has been happening over the last 3-4 years) is that it is more or less linked to Virtualmin updates, but not all … I opened the ticket after reading all previous threads and because the v8 update seems to have affected almost all of my servers.
How interesting! @Jamie, do you have any idea what might be causing this? I thought we expected this bug to be fixed already, but it seems it hasn’t been resolved yet.