Empty Response errors after recent update

quantility

Member
Jan 18, 2016
6
0
1
Ferrara
cPanel Access Level
Root Administrator
Hi, what is changed after this security update?
I have some sites that use SOAP/WDSL that now have broken connection!

I receive error like "Warning/Error/Message(s): Error Fetching http headers" when using SOAP/WDSL api (like in Magento) or "Empty response" when we do some operation in frontend (like browsing with Chrome).
 

quantility

Member
Jan 18, 2016
6
0
1
Ferrara
cPanel Access Level
Root Administrator
Thanks, we have applied the update to mod_lsapi. Problem is solved! ;)
But my question is: why did this problem happen right after the Cpanel update? There was also an update of mod_lsapi or has anything changed?
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,910
2,213
363
Thanks, we have applied the update to mod_lsapi. Problem is solved! ;)
But my question is: why did this problem happen right after the Cpanel update? There was also an update of mod_lsapi or has anything changed?
Hi @quantility,

You can review the /var/log/yum.log log file to see which packages were updated just before this problem started. In this case, it corresponds with an update to the ea-apache24 RPM with Apache version 2.4.35.

Thank you.
 

quantility

Member
Jan 18, 2016
6
0
1
Ferrara
cPanel Access Level
Root Administrator
Hi, we have a similar problem.
After the tonight update to Cpanel 78, some site that communicate with API (json-rpc) & POST in an HTTPS enviroment, are not working!
We have opened a support ticket (n. 11487295) and something similar is happened this time too.

Cpanel support says: "Hello,
I have seen some cases where HTTPS and POST data changes when using lsapi, but I'm still looking for what causes it and what fixes it. I'm reaching out to other colleagues for more of this information and will get back to you again shortly. "

Someone have the same problem?
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,910
2,213
363
Hello @quantility,

To update, the issue was solved in the support ticket by reloading the CageFS mounts with the following command:

Code:
cagefsctl -M
Thank you.