CPANEL-40507 - WHM/CPANEL Broke two sites on my server (that I know of) out of the blue today.
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.
-
@cPRex sir clients are getting angry, every few days any client comes and says his website is not working redirecting to default web page. Some clients gets serious bcz they think their website's data has been deleted or something wrong happened. I will lose clients if it's not fixed soon. Please try to fix it as soon as possible. 0 -
Still hapenning in CentOS 7.9 + cPanel 102.0.15 0 -
It's very annoying issue, today 3 domains started redirecting to default web page clients were yelling at us and posted bas reviews. Cpanel please fix this issue i request sir 0 -
Clients complaining. Clients restoring backups because they think they lost data. Client telling us how we haven't fixed this in almost 2 months. Cpanel shouldn't be giving us more work to do, on the contrary... 0 -
is this only on CentOS 7 or Cloudlinux servers? or has anyone confirmed same issue on Almalinux 8.5 /8.6 or Ubuntu with cPanel 102.0.15 ? thanks 0 -
is this only on CentOS 7 or Cloudlinux servers? or has anyone confirmed same issue on Almalinux 8.5 /8.6 or Ubuntu with cPanel 102.0.15 ? thanks
It has nothing to do with the operating system, the problem is with cpanel. Maybe if they give a new raise they will fix the problem. Greedy webpros love to price raise.0 -
It has nothing to do with the operating system, the problem is with cpanel. Maybe if they give a new raise they will fix the problem. Greedy webpros love to price raise.
Thanks for your reply. Was just asking. Since I do not have this issue :)0 -
102.0.16 is released just FYI. 0 -
Thanks for your reply. Was just asking. Since I do not have this issue :)
with around 20.000 sites, we see this 1-2 times every few days... sometimes 2 times on the same day. sometimes 1 time in 3-4 days, so is easy not to see (plus, client HAS to notice and report it)0 -
it is interesting, i can not understand why cpanel set this version as stable. 0 -
Has anyone experienced any issues since the .16 update? 0 -
Has anyone experienced any issues since the .16 update?
Hi, two days ago,i get the same issue on a server with RELEASE version, so,had 102.0.15 or 102.0.16 fix it ? i just think the issue should be fixed, and wait some days without issue, and then release it as stable, it will be better.0 -
0.16 has fixes for all the issues we're currently aware of, and that was released yesterday. 0 -
0.16 has fixes for all the issues we're currently aware of, and that was released yesterday.
Hi, but i check the stable version is 102.0.15 now, do we need switch all servers to RELEASE ? or will you set stable as 102.0.16 today,too ?0 -
We've been getting great feedback on the .16 version, so it will be moving to stable very quickly. 0 -
We are planning to move .16 to Current in about one hour. 0 -
with around 20.000 sites, we see this 1-2 times every few days... sometimes 2 times on the same day. sometimes 1 time in 3-4 days, so is easy not to see (plus, client HAS to notice and report it)
Thanks for you reply Jose. I"m sure it"s a big headache and I hope the issue is fixed for you as well in .16 Kind Regards, Spiro0 -
I just experienced this with the latest version .16 Client #1 Posted today at 09:54 This website is down again. It's not just me. Please see attached. Client #2 Posted today at 09:59 hi, my ssl for the website was working perfectly, but just now everything stopped and it tells me i don't have ssl any more. please could you let me know what happened? thank you Ari Client #3 Posted today at 10:25 Few Hours ago everything was working fine. I just checked now and I discovered an ssl error so Ignored it on my browser and proceeded only to find out that there's an error stating that the ip address has changed. Below is the screenshot of the page. This affected even addon domain Operating SystemCloudLinux v6.10.0 ProductcPanel & WHM v102.0.16 (STANDARD) [root@esja ~]# /scripts/rebuildhttpdconf && /scripts/restartsrv_apache info [rebuildhttpdconf] Creating missing document root /home/populart/public_html for populart Built /etc/apache2/conf/httpd.conf OK Waiting for "httpd" to restart gracefully "[OK] Send SIGUSR1 to 2769340 waiting for "httpd" to initialize "finished. Service Status httpd (httpd (lscgid)) is running as root with PID 2778451 (pidfile+/proc check method). Startup Log [OK] Send SIGUSR1 to 1593978 httpd restarted successfully. [root@esja ~]# Rebuilding fixed it, this is still happening.. What they refer to is that they are intercepted with a non-ssl saying intrusion, when its just defaulting to our wildcard certificate because their VHOST is missing. It's ongoing for 2 weeks now @cPRex and I can confirm that I am using the 102.0.16 (STANDARD) To rule all doubt when the update occurred lrwxrwxrwx 1 root root 62 May 18 22:26 last -> /var/cpanel/updatelogs/update.1947520.565324545.1647259516.log => Log opened from /usr/local/cpanel/scripts/updatenow (1947533) at Wed May 18 22:26:02 2022 [2022-05-18 22:26:02 +0000] Running version '11.102.0.15' of updatenow. [2022-05-18 22:26:02 +0000] Detected version '11.102.0.15' from version file. [2022-05-18 22:26:11 +0000] Target version set to '11.102.0.16' [2022-05-18 22:26:11 +0000] Switching to version 11.102.0.16 of updatenow to determine if we can reach that version without failure. [root@esja updatelogs]# date Thu May 19 10:38:02 GMT 2022 --- So I am confirming that as of this morning at least when they sent us this, their vhost was missing in the file. I don't know if all those 3 just found this out about 12 hours too late or if it happened this morning but so far I'm skeptic. EDIT: Client confirms Posted today at 10:43 Yes, the site was working fine yesterday. It went down at 9:50 UTC this morning. From Uptime Robot: The monitor Buildings & Cities xxx is currently DOWN (Connection Timeout) Event timestamp: 2022-05-19 09:50:13 UTC+0 According to this, the events took place 09:50 this morning server time,the patch took place 22:26 yesterday, about 12 hours ago, so this happened during .16 patch. 0 -
@Steini Petur - could you please make a ticket? 0 -
@Steini Petur - could you please make a ticket?
Done @cPRex, I gave them some access to investigate whilst being careful. It's a production server, all my clients the 3 they all told me the "site worked few hours ago" which would suggest this happened way after the patch from yesterday..0 -
Thanks so much! So far I haven't had any other reports of the behavior yet today, so I'm wondering if your issues could be something else. We'll find out in the ticket! 0 -
Thanks so much! So far I haven't had any other reports of the behavior yet today, so I'm wondering if your issues could be something else. We'll find out in the ticket!
Feel bad to report this to you @cPRex but here it goes.. --- Hello, Thank you for your patience. This does appear to be a continuation of the previously patched issues with domains missing from the httpd.conf. I do see some domains being added to and removed from the server between the update and the first reported time frame noticing the domains missing: There are also a lot of AutoSSL notifications being sent out shortly before the reported issue happened: We have opened another internal case, CPANEL-40671, regarding domains missing from the httpd.conf again. As before, running /scripts/rebuildhttpdconf gets the missing domains readded, and /scripts/restartsrv_httpd restarts the service with the new configuration file as outlined on the support article below:0 -
I can confirm, issue appears on .16 still. we got our first report today. 0 -
Scary how long this issue will last, this is one enormous change that had some drastic side effects 0 -
Last night we published an autofixer under case CPANEL-40694 which fixes an issue with the /etc/apache2/conf/httpd.conf.datastore being built. That autofixer ran automatically as part of last night's update. At this point, we're really only seeing fringe cases and so far today, things have looked good. Please let me know if you continue to see anything out of the ordinary at this time. 0 -
Since the autofixer was pushed two nights ago, I haven't heard any reports of this issue on the Forums or through our ticket system. Has anyone here seen a problem in the last 48 hours? 0 -
we did have a case this week, not sure wich day. i'll report if we get a new case. 0 -
We've not received one case since May 20, when I was talking about my case.. I can't confirm if there has been a case where a vhost is removed and then rebuilt as we get new clients every day, we're constantly getting new clients so the rebuildhttpd conf is running often. However for 8 whole days we've been without one, my last reply here was just to clarify that this has been one of the scariest issues that entered stable release since I can remember. 0 -
Hi,we got one case about 5/26. 0
Please sign in to leave a comment.
Comments
105 comments