Well, I’d recommend against using Fedora for hosting a Virtualmin server. It’s not a supported distro – we’d recommend something like CentOS, Scientific Linux, or Ubuntu LTS for that.
However, although it’s not supported – it should indeed work if you setup everything manually.
We’ve sometimes seen that error after something on the disk was changed, but the running processes wasn’t restarted.
I’m curious if that issue goes away after restarting Webmin, using “/etc/init.d/webmin restart”.
I installed Virtualmin on Fedora 15, I imported some domains from CentOS 6 to Fedora 15 and Virtualmin works just fine (just the installation took “a bit” longer). I haven’t tested all the features (since I don’t have a static ip address etc on my Desktop), I just use it as a better alternative to XAMPP etc.
Hrm, I’m not sure I follow… it’s normal to be able to access a cgi-bin dir using www.example.com/cgi-bin.
How is your system setup there, and how does that differ from a normal Virtualmin setup?
Though, I’ll offer that cgi-bin is just a setting in the Apache config… if you want to tweak the cgi-bin settings for an existing domain, you can look in /etc/httpd/conf/httpd.conf, where you can review the VirtualHost block for that domain.
To tweak things for future domains, you can go to System Settings -> Server Templates -> Default -> Apache website, and take a look at “Directives and settings for new websites”.
Ok had to go into squrrelmail and set it up manually after virtualmin set it up. The imap and smtp
ports were wrong in the squirrelmal setup. So I ran ./configure script and got it going.