FlareSolverr: [yggtorrent] (testing) Exception (yggtorrent): 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.

Have you checked our README?

  • I have checked the README

Have you followed our Troubleshooting?

  • I have followed your Troubleshooting

Is there already an issue for your problem?

  • I have checked older issues, open and closed

Have you checked the discussions?

  • I have read the Discussions

Environment

- FlareSolverr version:
- Last working FlareSolverr version:
- Operating system:
- Are you using Docker: [yes/no]
- FlareSolverr User-Agent (see log traces or / endpoint):
- Are you using a VPN: [yes/no]
- Are you using a Proxy: [yes/no]
- Are you using Captcha Solver: [yes/no]
- If using captcha solver, which one:
- URL to test this issue:

Description

.

Logged Error Messages

2023-11-01 11:57:43 INFO     FlareSolverr 3.3.6
2023-11-01 11:57:43 INFO     Testing web browser installation...
2023-11-01 11:57:44 INFO     Platform: Windows-10-10.0.22621
2023-11-01 11:57:44 INFO     Chrome / Chromium path: C:\Users\nike9\Downloads\flaresolverr\chrome\chrome.exe
2023-11-01 11:57:44 INFO     Chrome / Chromium major version: 115
2023-11-01 11:57:44 INFO     Launching web browser...
2023-11-01 11:57:47 INFO     FlareSolverr User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36
2023-11-01 11:57:47 INFO     Test successful!
2023-11-01 11:57:47 INFO     Serving on http://0.0.0.0:8191
2023-11-01 11:57:55 INFO     Incoming request => POST /v1 body: {'maxTimeout': 55000, 'cmd': 'request.get', 'url': 'https://www3.yggtorrent.wtf/engine/search?do=search&order=desc&sort=publish_date&category=all'}
2023-11-01 11:57:56 INFO     Challenge detected. Selector found: #challenge-spinner
2023-11-01 11:58:51 ERROR    Error: Error solving the challenge. Timeout after 55.0 seconds.
2023-11-01 11:58:51 INFO     Response in 56.024 s
2023-11-01 11:58:51 INFO     127.0.0.1 POST http://localhost:8191/v1 500 Internal Server Error
2023-11-01 11:59:43 INFO     127.0.0.1 GET http://localhost:8191/ 200 OK

Screenshots

No response

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Reactions: 1
  • Comments: 63 (16 by maintainers)

Most upvoted comments

For me it did, 3.3.7 works.

Rebuilding a container is the actual way of updating the dependencies. You should never ssh in and update a running container, that’s against the whole philosophy.

Hello. I had exactly the same problem with jackett and yggtorrent indexer. I managed to make it work again simply by :

  • using latest docker release
  • connect on it with root user
  • update everything (chromium in particular ) :apt-get update; apt-get upgrade
  • restart the container
  • test with jackett : it’s working ! 🎉

Hope it will last longer than 30 minutes ! 😄

FYI YggCookie worked for about 30 mins, now it is not working again.

@mushuthecat Thank’s you, it works for me !

hi, I’m using flaresolverr v3.3.2 with docker and this is my log

2023-11-02 20:08:59 DEBUG ReqId 22523894298368 Waiting for title (attempt 18): Just a moment... 2023-11-02 20:09:00 DEBUG ReqId 22523894298368 Timeout waiting for selector 2023-11-02 20:09:00 DEBUG ReqId 22523894298368 Try to find the Cloudflare verify checkbox... 2023-11-02 20:09:00 DEBUG ReqId 22523894298368 Cloudflare verify checkbox not found on the page. 2023-11-02 20:09:00 DEBUG ReqId 22523894298368 Try to find the Cloudflare 'Verify you are human'

and after 60s i’ve got the timeout like everyone

use YGGcookie to workaround the issue

Hi,

Workaround on my side using YGGcookie and not YGGtorrent:

  • stop your flaresolverr docker container
  • delete all images from flaresolverr
  • docker-compose up -d using 3.3.2
  • setup yggcookie on my jackett container (flaresolverr & jackett must be in the same host)

It works on my side