Submitted by JamieCameron on Fri, 06/02/2017 - 10:22Comment #3
So if I am reading the original thread right, the problem is that you have a Directory block with the path /home/*/public_html instead of the actual domain's directory? Because this is definitely not supported by Virtualmin and will cause all kinds of breakage, beyond just detecting the PHP mode wrong.
Submitted by jabowery on Sat, 06/03/2017 - 10:07Pro LicenseeComment #4
That's right -- the thing that triggered the incorrect PHP mode was something not supported by Virtualmin. I was attempting to import a website that had been managed by Plesk to Virtualmin -- which is hard enough without bad error messages sending people on a wild goose chase that, ultimately, has them stepping through Virtualmin code with the Perl debugger.
Submitted by JamieCameron on Sat, 06/03/2017 - 16:29Comment #5
In this case, was the Directory block that used /home/* inside the domain's Virtualhost block? If not, there's no way that Virtualmin could even theoretically detect that another PHP mode is in use. In which case, it falls back to assuming mod_php, which is typically configured globally.
Comments
Submitted by andreychek on Tue, 05/30/2017 - 14:05 Comment #1
Howdy -- it's possible that there is a configuration issue that's causing that problem.
Would it be possible to put a file named "test.php" into the public_html folder for that domain, and place the following into that file;
<?php phpinfo(); ?>And then would it be possible for us to see the resulting URL?
Thanks!
Submitted by jabowery on Fri, 06/02/2017 - 10:09 Pro Licensee Comment #2
At the top of the linked post, I gave the line of Virtualmin Perl code and the
Directorydirective that triggers the bug.What's this about "configuration"?
Also, how can I provide the "resulting URL" without publishing the domain name I'm working on?
Submitted by JamieCameron on Fri, 06/02/2017 - 10:22 Comment #3
So if I am reading the original thread right, the problem is that you have a Directory block with the path
/home/*/public_htmlinstead of the actual domain's directory? Because this is definitely not supported by Virtualmin and will cause all kinds of breakage, beyond just detecting the PHP mode wrong.Submitted by jabowery on Sat, 06/03/2017 - 10:07 Pro Licensee Comment #4
That's right -- the thing that triggered the incorrect PHP mode was something not supported by Virtualmin. I was attempting to import a website that had been managed by Plesk to Virtualmin -- which is hard enough without bad error messages sending people on a wild goose chase that, ultimately, has them stepping through Virtualmin code with the Perl debugger.
Submitted by JamieCameron on Sat, 06/03/2017 - 16:29 Comment #5
In this case, was the
Directoryblock that used/home/*inside the domain'sVirtualhostblock? If not, there's no way that Virtualmin could even theoretically detect that another PHP mode is in use. In which case, it falls back to assumingmod_php, which is typically configured globally.Submitted by jabowery on Sat, 06/03/2017 - 17:22 Pro Licensee Comment #6
It was inside the domain's
VirtualHostblock.Submitted by JamieCameron on Sun, 06/04/2017 - 14:25 Comment #7
Ok .. I wonder why cpanel uses a
*in the path, when it can only possibly match a single domain's home directory?Submitted by JamieCameron on Sun, 06/04/2017 - 14:28 Comment #8
Anyway, the 6.00 release of Virtualmin will handle this case.