Skip to content
This repository has been archived by the owner on Mar 27, 2020. It is now read-only.

Sometimes could not resolve challenge? (even it's not captcha) #30

Open
gmareater opened this issue Apr 2, 2018 · 21 comments
Open

Sometimes could not resolve challenge? (even it's not captcha) #30

gmareater opened this issue Apr 2, 2018 · 21 comments
Assignees

Comments

@gmareater
Copy link

hi
it's just more question than issue:
why sometimes could not resolve challenge?
challenge is not captcha

thanx for your answer

@elcattivo
Copy link
Owner

What website are you trying to access? Does the problem occur just on one particular website or on other websites, too?

@elcattivo elcattivo self-assigned this Apr 3, 2018
@kaso17
Copy link

kaso17 commented Apr 4, 2018

I can confirm this behavior.
Since a few weeks we're seeing more "Clearance failed after 4 attempts" exceptions.

Increasing the timeout doesn't fix it.

Example websites:
https://torrentz2.eu/
https://www.torrentleech.org/
https://www.xspeeds.eu/

Sometimes it still works. It feels like they changed something to the algorithm but didn't roll it out to all servers yet. Didn't spend any time debugging it yet.

@marrrcin
Copy link

marrrcin commented Apr 4, 2018

+1

There were definitely more failed attempts since a few days

@gmareater
Copy link
Author

In my tests, It seems its related to useragent
With default useragent, always resolve in first try, but with different and common used useragent, it fails so many times, untill resolve

@kaso17
Copy link

kaso17 commented Apr 4, 2018

@elcattivo
Here's a diff of a failed (left) and correct (right) challenge:
https://www.diffchecker.com/YihuA5nm
I didn't dig deeper into the solver yet to understand what might be the issue.
The "long" ones seem to fail.

@elcattivo elcattivo added the bug label Apr 4, 2018
@kaso17
Copy link

kaso17 commented Apr 4, 2018

ok, looked into this a little deeper.
The new challenges may return floating point answers instead of int. Easy to detected based on the source (toFixed() vs parseInt()).

My quick "if page contains toFixed, ignore current and get next challenge" worked but that's obviously not a good solution.

@elcattivo
Copy link
Owner

Thanks for your feedback.

@kaso17
Copy link

kaso17 commented Apr 4, 2018

I also noticed that normal int challenges are correctly solved but I'm getting a new challenge anyway.
Not sure if that's due to me ignoring the float challenges or happening due to something else.

@ByronAP
Copy link

ByronAP commented Apr 5, 2018

damn cloudflare crap :-(

@elcattivo
Copy link
Owner

I have added support for this new kind of challenge in 22fbc0c. Version 1.2.0 is already published on NuGet.

@gmareater
Copy link
Author

Thanx For your Support
just another thing, In ClearanceHandler File, could you Make "_cookies" public
or add a method to return it,
So I could be able to use it with "HttpWebRequest"
let me know, thanx

@kaso17
Copy link

kaso17 commented Apr 6, 2018

@elcattivo thank you for the quick fix.
@gmareater the clearance cookies should be included in the results (Set Cookie headers).

@elcattivo
Copy link
Owner

Although the calculated answer seems to be correct, I still get a lot of 403 errors when accessing the clearance page. Maybe something else has changed, too.

@kaso17
Copy link

kaso17 commented Apr 7, 2018

I didn't debug it yet, but the original javascript is using toFixed at the end of the calculation.
the c# implementation rounds but uses a normal toString at the end.
For some results that might be resulting in less than 10 decimal digits compared to the toFixed solution which always will result in exactly 10 digits.
Not sure if the missing 0 decimal digits will cause a failed challenge.

@Turokpd
Copy link

Turokpd commented Apr 13, 2018

first of all, thx for great solution. Are you looking into the latest changes? Looks like I am getting success only after 10th try. Also, any chance adding proxy support?

@elcattivo
Copy link
Owner

Sorry, still had no time to investigate this issue further.

@Turokpd proxy support (while sending the challenge solution) is a good idea.

@grandsilence
Copy link
Contributor

#32 I've found some extra info

@eMi-
Copy link

eMi- commented May 1, 2018

I just started using CloudFlareUtilities today and run into this issue.
I am testing on following site: https://tennis.wettpoint.com/spielergebnisse/2011.html
Hope it gets fixed soon...
@grandsilence I downloaded the source and implemented the second and third foundouts but I still run in the same issue "Clearance failed after 4 attempt(s)".

@grandsilence
Copy link
Contributor

grandsilence commented May 1, 2018

@eMi- It has force recaptcha validation. The project solving only JS Challange. You can implement one of the services (AntiCaptcha, AntiGate) for solving it. Yep, It's paid - ~2$ for 1k solutions.

default

@eMi-
Copy link

eMi- commented May 1, 2018

@grandsilence I am not totally sure what you mean and how you found out that this site has force recaptcha validation, but it works now (very slowly) when increasing the max default retries value for the clearance attempts from 3 to 100. But this is not a solution.

@grandsilence
Copy link
Contributor

@eMi- I don't know. I'm using my own HTTP library with some parts of CloudFlareUtilities. https://github.com/csharp-leaf (Called Leaf.Net). Works fine for me.

@elcattivo elcattivo reopened this May 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants