-
Notifications
You must be signed in to change notification settings - Fork 660
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
FlareSolverr 3.0.0 released #650
Comments
Hi, thanks for keeping armv7 support. Just confirming this is working well for me on rpi4 (with yggtorrent) |
Working perfectly here, seems faster at solving than previously too. Down from 16+ sec to around 4-5 sec |
@ngosang Thanks a lot! I released To release a version (v3.0.0) that is not a git version, it would be great to add the file Can you publish I was wondering why |
I did a bit of refactoring just now on a local copy to achieve this:
After that I was able to create a simple |
PR with the above refactor has been created at #651 |
FYI Via Prowlarr Still not working for BT4G, Badasstorrents, Cloudtorrents, idope.se, All of these work fine through the newest version of Jackett. Seems as though this may be a Prowlarr issue since flaresolverr logs show it thinks it worked. Prowlarr states BT4G and other trackers are blocked by Cloudflare Protection. 2023-01-05 02:33:07 INFO FlareSolverr 3.0.0 |
It is resolving the challenge in flaresolverr logs 2nd time for hd-space but in jackett it throws error. Flaresolverr logs: 2023-01-05 15:15:29 INFO Incoming request => POST /v1 body: {'maxTimeout': 55000, 'cmd': 'request.get', 'url': 'https://hd-space.org/index.php?page=login'} Jackett logs: 01-06 01:15:36 Error FlareSolverrSharp.Exceptions.FlareSolverrException: The cookies provided by FlareSolverr are not valid |
Changelog: - Add domain to cookies which is required since FlareSolverr 3.0.0 - Add failed asserts to check again response of FlareSolverr response Before the User cookies support mentioned in FlareSolverr/FlareSolverr#650 is implemented in the official repo, the har only works with this docker image: 15cm/flaresolverr:3.0.0 or forward. The docker image is built from https://github.com/15cm/FlareSolverr .
Changelog: - Add domain to cookies which is required since FlareSolverr 3.0.0 - Add failed asserts to check again response of FlareSolverr response Before the User cookies support mentioned in FlareSolverr/FlareSolverr#650 is implemented in the official repo, the har only works with this docker image: 15cm/flaresolverr:3.0.0 or forward. The docker image is built from https://github.com/15cm/FlareSolverr .
Changelog: - Add domain to cookies which is required since FlareSolverr 3.0.0 - Add failed asserts to check again the response of FlareSolverr Before the User cookies support mentioned in FlareSolverr/FlareSolverr#650 is implemented in the official repo, the har only works with this docker image: `15cm/flaresolverr:3.0.0` or onward. The docker image is built from https://github.com/15cm/FlareSolverr . Fix qd-today#225
Changelog: - Add domain to cookies which is required since FlareSolverr 3.0.0 - Add failed asserts to check again the response of FlareSolverr Before the User cookies support mentioned in FlareSolverr/FlareSolverr#650 is implemented in the official repo, the har only works with this docker image: `15cm/flaresolverr:3.0.0` or onward. The docker image is built from https://github.com/15cm/FlareSolverr . Fix qd-today#225
Changelog: - Add domain to cookies which is required since FlareSolverr 3.0.0 - Add failed asserts to check again the response of FlareSolverr Before the User cookies support mentioned in FlareSolverr/FlareSolverr#650 is implemented in the official repo, the har only works with this docker image: `15cm/flaresolverr:3.0.0` or onward. The docker image is built from https://github.com/15cm/FlareSolverr . Fix qd-today#225
It solves fanfiction.net now... occasionaly. At times it gives:
|
Also, it seems like the flaresovler output now displays japanese symbols as \uXXXX, any way it can be changed? |
But anyway: big big thanks for this version. My project is alive again now :) It's a completely "free time free service" thing so I wouldn't have been able to continue without people providing the parsing access, I am very grateful for your work |
* Update m-team FlareSolverr har Changelog: - Add domain to cookies which is required since FlareSolverr 3.0.0 - Add failed asserts to check again the response of FlareSolverr Before the User cookies support mentioned in FlareSolverr/FlareSolverr#650 is implemented in the official repo, the har only works with this docker image: `15cm/flaresolverr:3.0.0` or onward. The docker image is built from https://github.com/15cm/FlareSolverr . Fix #225 * Add everything before </title> of FlareSolverr response to har __log__ The FlareSolverr response status is before the response body that contains "</title>". If the user name can be found in the title, it means the login succeeded. The __log__ looks like this: {"status": "ok", "message": "Challenge not detected!", "solution": {"url": "https://kp.m-team.cc/userdetails.php?id=<userid>", "status": 200, "captcha_type": null, "cookies": [{"domain": "kp.m-team.cc", "httpOnly": false, "name": "tp", "path": "/", "secure": false, "value": "<tp_cookie>"}], "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36", "headers": {}, "response": "<html xmlns=\"http://www.w3.org/1999/xhtml\"><head>\n<meta http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\">\n<meta name=\"generator\" content=\"NexusPHP\">\n<title>M-Team - TP :: \u7528\u6236\u8a73\u60c5 - <username> - Powered by NexusPHP</title>
|
@HLFH how did you manage to make it work ? This is what I get on v3.0.2
|
I have the same thing as @Thomas-Philippot.
|
@Zegorax are you using a VPS or something ? I get the error on a debian VPS. Works like a charm on my local network using a raspberry pi |
It's running on Hetzner's network, I'm quite sur that it is the problem. In the past I simply connected to YggTorrent using a remote desktop also running there and it would solve the problem. But now, since a few days, it's not working anymore. |
Hello |
If you're using Jackett/Prowlarr and FlareSolverr on the same device and the same IP (i.e. no VPN or proxy), with IPv6 disabled, and other indexers which require FlareSolverr are working (TorrentQQ is a quick test), then the issue lies with YGG. There are plenty of old issues regarding YGG, and they almost all come down to the same thing: their implementation of Cloudflare IAUM protection as a result of them being DDoS'd. There's nothing we can do about that. |
Can't make it works too on Hetzner, tried on a local server and it's finally working! (Also, Flaresolverr is broken on RaspberryPi 3) |
Idope seems broken, with Jackett v0.20.3269.
|
The request always has the following problem { |
Proxy and Cookies support implemented in https://github.com/FlareSolverr/FlareSolverr/releases/tag/v3.2.0 |
I just released:
With those versions you will be able to bypass Cloudflare (all challenges without CAPTCHA). Tested with YGG and many other sites.
There are some breaking changes in FlareSolverr v3. If you are a developer check out the release notes. If you are installing FlareSolverr from source code, review the readme.
Missing features could be implemented in the future by me or by other contributors. PRs will be accepted.
Thanks @ilike2burnthing @garfield69 for the hard work.
Thanks @AeonLucid for give me some ideas.
The text was updated successfully, but these errors were encountered: