jaymoulin
commented
4 years ago You're using a deprecated version of cloudflare-bypass as you're using an old deprecated version (3.3.0). As @KyranRana is currently not using a stable tag release process (cf #157 ), the only possible way for you to use the actual latest with composer is to depend on jaymoulin/cloudflare-bypass instead of kyranrana/cloudflare-bypass. Another possible way is to download the actual master branch and paste all the codebase in your vendor folder. (cf https://github.com/KyranRana/cloudflare-bypass/issues/164#issuecomment-599148216)
Once again, I'm not happy with this (hopfully temporary) solution but this is the only way I found to unstuck this situation.
nitemare
momala454
KyranRana
I'm still getting errors that have been reported in issues that were closed. I am using the latest commit available. I have installed with composer, as well as downloaded the zip and copied the files over the composer-version files.
Issue Depending only on the HTTP Headers used, I am getting one of 2 errors, and I cannot successfully retrieve the site. Those errors are:
or
See below for full output and setup
Scenario 1
To test this out, I have been using the CFCurlTest.php example. (see details below for example code)
require "{Home Path}/libraries/vendor/autoload.php"; use CloudflareBypass\CFCurlImpl; use CloudflareBypass\Model\UAMOptions; $url = "https://torrentz2.eu/"; $ch = curl_init($url); // Want to cache clearance cookies ? curl_setopt($ch, CURLOPT_COOKIEJAR, "cookies.txt"); curl_setopt($ch, CURLOPT_COOKIEFILE, "cookies.txt"); curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLINFO_HEADER_OUT, true); curl_setopt($ch, CURLOPT_HTTPHEADER, array( "Upgrade-Insecure-Requests: 1", "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36", "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3", "Accept-Language: en-US,en;q=0.9" $cfCurl = new CFCurlImpl(); $cfOptions = new UAMOptions(); $cfOptions->setVerbose(true); // $cfOptions->setDelay(5); try { $page = $cfCurl->exec($ch, $cfOptions); // Want to get clearance cookies ? $cookies = curl_getinfo($ch, CURLINFO_COOKIELIST); } catch (ErrorException $ex) { echo "Unknown error -> " . $ex->getMessage(); }If I use it as-is, only changing the url to:
and using the existing headers (see below details)
curl_setopt($ch, CURLOPT_HTTPHEADER, array( "Upgrade-Insecure-Requests: 1", "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36", "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3", "Accept-Language: en-US,en;q=0.9" ));Results of Scenario 1 This will return NULL for $page and the Verbose error is:
See details below for Verbose Output
Scenario 2
I attempted to troubleshoot myself, making sure i had all the headers it asks for, and copied the user-agent i had working on v2, It no longer says its not supported, but it appears the clearance cookie never gets received. Once again using the CFCurlTest.php example:
Again, changing the url to:
and using the my updated headers (see below details)
curl_setopt($ch, CURLOPT_HTTPHEADER, array( 'Connection: Keep-Alive', 'Accept-Language: *', 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0', 'Accept: */*', 'Accept-Encoding: deflate, gzip', 'Upgrade-Insecure-Requests: 1' ));Results of Scenario 2 This too will return NULL for $page. Occasionally i have gotten the cloudflare challange page, but mostly its NULL. This is the Verbose Error:
See details below for Verbose Output
Additional information you deem important (e.g. issue happens only occasionally): This issue has been posted before, to which either it goes ignored, or someone replies "that site works for me" and the issue is ignored or assumed fixed.
I understand it may be a setup issue, rather than a bug, but i'm using the stock example, so something isn't as it should be
Version you are using (you may find this information in your
composer.lockfile)Note: I've updated fully with composer and those files show as modified in September, 2019, I tested both scenarios, and got the above results. I then downloaded the latest commit zip file, with files updated today, and copied those overtop, tested both scenarios again
PHP Version you are using