New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1337x] (testing) Exception (1337x): The cookies provided by FlareSolverr are not valid: The cookies provided by FlareSolverr are not valid #481
Comments
Yeah something seems to have changed. Flaresolverr thinks it solved the challenge and only returns a |
Having the same issue over here with nhentai.net-- FlareSolverr thinks the challenge is solved, but is returning an invalid solution. |
Same with fanfiction.net |
Cloudflare must have been updated. I'm getting this for 1337, limetorrents, eztv and YTS |
Debug log:
Postman response:
|
a quick fix before the real problem is fixed is to just add a bit of delay (in my case 30s was enough for now):
hope it helps |
In case it helps, this is the output via FanFicFlare in Calibre of trying to access fanfiction.net HTTP Error in FFF '<!DOCTYPE html><html lang="en-US"><head> <script src="/cdn-cgi/challenge-platform/h/b/orchestrate/jsch/v1?ray=7417513b6b7573b7"></script></head>
</body></html>'(503) URL:'https://www.fanfiction.net/s/14114069/1/Legends-Never-Die' |
Sorry, guys, I am kind of a newbie to jackett/sonarr, how can I apply the above solution to my system? |
@ghwjp I think this needs adding into the source code and re-compiling. Those of us using Windows will have to wait for a new version to be compiled. |
How is the testing going - hoping the fix can be implemented soon. |
Still no update? |
I don't this this has been fixed |
Have the same issue unfortunately. I am using Jackett at the moment, I've been fiddling all day, even tried Prowlarr, now I am thinking that this is a FlareResolverr issue. Exception (yts): The cookies provided by FlareSolverr are not valid: The cookies provided by FlareSolverr are not valid |
Bug was already confirmed and the team is working on it. We only can wait. You can quick fix/avoid this problem using unblockninja proxies (to bypass cloudflare challenges), like https://1337x.unblockninja.com . Cheers
Yes, issue is still open in GitHub. |
Let's give the developers some time and appreciate their contribution. :) |
it's can work without FlareSolverr , but test failed and tip me to use .
|
revert all of your changes and replace the file i provided |
credit: @realivanjx #481 (comment)
Sadly still getting the cookie issue - while it tells me And that URL has cloudflare protection, something is happening likely cloudflare updated :@ So, I'm confuddled. Stupid cloudflare.... >.< Side-Note: Ranobes.net worked with flaresolverr perfectly a few days ago I can't see any other place there might be an issue in identifying if cloudflare is running other than FlareSolverr/src/providers/cloudflare.ts Line 31 in a74884d
Which due to response.headers().vary.trim() == 'Accept-Encoding,User-Agent' not matching the actual response header exactly it leads to the else condition which nullifies the previous cf detection via the server identification in the headers.
But, I'm no expert on flaresolverr code.. So could be miles off Edit: Successfully detected and solved, while having 'similiar' response header as ranobe... Nope, no idea... Brain is mush |
Feel free to tinker, test it out, and submit a PR - https://github.com/FlareSolverr/FlareSolverr#from-source-code |
in my case cf is not detected. not showing with a browser too.
|
I'm narrowing in on the issues.... Thus the issue MUST be with FlaresolverrSharp (which I'm gonna assume everyone is using as the bridge, since I can't find the message "The cookies provided by FlareSolverr are not valid: The cookies provided by FlareSolverr are not valid" I've still got a few hours before I got to get sorted for a flight (which will leave me PC-less for a week 0.0), I'll have a look at it and see where the issue is coming from at the least. |
I got a theory, not 100% how to implement the fix to it.... But, the theory is along the lines of - the cloudflare protection is some form of 'unique view' checker, which means it generates a 1 time use cookie... This causes an issue due to flaresolverrsharp doing the process -
Fix
|
Right.... Maybe this works, maybe it doesn't... Worked in testing, but that's not the real world Possible fix => Code
It ain't pretty, but it works (for me) |
Update to FlareSolverr 2.2.8 I just removed the 30 s delay hack, it should solve the challenges faster. |
I am on latest but still having this issue |
Open a new issue, providing the information requested. |
Environment
Description
Flaresolverr seems to think it's solving the challenge but Jackett seems to think the cookies arent valid
Logged Error Messages
(Nothing seems to be going wrong)
2022-08-25T21:07:09+01:00 INFO REQ-9 Incoming request => POST /v1 body: {"maxTimeout":55000,"cmd":"request.get","url":"https://1337x.unblockit.bet/cat/Movies/time/desc/1/"}
2022-08-25T21:07:16+01:00 INFO REQ-9 Cloudflare detected
2022-08-25T21:07:17+01:00 INFO REQ-9 Challenge solved
2022-08-25T21:07:19+01:00 INFO REQ-9 Response in 9.997 s
Screenshots
The text was updated successfully, but these errors were encountered: