This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.
If you have any content that you'd like to use, my recommendation would be to setup a Virtual Server for that, and then to place the content for it within the directory Virtualmin creates in /home/USERNAME/public_html.
Note that this is an Apache behavior, not really related to Virtualmin...except in the sense that Virtualmin manages Apache VirtualHosts. Apache can either serve VirtualHosts or you can have a single DocumentRoot without any VirtualHosts defined. You can't have both. If you have even one VirtualHost defined, Apache goes into virtual hosting mode...if you want anything in /var/www/html to be shown, you'll have to create a VirtualHost that points to that directory.
Or, you can do as Eric suggested, and use Virtualmin to create all of your sites, and put the content you want into one of those sites (in /home).
Howdy,
Virtualmin places domains within /home.
If you have any content that you'd like to use, my recommendation would be to setup a Virtual Server for that, and then to place the content for it within the directory Virtualmin creates in /home/USERNAME/public_html.
-Eric
Note that this is an Apache behavior, not really related to Virtualmin...except in the sense that Virtualmin manages Apache VirtualHosts. Apache can either serve VirtualHosts or you can have a single DocumentRoot without any VirtualHosts defined. You can't have both. If you have even one VirtualHost defined, Apache goes into virtual hosting mode...if you want anything in /var/www/html to be shown, you'll have to create a VirtualHost that points to that directory.
Or, you can do as Eric suggested, and use Virtualmin to create all of your sites, and put the content you want into one of those sites (in /home).
--
Check out the forum guidelines!