-
Notifications
You must be signed in to change notification settings - Fork 139
Solver not working anymore #65
Comments
@Ekliptor hey, thanks for reporting this. I will take a look asap and will come up with a fix. |
@Ekliptor which url are you trying to open? |
I get these new challenges as posted above on every domain that is set to "Under attack mode" in Cloudflare. To demonstrate i just set cashtippr.com to show this challenge. Also when accessing it with a GET request using cloudscraper from a German IP I still get through (past the challenge) about 80% of the time. Either way it's still working, but far from 100% since their challenge changed. Or maybe CF got more restrictive with my IPs. Sorry for not having investigated this further yet. |
@Ekliptor thanks for the details, but I still don't quite understand what has happened and changed. CF has 2 pages which cloudscraper tries to bypass: The code snippet you provided in the issue is with a js challenge, but you are mentioning the line of code I was able to access |
Hello, The issue seams to be that after getting a challenge, CF sometimes brings a second challenge, so the scraper needs to be executed in a look until it makes it through. just my 2 cents David X. |
@DavidXanatos @Ekliptor I'm struggling to repro such a scenario. I would appreciate if you could provide me with a link that has multiple challenges, or ideally a source code of each page in the chain of CF responses, so I can write a test case and fix the library. |
an example would be: h++p://iload.to/l/1786935/9Qga10zgWZ |
@DavidXanatos I only get one CF challenge and then 404 page |
try tomorow thay seam to have soem issues since a few hours, |
Also I was able to reproduce this using Google Chrome. It submitted the cloudflare challenge and then came another challenge right after. Only on the 3rd reload did I get to see the actual iload.to page. |
@DavidXanatos @Ekliptor i have managed to repro it and get 2 challenges in a row. Here is a new branch in which i'm gonna refactor the library and soon will create a PR. |
@DavidXanatos @Ekliptor @Royalgamer06 hey folks, I have just published a WIP PR which fixes this issue, e.g. properly processes any consequent challenges #66 Please give it a try and let me know if that works for you. You can use a npm package from a branch with something like this. I still want to do some minor adjustments there before releasing. Thanks. |
Hi,
previously the CF challenge was extracted with the following function:
var challenge = body.match(/S='([^']+)'/);
Now they made that variable random and added a random-name property on it for the challenge. Full example:
In the above example the challenge comes from the variable
var bUNLJBB.xqYrWXXfBO
which returns a number. But as mentioned, the variable name is randomI can see this is possible to extract, but requires a lot more work. Has anybody been working on this already?
edit. I can see the extraction of the HTML form variables still works, and I do get past the CF challenge in some cases. However in some cases it fails, presumably due to the JavaScript above.
The text was updated successfully, but these errors were encountered: