I have installed and in the process of attempting to get ISPConfig to behave, but I'm hitting some major roadblocks. This is my first time using this software, and I realize that I may have mis-configured the software, or incorrectly answered the installation questions. I'm not finding anything in the manual or the forum that seems to address these issues. A note... I'm running Gentoo, and I installed the softwar using these instructions: http://www.lostregions.de/index.php?option=com_jd-wiki&Itemid=31&id=ispconfighowto:wiki When I set up a user or site, it completely replaces my current configs (http.conf, 00_default_vhost.conf and bind configs) with only the settings that were done through ISPConfig. Obviously, if I really wanted to I could re-do everything in ISPConfig. Also, when I set up a new user or site, it sets the user up as "web#" (where # is a number generated by ISPConfig), instead of the user's username. It also seems to require that a user have a domain name, so I cannot set up a user with www.mydomain.com/~user. It also seems to set the home directory for the user in the wrong place as well. It should be /home/[user]/, and the pages be located in /home/[user]/public_html/. Thank you.
Thats the intended behaviour. ISPConfig must be installed ony empty server. You can not use other controlpanels together with ISPConfig. The installer warns you about that! Thats the user prefix to prevent username collisions between websites. You can deactivate it under management > system config > settings. There is nothing wrong with that. ISPConfig is a hosting controlpanel for internet service providers and it is common that users where grouped by domain in this business. Maybe you select the wrong software for your purpose, ISPConfig is not intended to manage a few linux system users in the /home directory.
Thank you for your information. My server is largely empty, as it only has a few items with my own information on it. It would not be too difficult to make the changover. Perhaps I was overestimating how many users would want webhosing without a domain name, but I suppose that for those individuals I could simply use a script that I've put together. You are probably correct that the vast majority of users would want a domain name for webhosting, and as such ISPConfig should do the trick.
