Two sites had their document root paths crossed up out of the blue in the middle of the work day. No one on my team was even working on anything on the server. Apparently WHM did something to the HTTPD config that caused the issue.
The issue is that for both sites we have the following setup:
MainDomain -> MainDocRoot
AlternateDomain -> AlternateDocRoot
HTTP requests started being served instead as:
MainDomain -> AlternateDocRoot
AlternateDomain -> AlternateDocRoot
On one of the sites, AlternateDocRoot just had a simple .htaccess file with a redirect back to MainDomain.com and that caused that site to go down in a fire death of "too many redirects" for all of its visitors. The other site was just showing a "landing page" instead of their actual website due to the wrong document root.
What both sites have in common is that they both have their original document root folder "public_html" replace with a symlink to a project sub-directory, eg:
~/public_html -> ~/project/web
This configuration is NOT unique to these sites though. I have at least 5 other sites that use the same set up and did not have issues come up.
My managed server team over at liquid web is looking into this to see if there is anything in the cpanel/whm logs that can indicate to us what happened and why. I will report back when I get more information from them.
We were able to resolve the problem rebuilding the HTTPD conf file. However I am VERY concerned that this happened. I cant be having WHM/CPANEL just mangling site configs out of the blue.
The issue is that for both sites we have the following setup:
MainDomain -> MainDocRoot
AlternateDomain -> AlternateDocRoot
HTTP requests started being served instead as:
MainDomain -> AlternateDocRoot
AlternateDomain -> AlternateDocRoot
On one of the sites, AlternateDocRoot just had a simple .htaccess file with a redirect back to MainDomain.com and that caused that site to go down in a fire death of "too many redirects" for all of its visitors. The other site was just showing a "landing page" instead of their actual website due to the wrong document root.
What both sites have in common is that they both have their original document root folder "public_html" replace with a symlink to a project sub-directory, eg:
~/public_html -> ~/project/web
This configuration is NOT unique to these sites though. I have at least 5 other sites that use the same set up and did not have issues come up.
My managed server team over at liquid web is looking into this to see if there is anything in the cpanel/whm logs that can indicate to us what happened and why. I will report back when I get more information from them.
We were able to resolve the problem rebuilding the HTTPD conf file. However I am VERY concerned that this happened. I cant be having WHM/CPANEL just mangling site configs out of the blue.
Last edited: