October 15, 20241 yr An error occurred while testing this indexer Exception (torrentleech): FlareSolverr was unable to process the request, please check FlareSolverr logs. Message: Error: Error solving the challenge. Timeout after 55.0 seconds.: FlareSolverr was unable to process the request, please check FlareSolverr logs. Message: Error: Error solving the challenge. Timeout after 55.0 seconds.
October 17, 20241 yr Author 20 minutes ago, ramjam824 said: @binhex Are you able to assist here? I will see if i get some time in the next couple of days to take a look at this, super busy right now.
October 18, 20241 yr Author Hi guys, i managed to get an hour to myself to have a stab at this, so i was using the compiled version of flaresolverr but i cannot patch it, so i switched to pulling from source and installing the python packages and then finally applying the patched file, however there is another showstopper bug which means i cannot use this either until another PR is merged, here are the gory details:- The issue:- https://github.com/FlareSolverr/FlareSolverr/issues/1119 possible fix (PR):- https://github.com/FlareSolverr/FlareSolverr/pull/1163 And as you can see the PR above makes alterations to the flaresolverr_service.py file, so whether this includes the PR you guys want incorporating or not i cannot say, most probably not, all in all its in a very broken state and will require the flaresolverr dev's (not me) to carefully merge in the PR's one at a time, until that's done it's a waiting game.
October 18, 20241 yr I've been using binhex-flaresolverr for quite a while and I've had the problem of /v1 500 internal server error, and I also get this error when i use the regular flaresolverr. I have also read through the form and I haven't been able to fix it with everything that someone has given me.
October 24, 20241 yr On 3/5/2024 at 6:31 AM, binhex said: are you sharing networkkng with another container, for example vpn container? if you are and you are using one of my images then you will need to define the port in/out (depeds on setup). @IMACRAB did you solve that issue of the webUI showing error: "Method not allowed." status_code: 405? @binhex My FlareSolverr API URL inside of jackett: http://192.168.0.9:8191/ Thanks docker run -d --name='binhex-flaresolverr' -e TZ="Australia/Brisbane" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Delaware" -e HOST_CONTAINERNAME="binhex-flaresolverr" -e 'SHARED_NETWORK'='no' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8191]/v1' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/flaresolverr-icon.png' -v '/mnt/user/appdata/binhex-flaresolverr':'/config':'rw' -v 'binhex-shared':'/shared':'rw' --net=container:binhex-qbittorrentvpn 'binhex/arch-flaresolverr' f9f7b384700ce2814b194a54f947e63ffca50a5474ba3b955b922b5fb82ac201 docker run -d --name='binhex-jackett' -e TZ="Australia/Brisbane" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Delaware" -e HOST_CONTAINERNAME="binhex-jackett" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100 ' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9117]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/jackett-icon.png' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-jackett':'/config':'rw' --net=container:binhex-qbittorrentvpn 'binhex/arch-jackett' 12518b4916c7ceedbe58eaf73ad7964aa42d6fb1915203d1438e54c93852e9c4 I’m getting this error inside of jackett An error occurred while testing this indexer Exception (torrentleech): Exception: System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 60 seconds elapsing. ---> System.TimeoutException: A task was canceled. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled. at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(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__DisplayClass12_0.<<SendFlareSolverrRequest>b__0>d.MoveNext(): Exception: System.Threading.Tasks.TaskCanceledException: The r Edited October 24, 20241 yr by CafeNevosa Update
October 24, 20241 yr Author 9 hours ago, CafeNevosa said: did you solve that issue of the webUI showing error: "Method not allowed." status_code: 405? On 10/18/2024 at 4:11 PM, Toastypaws said: I've been using binhex-flaresolverr for quite a while and I've had the problem of /v1 500 internal server error Just to be crystal clear here, Flaresolverr is currently in a broken state, until the Flaresolverr dev's (not me) merge in the PR's mentioned here this is dead in the water.
November 13, 20241 yr Thanks for looking into this. I've been wrecking my head around this for a while, glad I'm not the only one with the issue.
December 3, 20241 yr There seems to be some other projects that might be working? Has there been any word from the devs or are they ghosts at this point? Edited December 3, 20241 yr by MightyRufo
December 13, 20241 yr Went to setup flaresolverr for prowlarr. Received this error and log section. Seems like a straight forward install. Double checked everything input correctly. Removed and reinstalled. The rest of the 'arr' suite is up and running great, just having issues here. Any ideas? 2024-12-13 14:30:57.7|Warn|ProwlarrErrorPipeline|Invalid request Validation failed: -- Host: Unable to connect to proxy: HTTP request failed: [503:ServiceUnavailable] [POST] at [http://192.168.1.64:8191/v1]. Check the log surrounding this error for details 2024-12-13 14:30:57.7|Debug|Api|[POST] /api/v1/indexerProxy/test: 400.BadRequest (30116 ms) 2024-12-13 14:31:04.0|Debug|Prowlarr.Http.Authentication.ApiKeyAuthenticationHandler|AuthenticationScheme: API was successfully authenticated. 2024-12-13 14:31:04.0|Debug|FlareSolverr|Cloudflare Detected, Applying FlareSolverr Proxy FlareSolverr to request https://prowlarr.servarr.com/v1/ping 2024-12-13 14:31:34.0|Warn|HttpClient|HTTP Error - Res: HTTP/1.1 [POST] http://192.168.1.64:8191/v1: 503.ServiceUnavailable (6571 bytes) 2024-12-13 14:31:34.0|Error|FlareSolverr|Proxy validation failed [v1.27.0.4852] NzbDrone.Common.Http.HttpException: HTTP request failed: [503:ServiceUnavailable] [POST] at [http://192.168.1.64:8191/v1] at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 128 at NzbDrone.Common.Http.HttpClient.Execute(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 137 at NzbDrone.Core.IndexerProxies.FlareSolverr.FlareSolverr.Test() in ./Prowlarr.Core/IndexerProxies/FlareSolverr/FlareSolverr.cs:line 189 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> Flaresolver logs show this. 2024-12-13 14:28:38,025 DEBG 'flaresolverr' stdout output: 2024-12-13 14:28:38 INFO Test successful! 2024-12-13 14:28:38,030 DEBG 'flaresolverr' stdout output: 2024-12-13 14:28:38 INFO Serving on http://0.0.0.0:8191
December 14, 20241 yr Author On 12/13/2024 at 8:45 PM, WubbaLubbaDubDub said: just having issues here. Any ideas? https://forums.unraid.net/topic/155853-support-binhex-flaresolverr/page/2/#findComment-1478510
February 2, 20251 yr Having an issues with all my indexers (torrents) and Flaresolverr. Any ideas what to do? Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. Connection refused (127.0.0.1:8080)
March 11, 20251 yr did flaresolverr die overnight for anyone else? Not sure if it's a cloudflare update or more indexers are using it or what. for example: 2025-03-11 14:46:52.6|Warn|HttpClient|HTTP Error - Res: HTTP/1.1 [POST] http://10.0.0.186:8191/v1: 500.InternalServerError (182 bytes) {"status": "error", "message": "Error: Error solving the challenge. Timeout after 60.0 seconds.", "startTimestamp": 1741718751891, "endTimestamp": 1741718812651, "version": "3.3.21"} Edited March 11, 20251 yr by acosmichippo
March 14, 20251 yr Same issue. Cannot add tracker in prowlarr with flaresolverr. 2025-03-14 04:48:14 INFO Challenge detected. Title found: Just a moment... 2025-03-14 04:49:14 ERROR Error: Error solving the challenge. Timeout after 60.0 seconds. 2025-03-14 04:49:14 INFO Response in 60.862 s 2025-03-14 04:49:14 INFO 172.18.0.1 POST http://10.10.10.2:8191/v1 500 Internal Server Error 2025-03-14 04:49:16 INFO Incoming request => POST /v1 body: {'maxTimeout': 60000, 'cmd': 'request.get', 'url': 'https://ext.to/browse/?sort=age&order=desc&age=0&with_adult=1', 'proxy': {}} 2025-03-14 04:49:17 INFO Challenge detected. Title found: Just a moment... 2025-03-14 04:50:17 ERROR Error: Error solving the challenge. Timeout after 60.0 seconds. 2025-03-14 04:50:17 INFO Response in 60.806 s 2025-03-14 04:50:17 INFO 172.18.0.1 POST http://10.10.10.2:8191/v1 500 Internal Server Error 2025-03-14 04:50:24 INFO Incoming request => POST /v1 body: {'maxTimeout': 60000, 'cmd': 'request.get', 'url': 'https://ext.to/browse/?sort=age&order=desc&age=0&with_adult=1', 'proxy': {}} 2025-03-14 04:50:25 INFO Challenge detected. Title found: Just a moment... 2025-03-14 04:51:25 ERROR Error: Error solving the challenge. Timeout after 60.0 seconds. 2025-03-14 04:51:25 INFO Response in 60.781 s Edited March 14, 20251 yr by z0ki
March 14, 20251 yr Author On 3/11/2025 at 6:56 PM, acosmichippo said: did flaresolverr die overnight for anyone else? Not sure if it's a cloudflare update or more indexers are using it or what. for example: 4 hours ago, z0ki said: Same issue. Cannot add tracker in prowlarr with flaresolverr. See here:- https://forums.unraid.net/topic/155853-support-binhex-flaresolverr/page/2/#findComment-1478510
May 4, 20251 yr I have had the following setup for a very long time: Binhex qBittorrentVPN FlareSolverr routed via the qBittorrentVPN docker network Prowlarr also routed via the same qBittorrentVPN docker network I noticed that a certain site that requires FloreSolverr has not been working for me for about 2 weeks. I tried to find out what is the reason and it seems that routing the FlareSolverr via qBittorrentVPN somehow causes long delays in the network traffic. Please see the log below: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2025-05-04 18:51:05.045428 [info] Host is running unRAID 2025-05-04 18:51:05.064141 [info] System information: Linux 117540cbac2e 6.6.78-Unraid #2 SMP PREEMPT_DYNAMIC Thu Feb 20 13:33:15 PST 2025 x86_64 GNU/Linux 2025-05-04 18:51:05.083563 [info] Image tags: BASE_RELEASE_TAG=2024100402,IMAGE_RELEASE_TAG=3.3.21-2-01 2025-05-04 18:51:05.105010 [info] PUID defined as '99' 2025-05-04 18:51:05.200986 [info] PGID defined as '100' 2025-05-04 18:51:05.244856 [info] UMASK defined as '000' 2025-05-04 18:51:05.264793 [info] Permissions already set for '/config' 2025-05-04 18:51:05.286551 [info] Deleting files in /tmp (non recursive)... 2025-05-04 18:51:05.365048 [info] SHARED_NETWORK defined as 'yes' 2025-05-04 18:51:05.384325 [info] Starting Supervisor... 2025-05-04 18:51:05,549 INFO Included extra file "/etc/supervisor/conf.d/flaresolverr.conf" during parsing 2025-05-04 18:51:05,549 INFO Set uid to user 0 succeeded 2025-05-04 18:51:05,551 INFO supervisord started with pid 7 2025-05-04 18:51:06,553 INFO spawned: 'flaresolverr' with pid 62 2025-05-04 18:51:06,553 INFO reaped unknown pid 8 (exit status 0) 2025-05-04 18:51:06,818 DEBG 'flaresolverr' stdout output: 2025-05-04 18:51:06 INFO FlareSolverr 3.3.21 2025-05-04 18:51:06 INFO Testing web browser installation... 2025-05-04 18:51:06,818 DEBG 'flaresolverr' stdout output: 2025-05-04 18:51:06 INFO Platform: Linux-6.6.78-Unraid-x86_64-with-glibc2.40 2025-05-04 18:51:06,819 DEBG 'flaresolverr' stdout output: 2025-05-04 18:51:06 INFO Chrome / Chromium path: /opt/flaresolverr/chrome/chrome 2025-05-04 18:51:06,945 DEBG 'flaresolverr' stdout output: 2025-05-04 18:51:06 INFO Chrome / Chromium major version: 123 2025-05-04 18:51:06 INFO Launching web browser... 2025-05-04 18:51:07,945 INFO success: flaresolverr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-05-04 18:55:44,020 DEBG 'flaresolverr' stdout output: 2025-05-04 18:55:44 INFO FlareSolverr User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36 2025-05-04 18:55:44 INFO Test successful! 2025-05-04 18:55:44,026 DEBG 'flaresolverr' stdout output: 2025-05-04 18:55:44 INFO Serving on http://0.0.0.0:8191 2025-05-04 19:01:53,725 DEBG 'flaresolverr' stdout output: 2025-05-04 19:01:53 INFO Incoming request => POST /v1 body: {'maxTimeout': 60000, 'cmd': 'request.get', 'url': 'https://prowlarr.servarr.com/v1/ping', 'proxy': {}} 2025-05-04 19:04:18,690 DEBG 'flaresolverr' stdout output: 2025-05-04 19:04:18 INFO Challenge not detected! 2025-05-04 19:06:35,285 DEBG 'flaresolverr' stdout output: 2025-05-04 19:06:35 INFO Response in 281.559 s 2025-05-04 19:06:35,285 DEBG 'flaresolverr' stdout output: 2025-05-04 19:06:35 INFO 127.0.0.1 POST http://localhost:8191/v1 200 OK As one can see it takes about 4.5 minutes to perform the test when FlareSolverr is started. Additionally, it takes almost 2.5 minutes when I try to create the FlareSolverr indexer proxy in Prowlarr. It fails in Prowlarr as the timeout limit is not met. I am aware that FlareSolverr is not working anymore for most of the users but this is different as also the startup test takes so much time. Additionally, this has worked for me until this strange behaviour started and I have not updated FlareSolverr for at least 6 months. If I change the network to bridge the startup test is passed instantly. So, it seems that something has changed how qBitTorrentVPN or Unraid handles the traffic routed via the qBittorrentVPN docker. Has anybody else faced anything like this? How could this be fixed? Thank you!
May 30, 20251 yr I am getting a similar error now with how flaresolverr essentially keeps just looping back and forth, timing out in solving the challenge and wanted to ask if there are other options or recommendations to replace this, and if there is a good place to look for these in the future.
May 30, 20251 yr Author 5 hours ago, zan335 said:I am getting a similar error now with how flaresolverr essentially keeps just looping back and forth, timing out in solving the challenge and wanted to ask if there are other options or recommendations to replace this, and if there is a good place to look for these in the future.there is an alternative and its mostly working for me, i am seeing tracebacks (uncaught exceptions) so it's def not a polished application yet but it might be worth a go, i have created an template for it and it can be seen on CA, its called 'binhex-official-byparr', this is a template for the official docker image, so any issues should be reported to the developer of the image (see support link).
May 30, 20251 yr 8 hours ago, binhex said:there is an alternative and its mostly working for me, i am seeing tracebacks (uncaught exceptions) so it's def not a polished application yet but it might be worth a go, i have created an template for it and it can be seen on CA, its called 'binhex-official-byparr', this is a template for the official docker image, so any issues should be reported to the developer of the image (see support link).Ahh I see, appreciate the help, ty!
June 2, 20251 yr On 5/30/2025 at 3:19 AM, binhex said:there is an alternative and its mostly working for me, i am seeing tracebacks (uncaught exceptions) so it's def not a polished application yet but it might be worth a go, i have created an template for it and it can be seen on CA, its called 'binhex-official-byparr', this is a template for the official docker image, so any issues should be reported to the developer of the image (see support link).What are you using as Proxy? or am I missing something?
June 2, 20251 yr On 5/30/2025 at 9:19 AM, binhex said:there is an alternative and its mostly working for me, i am seeing tracebacks (uncaught exceptions) so it's def not a polished application yet but it might be worth a go, i have created an template for it and it can be seen on CA, its called 'binhex-official-byparr', this is a template for the official docker image, so any issues should be reported to the developer of the image (see support link).Thank you for taking on this docker container also! I already tried this container but the results are the same as for FlareSolverr. That is, it works as it should if I do not route the container through the qBittorrentVPN container. However, if the traffic is routed through the qBittorrentVPN container, getting/solving the Prowlarr test page (https://prowlarr.servarr.com/v1/ping) takes several minutes.From Byparr console when traffic is routed through the qBittorrentVPN container, getting the Prowlarr test page utilizing the curl command takes only a few seconds. So, VPN is working but maybe there is something similarly wrong for both FlareSolverr and Byparr. @binhex, any ideas on this?
June 2, 20251 yr Author 2 hours ago, EVERGREEN said:What are you using as Proxy? or am I missing something?I'm personally sharing the network of privoxyvpn with byparr, but you don't have to do this if you don't want, as long as prowlarr/jackett are on the same network as byparr then you should be good.
June 2, 20251 yr 2 hours ago, binhex said:I'm personally sharing the network of privoxyvpn with byparr, but you don't have to do this if you don't want, as long as prowlarr/jackett are on the same network as byparr then you should be good.Thanks for the response, I’ll giver a go!
June 3, 20251 yr 20 hours ago, binhex said:I'm personally sharing the network of privoxyvpn with byparr, but you don't have to do this if you don't want, as long as prowlarr/jackett are on the same network as byparr then you should be good.So, is there a trick to do to make the privoxyvpn network work with Byparr? I have set the VPN_INPUT_PORTS and Prowlarr can connect Byparr. But for some reason it takes a very long time to solve / retrieve the Prowlarr test page as I wrote.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.