cPanel Curl Update breaks WHMCS Enom Module

brianc

• November 21, 2019 15:06

The enom module within WHMCS is no longer functioning with the following error message: Registrar Error CURL Error: 56 - OpenSSL SSL_read: Success Enom is saying this: We have concluded our investigation into the CURL error that WHMCS users have encountered, and determined the root cause to stem from a recent CURL update in the versions of cPanel used by many WHMCS installations. Since this is a third-party software configuration, affected customers needing further support should contact WHMCS. WHMCS is saying this: Have your servers upgraded to curl 7.67? If so please downgrade to curl 7.66 cPanel how do we do this and how in the world could something like this make it through to our production servers?

• 

  Raymond Hayes

  • November 21, 2019 20:24

  Same issue. But, our version of Curl is 7.29.0-54.el7 - Which does not explain the issues with Curl we have seen reported. Now, we must note: This is a Virtuozzo VPS for us...so, we do not have much control of the versioning to boot. Extremely serious issue. No purchases or updates can be done from WHMCS now. Affects both 84.0.13 and 84.0.14

  0
• 

  brianc

  • November 21, 2019 20:28

  What version of CURL is your PHP saying you are using with WHMCS? You can find that out within WHMCS Utilities -- System -- PHP Info. Mine says

  cURL Information

  7.67.0

  0
• 

  Raymond Hayes

  • November 21, 2019 20:33

  Sorry. Wrong version noted. We had 7.67. We just downgraded to 7.66, restarted apache....no change. Reboot?

  0
• 

  brianc

  • November 21, 2019 20:34

  How do you downgrade curl on a cPanel server?

  0
• 

  Raymond Hayes

  • November 21, 2019 20:48

  If using CentOS or other Hat flavor, from console do yum downgrade ea-libcurl Then if you use Apache, restart. I would restart php-fpm as well if in use. For us, we use Litespeed. We just restated httpd and then did Restart Detached php resources in Litespeed. Everything is working now on 7.66

  0
• 

  brianc

  • November 21, 2019 20:57

  Confirmed using 7.66 is working as well for me. I am also using version lock on libcurl until cPanel or whoever issues a fix for this.

  0
• 

  quietFinn

  • November 21, 2019 21:24

  downgrade ea-libcurl worked, and added versionlock also. Some additional info here:

  0
• 

  CODE grunt

  • November 21, 2019 21:32

  Restarting php-fpm was required in our case - was pulling my hair out trying to reconcile why the CLI version was different than the Apache version.

  0
• 

  Triggerbox

  • November 22, 2019 11:51

  Only running yum downgrade ea-libcurl ea-libcurl-devel
  from the Select Yes to restart the PHP-FPM service. Thanks!

  0
• 

  PPNSteve

  • November 22, 2019 15:00

  Same issue here as well.. will try downgrading curl to resolve immediate problem BUT I still want to know if there will be a priority fix by cPanel, etc.

  0
• 

  cPAusaf

  • November 22, 2019 19:03

  There was an unintended change introduced upstream in cURL 7.67 unfortunately:

  0

Please sign in to leave a comment.