Hi All,
We have a server with WHM 11.32.2 (build 18). There are numerous cPanel accounts configured on the server, each with it's own set of domains.
We're trying to add a new "addon domain" to one of the cPanel accounts and it appears to be added properly - it shows up in cPanel fine, the directory is created etc. We put some html files in the directory, and set the proper ownership and permissions.
But, when we try to visit the domain in a browser Apache is showing its own default index.html (located at /usr/local/apache/htdocs/index.html) instead of the index.html page of the new addon domain.
We checked httpd.conf and the domain appears to be configured properly best we can tell - the correct directory path is there so in theory Apache should show the domain's home page instead of its own default index.html
Previously we had no problem with new add-on domains. The only clue we have is that this condition exists after upgrading WHM 11.32.2 (build 18), although we can't say that the upgrade is the source of the problem since we don't know for sure.
Any ideas how to troubleshoot this and resolve it?
We have a server with WHM 11.32.2 (build 18). There are numerous cPanel accounts configured on the server, each with it's own set of domains.
We're trying to add a new "addon domain" to one of the cPanel accounts and it appears to be added properly - it shows up in cPanel fine, the directory is created etc. We put some html files in the directory, and set the proper ownership and permissions.
But, when we try to visit the domain in a browser Apache is showing its own default index.html (located at /usr/local/apache/htdocs/index.html) instead of the index.html page of the new addon domain.
We checked httpd.conf and the domain appears to be configured properly best we can tell - the correct directory path is there so in theory Apache should show the domain's home page instead of its own default index.html
Previously we had no problem with new add-on domains. The only clue we have is that this condition exists after upgrading WHM 11.32.2 (build 18), although we can't say that the upgrade is the source of the problem since we don't know for sure.
Any ideas how to troubleshoot this and resolve it?