<div class='quote'>This whole install have been nothing but problematic I was hoping that it was a faulty install that was causing my previous mail, and cgi problems. I even used webmin to install all modules during the testing process.</div>
That's not the way to install a full Virtualmin stack. Installing Webmin modules does nothing to the underlying system--it simply can't. Webmin module packages don't have that kind of capability--they're just tarballs (though Webmin does do some dependency resolution against other Webmin modules and such).
There is an install script for Virtualmin found on the download page here at Virtualmin.com. It does a complete install of all dependencies (like Apache, BIND, Postfix, etc.) and it configures them appropriately for use with Virtualmin. Installing and configuring manually is certainly possible...but it's not something I'd suggest unless you're a pretty serious Linux nerd.
<div class='quote'>It is the public version so I guess that is a possible reason why.</div>
The install script is available for both Virtualmin GPL and Virtualmin Professional. There is quite a bit of documentation about installing Virtualmin here:
Check out the forum guidelines!
<div class='quote'>script failed, incorrectly reported os</div>
That'd be something I'd want to know about. If you really are running a supported OS version, it should work...if it doesn't, I want to fix it. Give me more details! ;-)
What details do you need?
How can I Disable suexec in Virtualmin??
I found it:
System Settings â
Well, as an FYI, this stuff you're running into is all corrected when using a distribution that works with the install script :-)
Fedora has a short life cycle, and doesn't go hand in hand well for server use... I would highly suggest looking into using an alternate distribution, that'll make your life much easier :-)
You're not seeing the Virtualmin software repository, because you're missing the virtualmin.repo file that points to software.virtualmin.com/gpl/ -- but that's something you can add manually.
You're getting the above SELinux errors because SELinux was never disabled. You can manually disable that in /etc/selinux/config, and then reboot.
<div class='quote'>You're not seeing the Virtualmin software repository, because you're missing the virtualmin.repo file that points to software.virtualmin.com/gpl/ -- but that's something you can add manually.</div>
The virtualmin-universal repository is something he can add manually (and should), but it won't help him with Apache. We only provide Apache on supported operating systems...and Fedora 9 isn't a supported system for Virtualmin GPL (it is for Professional, but we still strongly discourage use of Fedora on servers).
Apache will need to be rebuilt, if you want to use suexec. Docs for that process have been posted here in the forums a few times, and I can help you find it if you don't have any luck searching for those threads.
Gah! Yeah, Joe's right.. my bad, I completely didn't think about the lack of Virtualmin packages for Apache :-)
So yeah, that's another reason to consider a supported distro ;-)
My problem is I have several things already running under var/www what am I supposed to do? Tell all my users oh sorry need to scrap evewrything and reinstall because virtualmin has to be in /home and refuses to use var/www.
Why is it not possible to just tell virtualmin to use what is currently setup?
<div class='quote'>Why is it not possible to just tell virtualmin to use what is currently setup? </div>
You can, in System Settings -> Module Config -> Defaults for new domains -- you can set whatever home directory you want in there, including /var/www.
The problem you'll run into is with suexec specifically. It has to be compiled with a path for which it will run. The suexec distributed with Virtualmin is compiled for /home.
So it's no problem if you want to use /var/www, but you'll need to either:
1. Disable suexec (in System Settings -> Server Templates -> Default Template -> Apache Website, "Automatically add appropriate SuExec directive".
2. Don't use Virtualmin's Apache packages, using the ones included with your distro instead
3. Compile suexec manually, pointing suexec to the location of your choice
I have been reading this thread and was trying to follow the advice because I am having the same issues.
Now do you mind telling me how I can disable Suexec? Where is System Settings -> Server Templates -> Default Template -> Apache Website? I tried looking for it in Webmin but I never found it. I check virtualmin directory and never found it either.
I hope you I get answer.
You need the Virtualmin Framed Theme. Trying to run Virtualmin without it is just asking for a life of suffering and confusion. While you're at it, think about whether you can start with a fresh OS install and run our install script instead of trying to setup Virtualmin manually. It'll save you a lot of time, and these kinds of questions won't even come up (both the suexec question and the menu item location question).
From the sounds of it Installing virtualmin at this stage would be more trouble then it's worth. If I had a blank server I hadn't yet installed anything on it'd be no problem to then set everything else up in home. Since Virtualmin has to do things differently I won't in all likelyhood be using it unfortunately.
<div class='quote'>Since Virtualmin has to do things differently</div>
Eric <i>just</i> explained that that is not true. I'm not sure how you could have interpreted his advice as being "Virtualmin has to do things differently". Virtualmin is nothing if not flexible.
But, you do what you have to do. ;-)
I found a fix for this in Ubuntu 9.04. working on another issue, I ran into a dir called suexec, under /etc/apache2. In the suexec folder is a file called www-data. I edit the file to read as...
/homepublic_html/cgi-bin# The first two lines contain the suexec document root and the suexec userdir# suffix. Both features can be disabled separately by prepending a # character.# This config file is only used by the apache2-suexec-custom package.
Once started, I checked it again and now it is happy!
All commands needed to create and restore backups are installed.
.. your system is ready for use by Virtualmin.
Updating all Webmin users with new settings..
Updating status collection job ..
on debian lenny run ok
after install go to
edit the file
u can see the first 2 lines,
make the changes:
ctrl+x and say Y for save the changes
after, restart apache
y para los que hablan español (mi ingles es pesimo)
en debian lenny corre ok
despues de la instalacion, ir a
editar el archivo
pueden ver las 2 primeras lineas,
hacer los cambios:
ctrl+x y diga S para grabar los cambios
despues reiniciamos apache
On a new CentOS system his did the trick for me....
Try this step (assuming all of the templates and stuff reference $HOME rather than absolute paths containing "/home"
In Users and Groups / Module Config (in Webmin:System) set the default home directory to /var/www/html
Hope this helps!
I fixed this in the GPL version by installing the package apache2-suxec-custom
It has a config file located in the directory /etc/apache2/suxec
In this file you can configure the necessary paths.
Seems this error persists even six years later.
Installed CentOS 6.5 x64
Tried to install Virtualmin through Webmin... fail
Anyway, I'm trying install.sh now. Very disappointed that Virtualmin couldn't be installed separately from Webmin, and now that I already tried the Virtualmin installation install.sh may fail too. I might have to rewind to another fresh installation of CentOS. :(