Currently Being ModeratedMay 7, 2012 7:06 AM (in response to rsthilaire2008)
I just edited the "servermgr_web_apache2_config.plist" file also, adding a new item and duplicating all the child items, changing the ServerName and the _id_.
Still nothing. Again, any help is appreciated.
Currently Being ModeratedMay 7, 2012 8:12 AM (in response to rsthilaire2008)
The most likely reason you're getting the default OS X Server login is that Apache does not have a virtual host established for the server, or there's nothing in the specified web directory, or that whatever's been established is pointing to the default OS X Server web directory. That there's a configuration error.
And FWIW, the usual mechanism for managing web sites on OS X Server 10.6 is the Server Admin.app tool, and that handles multiple Apache virtual hosts - what Apple calls "sites" -- without problems. Modifying the plist files and related files directly can potentially derail use of the Server.app and Server Admin.app tools, and potentially cause problems for upgrades, etc.
Currently Being ModeratedMay 7, 2012 9:52 AM (in response to MrHoffman)
Mr.Hoffman, all the virtual hosts are established in the Apache2>Sites folder. Each site has its own .conf file.
The most recent is the domain above and is created and pointing to the directory it should be. There is also an index.html in that directory.
All of the changes I made were duplicates off of a site that is live and working.
I had started with the Serveradmin in file sharing. But then was directed to the Apach folders by another mac forum user. Do you have specific direction on how the site should have been created? I am very new to this, so any questions or images I can provide would not be a problem. Thank you in advance.
Currently Being ModeratedMay 7, 2012 11:17 AM (in response to rsthilaire2008)
SOLVED. I restarted apache, unshared and shared again. Rest the permisions and the protocals. Emptied my cache and it worked. Thank you for taking the time to help.
Currently Being ModeratedMay 7, 2012 3:04 PM (in response to rsthilaire2008)
If you're on OS X client or on various other platforms, editing the Apache configuration files is how you're usually obligated to manage Apache.
If you're on OS X Server, then launch Server Admin.app and have a look at the web management section of that tool. That tool (or Server.app, depending on your specific task and your preferred requirements) is how Apache is managed.
The downside of having hand-edited the configuration files is as stated earlier; Server Admin.app may decide to clobber what you've done.
For details on administering Apache on OS X Server, please consider reading the Apple Web Technologies Administration Manual (10.6) for an introduction. And should the Apple directions conflict with a forum poster's comments, well, then you're left to make a decision. (There are cases where I've been obligated to go past what erver Admin.app and related have to offer, but those cases have been comparatively infrequent.)