Update Failed: Failed to enable crypto error:14090086:SSL routines

[MtAydemir]

Hi,

#RSY-558042 no one answered the request for support.

I get this error during the update and I have a problem with all WHMCs installations:

Error (Help Documentation)
Error: failed to open stream: operation failed
Failed to enable crypto
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
The "https://releases.whmcs.com/pkgs/whmcs-7.3.0-release.1.zip" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:
[Composer\Downloader\TransportException]
Downloading
- Installing whmcs/whmcs (7.3.0)
Updating dependencies
https://releases.whmcs.com could not be fully loaded, package information was loaded from the local cache and may be out of date
failed to open stream: operation failed
Failed to enable crypto
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
The "https://releases.whmcs.com/packages.json" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:
Loading composer repositories with package information

 

-------------------------------------------------------------------------------------------------------------------------------------------

I am having problems with all whmcs software.

So I thought it was a problem with the server and I communicated with cPanel.

The Cpanel team did research on the server and gave this answer:

Hello,

Thank you for your patience while I reviewed your issue further. Please note that cPanel does not directly develop or maintain WHMCS, so our ability to provide support for their plugin and billing system is quite limited. I did however review your system to confirm as much information as I could.

The reported error indicates that your content is attempting to connect to https://releases.whmcs.com with an invalid cabundle. I checked over your PHP installation and local packages, but I found no issues with the services. I was able to test and connect manually using OpenSSL and verified that your SSL settings in Apache/PHP are correct.

===
[08:07:01 ******** root@****** ~/cptechs]cPs# openssl s_client -connect releases.whmcs.com:443 
CONNECTED(00000003)
depth=3 C = US, O = "VeriSign, Inc.", OU = Class 3 Public Primary Certification Authority
verify return:1
depth=2 C = US, O = "VeriSign, Inc.", OU = VeriSign Trust Network, OU = "(c) 2006 VeriSign, Inc. - For authorized use only", CN = VeriSign Class 3 Public Primary Certification Authority - G5
verify return:1
depth=1 C = US, O = Symantec Corporation, OU = Symantec Trust Network, CN = Symantec Class 3 Secure Server CA - G4
verify return:1
depth=0 C = GB, ST = Buckinghamshire, L = Milton Keynes, O = WHMCS Limited, CN = *.whmcs.com
verify return:1

This indicates that the local call is attempting to use an invalid method that is being rejected by the remote server. The error reported "SSL3_GET_SERVER_CERTIFICATE:certificate verify failed" indicates that the code is attempting to connect using SSL3. Since this method is deprecated/insecure, the remote system and your server both have this method disabled.

At this time I recommend reaching out to WHMCS support for further assistance. They will be able to review the local information and best advise you on how to proceed.

As a courtesy I also looked around online and found the following discussion on WHMCS's site. This is rather old and may not be relevant(as its the same error, but from curl), but it does indicate their team was able to provide an update script to correct a similar error.

https://whmcs.community/topic/76593-curl-error-60/

Let me know if I can be of any further assistance or if you have any additional questions.

[burnleyvic]

Hi, for the server your site is running on can you please post here the versions for:

- Operating system (distro, version)

- OpenSSL

- PHP, I'm suspecting you're running PHP 5.6.

[MtAydemir]

Hi,

The problem has been solved.

The problem is caused by php_open_basedir settings. When we disable this setting for the site, the update is successful.

[WHMCS John]

Hi @MtAydemir,

Thanks for following-up with a workaround. I have created a troubleshooting guide which investigates the causes of the problems and identifies some permanent solutions: http://help.whmcs.com/m/72132/l/812446-troubleshooting-a-file-could-not-be-downloaded-error

Our of interest, what was your open_basedir setting when you first attempted the update process?

I'd be interested in reproducing the issue and seeing if we can add a pre-flight check to the auto-updater to identify the problematic configuration before starting the update process. That would result in a friendly and more informative error message.

Thanks in advance for your help!

[MtAydemir]

Hi @WHMCS John

There was no specific setting. We closed the php_open_basedir. problem solved.

Despite all our experiments, the only solution we found was that.