FlareSolverr: [yggtorrent] (testing) Exception: System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.
Environment
- FlareSolverr version: 2.2.10
- Last working FlareSolverr version: unsure, couple of days ago
- Operating system: Debian 11
- Are you using Docker: no
- FlareSolverr User-Agent (see log traces or / endpoint):
- Are you using a proxy or VPN?: no
- Are you using Captcha Solver: [yes/no]
- If using captcha solver, which one:
- URL to test this issue:
Description
[List steps to reproduce the error and details on what happens and what you expected to happen]
Logged Error Messages
Jackett.Common.IndexerException: Exception (yggtorrent): Exception: System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 55 seconds elapsing.
---> System.TimeoutException: The operation was canceled.
---> System.Threading.Tasks.TaskCanceledException: The operation was canceled.
---> System.IO.IOException: Unable to read data from the transport connection: Operation canceled.
---> System.Net.Sockets.SocketException (125): Operation canceled
--- End of inner exception stack trace ---
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
at FlareSolverrSharp.Solvers.FlareSolverr.<>c__DisplayClass10_0.<<SendFlareSolverrRequest>b__0>d.MoveNext()
---> FlareSolverrSharp.Exceptions.FlareSolverrException: Exception: System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 55 seconds elapsing.
---> System.TimeoutException: The operation was canceled.
---> System.Threading.Tasks.TaskCanceledException: The operation was canceled.
---> System.IO.IOException: Unable to read data from the transport connection: Operation canceled.
---> System.Net.Sockets.SocketException (125): Operation canceled
--- End of inner exception stack trace ---
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
at FlareSolverrSharp.Solvers.FlareSolverr.<>c__DisplayClass10_0.<<SendFlareSolverrRequest>b__0>d.MoveNext()
at FlareSolverrSharp.Solvers.FlareSolverr.<>c__DisplayClass10_0.<<SendFlareSolverrRequest>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at FlareSolverrSharp.Utilities.SemaphoreLocker.LockAsync[T](Func`1 worker)
at FlareSolverrSharp.Solvers.FlareSolverr.SendFlareSolverrRequest(HttpContent flareSolverrRequest)
at FlareSolverrSharp.Solvers.FlareSolverr.Solve(HttpRequestMessage request, String sessionId)
at FlareSolverrSharp.ClearanceHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
at Jackett.Common.Utils.Clients.HttpWebClient2.Run(WebRequest webRequest) in /home/vsts/work/1/s/src/Jackett.Common/Utils/Clients/HttpWebClient2.cs:line 179
at Jackett.Common.Utils.Clients.WebClient.GetResultAsync(WebRequest request) in /home/vsts/work/1/s/src/Jackett.Common/Utils/Clients/WebClient.cs:line 186
at Jackett.Common.Indexers.BaseWebIndexer.RequestWithCookiesAsync(String url, String cookieOverride, RequestType method, String referer, IEnumerable`1 data, Dictionary`2 headers, String rawbody, Nullable`1 emulateBrowser) in /home/vsts/work/1/s/src/Jackett.Common/Indexers/BaseIndexer.cs:line 522
at Jackett.Common.Indexers.CardigannIndexer.PerformQuery(TorznabQuery query) in /home/vsts/work/1/s/src/Jackett.Common/Indexers/CardigannIndexer.cs:line 1414
at Jackett.Common.Indexers.BaseIndexer.ResultsForQuery(TorznabQuery query, Boolean isMetaIndexer) in /home/vsts/work/1/s/src/Jackett.Common/Indexers/BaseIndexer.cs:line 310
--- End of inner exception stack trace ---
at Jackett.Common.Indexers.BaseIndexer.ResultsForQuery(TorznabQuery query, Boolean isMetaIndexer) in /home/vsts/work/1/s/src/Jackett.Common/Indexers/BaseIndexer.cs:line 322
at Jackett.Common.Indexers.BaseWebIndexer.ResultsForQuery(TorznabQuery query, Boolean isMetaIndexer) in /home/vsts/work/1/s/src/Jackett.Common/Indexers/BaseIndexer.cs:line 692
at Jackett.Common.Services.IndexerManagerService.TestIndexer(String name) in /home/vsts/work/1/s/src/Jackett.Common/Services/IndexerManagerService.cs:line 311
at Jackett.Server.Controllers.IndexerApiController.Test() in /home/vsts/work/1/s/src/Jackett.Server/Controllers/IndexerApiController.cs:line 132
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Builder.Extensions.UsePathBaseMiddleware.InvokeCore(HttpContext context, PathString matchedPath, PathString remainingPath)
at Jackett.Server.Middleware.CustomExceptionHandler.Invoke(HttpContext httpContext) in /home/vsts/work/1/s/src/Jackett.Server/Middleware/CustomExceptionHandler.cs:line 26
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 20
- Comments: 105 (14 by maintainers)
On Yggtorrent forum, they say Flaresolverr blocked RSS flux to prevent DDoS attacks, the issue should be solved in a few days.
Released FlareSolverr 3.0.0 and Jackett 0.20.2486 => #650
For me it worked until yesterday, around 6:30pm. Reinstall does nothing, as well as increasing timeout. Sometimes testing with curl works, but very unstable.
Additional to this, I can see that the
cloudflare.tsmention#cf-challenge-runningwhich it seems to be now#challenge-running. I tried with adding it but no luck.– FlareSolverr version: 2.2.10 Last working FlareSolverr version: 2.2.10 Operating system: Debian 11 Are you using Docker: NO FlareSolverr User-Agent (see log traces or / endpoint): N/A Are you using a proxy or VPN?: NO Are you using Captcha Solver: [yes/no] NO If using captcha solver, which one: N/A URL to test this issue: N/A
Any chance to github your fork of v3beta to have it "ready to use " ? I’m not a “rebuild our own docker image” guy TBH …
Well, I managed on my side to make the whole thing work as expected, here are the conditions met on my side:
Flaresolverr logs:
YGGcookie seems not to work for a dedicated server (without UI), as if you login from home and paste cookies in prowlarr on your dedicated cloud server, origin IP will be different. Don’t forget that.
I had the same error as a lot of us here but I was able to resolve it by making the request from a french IP, using FlareSolverr 3.0.0.beta3, and using Prowlarr instead of Jackett. When testing the indexer, Jackett was making 2 requests (for pagination I think.) and the second request would always fail, not sure why… Using Prowlarr has fixed this. Also, I couldn’t make it works with cookies, I had to use credentials in Prowlarr. Hope to help those facing the same issue.
No, flaresolverr are not able to bypass captcha ( https://github.com/FlareSolverr/FlareSolverr#captcha-solvers ) at all. IAUA have different kind of challenge : ( https://developers.cloudflare.com/fundamentals/get-started/concepts/cloudflare-challenges/#managed-challenge-recommended ) depending the IP you come from. If you’re on dedicated server IP or under VPN IP, you have 100% chance to be prompt for captcha. On your ISP IP, it’s could work or not…
That’s why, only thing to do are to wait after ygg, and don’t spend much time for this.
Totally agree for the Ygg issue, but i share the logs because it’s going to an infinite loop
Timeout waiting for selector looptill the final timeout. and so never popup an err likeCaptcha detected but no automatic solver is configuredlike i ad before in the same case ( IAUA ). So could be an issue or err improvement.the last version of FlareSolverr work great for me spécial thank to développer
2023-01-05 10:54:56 INFO FlareSolverr 3.0.0 2023-01-05 10:54:56 INFO Testing web browser installation… 2023-01-05 10:54:57 INFO FlareSolverr User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 2023-01-05 10:54:57 INFO Test successful 2023-01-05 10:54:57 INFO Serving on http://0.0.0.0:8191 2023-01-05 11:07:20 INFO Incoming request => POST /v1 body: {‘maxTimeout’: 55000, ‘cmd’: ‘request.get’, ‘url’: ‘https://www6.yggtorrent.lol/engine/search?category=all&name=&description=&file=&uploader=&sub_category=&do=search&order=desc&sort=publish_date’} 2023-01-05 11:07:21 INFO Challenge detected. Title found: Just a moment… 2023-01-05 11:07:23 INFO Challenge solved! 2023-01-05 11:07:23 INFO Response in 2.996 s 2023-01-05 11:07:23 INFO 172.18.0.3 POST http://flaresolverr:8191/v1 200 OK 2023-01-05 11:07:26 INFO Incoming request => POST /v1 body: {‘maxTimeout’: 55000, ‘cmd’: ‘request.get’, ‘url’: ‘https://www6.yggtorrent.lol/’} 2023-01-05 11:07:27 INFO Challenge detected. Title found: Just a moment… 2023-01-05 11:07:29 INFO Challenge solved! 2023-01-05 11:07:29 INFO Response in 2.7 s 2023-01-05 11:07:29 INFO 172.18.0.3 POST http://flaresolverr:8191/v1 200 OK
FYI with the v3beta, up to date undetected_chromedriver, and a custom User-Agent (in Jackett), I have no more problem with Yggtorrent.
On beta3 with https://www6.yggtorrent.lol/ i’ve this result in jackett 😦 “FlareSolverr was unable to process the request, please check FlareSolverr logs. Message: Unable to solve captcha of type turnstile”
And Logs: 2023-01-03 22:07:19 INFO 172.17.0.1 POST http://localhost:8191/v1 200 OK 2023-01-03 22:08:18 INFO Incoming request => POST /v1 body: {‘maxTimeout’: 60000, ‘cmd’: ‘request.get’, ‘url’: ‘https://www6.yggtorrent.lol/’} 2023-01-03 22:08:25 INFO Challenge detected. Selector found: #challenge-spinner 2023-01-03 22:08:43 INFO Response in 25.179 s 2023-01-03 22:08:43 INFO 172.17.0.1 POST http://localhost:8191/v1 200 OK
Any tips ?
Working well with
ghcr.io/aeonlucid/flaresolverr:v3betafork!Log:
Thanks! @JigSawFr
It’s working for some (like me), but not for others. Once their Cloudflare protection is stepped down (i.e. when people stop DDoSing them), there shouldn’t be any issues.
After enabling
LOG_LEVEL=debugI can see a#trk_jschal_jsloop @ilike2burnthing did you do something special to make it work?Yes, also Cloudflare present random captcha’s depending on their detection algorithm, turnstile captcha seems to be problematic with undetected chrome driver atm https://github.com/ultrafunkamsterdam/undetected-chromedriver/issues/827
The @hcharbonnier idea does not work for me, so it does not work for everyone.
The fork https://github.com/AeonLucid/FlareSolverr already has an up-to-date
undetected_chromedriverand it still does not work:https://github.com/AeonLucid/FlareSolverr/issues/2FlareSolverr upstream v3beta branch even with an up-to-date
undetected_chromedriverdoes not work.Jackett; many have switched to Prowlarr ; and the User-Agent modification is not in Jackett upstream.I’d say we should wait for a reply from @ngosang here and from @AeonLucid there.
how do you manage this precisely ?
I do confirm that my above configuration with the flaresolverr fork provided in this thread is WORKING !
Thanks for the trick !
But it is broken … again 😤
I can confirm that using aeonlucid’s fork solved the issue for me. Thank you very much for sharing! 🎉
It looks like it isn’t working right now for me…
It was random earlier, but now it won’t work anymore
I’m using UnRaid, i have deployed it (ghcr.io/aeonlucid/flaresolverr:v3beta) with the docker run if i did it correctly :
{“msg”: “FlareSolverr is ready!”, “version”: “3.0.0”, “userAgent”: “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36”}
Seems the Flaresolver is working great
But it’s falling on Jackett i still got some error
After few diging, it works !
@MartnIV nice thanks for your comment, this fork has ability to bypass Cloudflare IUAM mode ( I’m Under Attack Mode)
And this is where I disagree with you. Flaresolverr should be able to bypass the
I am under attackmode. Someone said that the Cloudflare page had changed recently and some captcha couldn’t be solved. Maybe it isn’t possible to solve it, but I do think that asking someone who knows about it (the maintainer of this repository) will definitely help, whether it being solving the problem or explaining more clearly what is happening.It’s not a FlareSolverr issue. The YGG mods have said it’s a purposeful, temporary action on their part to protect against DDoS attacks. The only thing that’s going to change that is them dropping said protection. They said this nearly a week ago, nothing has changed, so it would be great if people could stop posting ‘same here’ comments and their own theories.
Here : https://www5.yggtorrent.fi/forum/index.php?threads/probleme-jackett.84346/
(In french, of course)
Same for me, but for yggcookie it Will work for 1 or 2 research, and result in the bug to appear again unless I redo the cookie setting, again and again
I tried to install FlareSolverr 3.0.0.beta3 and put Cloudflare DNS but i still have the issue 😦.
Tested also on FlareSolverr v3beta and it provides me a better view :