You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apache versions are now compiled with VS17, and Laragon automatically sets the 1st line of fcgid.conf to LoadModule fcgid_module "D:/Laragon/etc/apache2/modules/mod_fcgid-2.3.9-Win64-vs17.so"
however this file does not exist.
Laragon needs to check for the latest FCGID and VS versions for which there is a mod_fcgid-*-win64-vs*.so file and use that.
In this case it should be LoadModule fcgid_module "D:/Laragon/etc/apache2/modules/mod_fcgid-2.3.10-win64-VS16.so".
Note: A workaround is to edit the file manually and then set the read-only property.
The text was updated successfully, but these errors were encountered:
It is indeed indirectly related to that. I have installed a non-thread-safe version of PHP so that I can use it with nginx. And Laragon has correctly detected that and has "included" fcgid.conf as a direct consequence - but has created a version of fcgid.conf that points to a non-existent module file (which is a bug).
Apache versions are now compiled with VS17, and Laragon automatically sets the 1st line of
fcgid.conf
toLoadModule fcgid_module "D:/Laragon/etc/apache2/modules/mod_fcgid-2.3.9-Win64-vs17.so"
however this file does not exist.
Laragon needs to check for the latest FCGID and VS versions for which there is a
mod_fcgid-*-win64-vs*.so
file and use that.In this case it should be
LoadModule fcgid_module "D:/Laragon/etc/apache2/modules/mod_fcgid-2.3.10-win64-VS16.so"
.Note: A workaround is to edit the file manually and then set the read-only property.
The text was updated successfully, but these errors were encountered: