|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #78891 Bug with CURL completely stopped working
Submitted: 2019-11-30 01:45 UTC Modified: 2019-12-04 14:33 UTC
From: gilperon at gmail dot com Assigned:
Status: Duplicate Package: Unknown/Other Function
PHP Version: 7.2.25 OS: all
Private report: No CVE-ID: None
 [2019-11-30 01:45 UTC] gilperon at gmail dot com
The test script does not work anymore using Curl with any destination that is HTTPS. If you try any destination with HTTP it will work just fine. On .24 version this bug ONLY would happen when you first connected to a database and after that tried to use CURL. But now, this bug affects using only CURL and doesnt need to connect to database to trigger it anymore. This bug just got a lot more serious.

Test script:

$curl = curl_init();

$opts = array();

$opts[CURLOPT_URL] = "";


echo curl_exec($curl);


Expected result:
I should see the content of the requested url

Actual result:
Nothing is shown.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2019-11-30 07:47 UTC]
-Status: Open +Status: Duplicate -Assigned To: +Assigned To: cmb
 [2019-11-30 07:47 UTC]
Please stop reporting the same issue over and over again.  Thanks.
 [2019-11-30 12:13 UTC] gilperon at gmail dot com -> clearly you didnt read this bug report! It's different from ANY of the other bugs I reported!

Now, the CURL simply does not work. It does not matter if you will open a database connection previsouly or if you create a previous connection with SSL. No!

 [2019-11-30 12:30 UTC]
-Status: Duplicate +Status: Open -Assigned To: cmb +Assigned To:
 [2019-11-30 12:30 UTC]
 [2019-11-30 13:09 UTC]
-Status: Open +Status: Feedback
 [2019-11-30 13:09 UTC]
This issue is almost certainly not on the PHP side, but either due to a libcurl update (maybe you pulled one in together with a PHP update?) or a misconfiguration of the certificate store (most likely).

The fact that this happens with just curl, that there have been no recent code changes (in PHP) in this area, and the issue is not reproducible by other people (I just tried your code, works just fine) is a pretty strong indication of that.

To say more here, at the very least it would be important to know a) what error curl reports and b) what libcurl version you're using and whether it was updated recently.
 [2019-11-30 17:06 UTC] gilperon at gmail dot com thanks for your attention. I can easily reproduce this bug installing LAMP on a CENTOS 7 new server on Linode. Just fire a cloud server, install lamp with PHP using 7.2.25 and the bug happens.

Using file_get_contents the bug does not happen. Only with CURL. Also, the CURL code that I provided you, does not return any error, just an empty string when the requested domain contains HTTPS protocol. 

There is no error reported at error_log of Apache!

Regarding the version of the libcurl I executed the code "var_dump( curl_version() );" and I got this:

array(9) {
  string(6) "7.29.0"
  string(23) "x86_64-redhat-linux-gnu"
  string(8) "NSS/3.36"
  string(5) "1.2.7"
  array(20) {
    string(4) "dict"
    string(4) "file"
    string(3) "ftp"
    string(4) "ftps"
    string(6) "gopher"
    string(4) "http"
    string(5) "https"
    string(4) "imap"
    string(5) "imaps"
    string(4) "ldap"
    string(5) "ldaps"
    string(4) "pop3"
    string(5) "pop3s"
    string(4) "rtsp"
    string(3) "scp"
    string(4) "sftp"
    string(4) "smtp"
    string(5) "smtps"
    string(6) "telnet"
    string(4) "tftp"
 [2019-11-30 17:10 UTC] gilperon at gmail dot com
I just forgot to say that when I open my Centos terminal and execute the command below, everything works fine:


So, using curl directly from the terminal, works fine. Only using it with PHP is that gets buggy.
 [2019-11-30 17:14 UTC] gilperon at gmail dot com
One more note: using "echo curl_error($curl); " shows a blank string! So curl is not showing any error.
 [2019-12-01 12:25 UTC]
It's pretty weird that curl_error() doesn't report anything here. Just to double check, if you replace the "echo curl_exec($curl)" with "var_dump(curl_exec($curl))", do you get "bool(false)" or "string(0)"? And afterwards, does "var_dump(curl_errno($curl))" give "int(0)" as well?
 [2019-12-01 14:17 UTC] gilperon at gmail dot com I just woke up right now and went to try your code and suddenly this bug went away. I didnt make ANY update yesterday. I didnt do "yum update" and for some reason CURL came back to work!

Then I tried adding the line of code - mysqli_connect("localhost","root","password") - above the CURL and then it crashed  again. Which means that the bug that I reported a few days back came back to happen again.

So now, CURL only does not work when opening the mysqli connection.

Nikik I tried that 2 line of codes you asked me and the output follows below:



$conn = mysqli_connect("localhost","root","password");

$curl = curl_init();

$opts = array();

$opts[CURLOPT_URL] = "";








I investigated, and 77 means -> CURLE_SSL_CACERT_BADFILE.

ALSO one even strange thing, if I replace 

$conn = mysqli_connect("localhost","root","password"); 

with just


The bug goes away and everything works! 

Hope this helps and if you want me to execute any other code, I am here to help!
 [2019-12-02 02:30 UTC] gilperon at gmail dot com
One more thing, I tried using the CART file from and it also does show the same exactly error, so I am pretty cure there is no problem with cacert or certificate bundle.
 [2019-12-02 02:43 UTC]
-Status: Feedback +Status: Duplicate
 [2019-12-02 02:43 UTC]
If your original code, the one where you do *not* do anything over an SSL connection before using cURL, is no longer causing any problems then we're back to this being a duplicate of the other report.
 [2019-12-02 12:29 UTC] gilperon at gmail dot com you are right. This bug now only happens when opening a mysqli connection previously to using CURL with HTTPS. I have no idea how this bug "fixed" itself cause I could easily reproduce it on a fresh install of centos + lamp on Linode (cloud server company) and I didnt any "yum update" after the install. Have no idea how it got fixed HOWEVER the bug still happens when opening a mysqli connection previsouly to using CURL with HTTPS.
 [2019-12-04 09:23 UTC]
This is pretty weird, because your curl is linked against NSS (first time I'm seeing that particular combination...), while mysql will use OpenSSL. Assuming it's using mysqlnd.

I don't really have a good idea on how to debug this (short of making this reproducible in something like Docker) ... possibly running PHP under "strace" and taking a look at the log would give some insight into where the failure originates.
 [2019-12-04 09:25 UTC]
To clarify, running under strace should be as simple as "strace php script.php".

(Copying this comment from bug #78845, I mixed up the tabs.)
 [2019-12-04 14:33 UTC] gilperon at gmail dot com
Sorry I dont know how to use strace :( But isnt anyone of you able to reproduce this on a clean cloud server install with LAMP?
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Mon May 29 03:03:42 2023 UTC