A few days ago I needed to have some directive changes in Apache but they were rejected because Apache 2.4 did not understand them. Isn’t it time to upgrade Apache in Virtualmin to support newer directives?
Your OS determines your Apache version, not us. If you want a newer Apache, use a newer OS.
We trust you to choose the OS that suits your needs and we don’t replace components arbitrarily. Because CentOS/RHEL don’t have suexec-custom, we have historically provided our own build of the CentOS/RHEL httpd package, but it identical to the upstream package except for the suexec path being set to home. So…even though we’re providing the package, we aren’t dictating what version it is, your OS is.
OK, I guess I misread some of the archived forum posts. The thing is this; Apache was listed as from the Virtualmin repo; or at least that is what it appeared to be when I put the original httpd back. I found a repo that actually provided an up to date version of Apache. So if that repo is on the server when I install Virutalmin, then it should install that version of Apache. I actually did upgrade Apache but removing the old httpd resulted in some issues. At this time I am having issues after the whole upgrading of Apache so since the server is not an active webserver as such, I think I will wipe it and install Virtualmin with Nginx.
If you’re using CentOS 6 or 7 you need the custom build with suexec pointing to /home, if you’re using any execution mode that requires it (CGI, fcgi). You can’t use arbitrary packages (and we never recommend it, even when there isn’t a custom requirement, unless you really know what you’re doing…folks who’ve broken their systems by installing packages from third party repos is a running theme around here). If you must use a different package than ours, you’ll need to rebuild your own with suexec set to /home, or don’t use suexec (use PHP-FPM or app servers).
We have stopped shipping a custom httpd package for CentOS/RHEL 8, with the resultant limitation that you can no longer use CGI/fcgi/suexec (again, PHP-FPM is the only way to run PHP, and all other languages have to use an app server and proxy from Apache/nginx…which is the recommended way to run things, regardless).
Oh, and to be clear: You should never enable third party repos before installation of Virtualmin. If you are going to use anything custom, or add third party repos, you must do that after installation. Installation is not designed to accommodate arbitrary packages from third party repos. It’s hard enough to stay on top of the OS-provided package updates and make sure they don’t break the installation.
OK, understand. Install Virtualmin first and then work on upgrading such things as Nginx and Mariadb. Thanks for reminding me. I think I did it wrong once before and ended up having to start over.
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.