Challenge solved, but Prowlarr reports blocked

lielianjie commented 7 months ago

Have you checked our README?

[X] I have checked the README

Have you followed our Troubleshooting?

[X] I have followed your Troubleshooting

Is there already an issue for your problem?

[X] I have checked older issues, open and closed

Have you checked the discussions?

[X] I have read the Discussions

Environment

- FlareSolverr version: 3.3.16
- Last working FlareSolverr version: 3.3.16 (I guess)
- Operating system: Synology
- Are you using Docker: yes
- FlareSolverr User-Agent (see log traces or / endpoint):
- Are you using a VPN: no
- Are you using a Proxy: no
- Are you using Captcha Solver: no
- If using captcha solver, which one:
- URL to test this issue: https://www3.yggtorrent.qa

Description

Hi,

Since few days I have this issue with YGG (see logs). It seems that the challenge is solved but I have a timeout. I'm using Prowlarr since a while and never had this issue before.

Logged Error Messages

2024-04-02 10:59:17 INFO     Incoming request => POST /v1 body: {'maxTimeout': 60000, 'cmd': 'request.get', 'url': 'https://www3.yggtorrent.qa/engine/search?category=all&do=search&order=desc&sort=publish_date', 'proxy': {}}
version_main cannot be converted to an integer
2024-04-02 10:59:21 INFO     Challenge detected. Title found: Just a moment...
2024-04-02 10:59:26 INFO     Challenge solved!
2024-04-02 10:59:26 INFO     Response in 9.096 s
2024-04-02 10:59:26 INFO     192.168.1.102 POST http://192.168.1.103:8191/v1 200 OK

Screenshots

No response

K3RM1T-CYBER commented 7 months ago

Same

KATTIX commented 7 months ago

same here they are my logs

2024-04-02 17:56:13 INFO Challenge detected. Title found: Just a moment... 2024-04-02 17:57:07 ERROR Error: Error solving the challenge. Timeout after 55.0 seconds. 2024-04-02 17:57:07 INFO Response in 55.965 s 2024-04-02 17:57:07 INFO 172.19.0.1 POST http://192.168.1.38:8191/v1 500 Internal Server Error

ilike2burnthing commented 7 months ago

@KATTIX https://github.com/FlareSolverr/FlareSolverr/issues/1036

@lielianjie where are you seeing a timeout?

lielianjie commented 7 months ago

@KATTIX #1036

@lielianjie where are you seeing a timeout?

I guess I thought it was a timeout issue because I saw "maxTimeout': 60000" but in Prowlarr, I have this error:

and in Flaresolverr logs, I have this error:

2024-04-02 10:59:17 INFO Incoming request => POST /v1 body: {'maxTimeout': 60000, 'cmd': 'request.get', 'url': 'https://www3.yggtorrent.qa/engine/search?category=all&do=search&order=desc&sort=publish_date', 'proxy': {}} version_main cannot be converted to an integer

ilike2burnthing commented 7 months ago

Follow the troubleshooting steps here -https://github.com/FlareSolverr/FlareSolverr/wiki/Troubleshooting

Is Prowlarr installed natively or also in Docker?

lielianjie commented 7 months ago

Prowlarr is also installed on docker but on another Synology. I just read in your troubleshooting that both Flaresolverr and Prowlarr should be isntall on the same host so I'll do that and I'll check the rest of the troubleshooting and I'll get back to you. Odd though because everything was working flawlessly during many months.

K3RM1T-CYBER commented 7 months ago

I was in the same situation as him. I just moved my prowlarr container to the same server as my flaresolverr, it seems to be working again. THANKS :)

Guesh1337 commented 7 months ago

I'm using Jackett and Flaresolverr on the same linux machine using docker and i'm having this issue since 3 days on YGG

Brokeos commented 7 months ago

Running on docker, without vpn / proxy

2024-04-03 17:19:24 DEBUG ReqId 140383032174336 Navigating to... https://www3.yggtorrent.qa/engine/search?do=search&order=desc&sort=publish_date&category=all 2024-04-03 17:19:24 INFO ReqId 140383032174336 Challenge detected. Title found: Just a moment... 2024-04-03 17:19:24 DEBUG ReqId 140383032174336 Waiting for title (attempt 1): Just a moment... 2024-04-03 17:19:25 DEBUG ReqId 140383032174336 Timeout waiting for selector 2024-04-03 17:19:25 DEBUG ReqId 140383032174336 Try to find the Cloudflare verify checkbox... 2024-04-03 17:19:25 DEBUG ReqId 140383032174336 Cloudflare verify checkbox not found on the page. 2024-04-03 17:19:25 DEBUG ReqId 140383032174336 Try to find the Cloudflare 'Verify you are human' button... 2024-04-03 17:19:25 DEBUG ReqId 140383032174336 The Cloudflare 'Verify you are human' button not found on the page. ... 2024-04-03 17:20:19 DEBUG ReqId 140383032174336 Waiting for title (attempt 18): Just a moment... 2024-04-03 17:20:19 DEBUG ReqId 140383065745152 A used instance of webdriver has been destroyed 2024-04-03 17:20:19 ERROR ReqId 140383065745152 Error: Error solving the challenge. Timeout after 55.0 seconds. 2024-04-03 17:20:19 DEBUG ReqId 140383065745152 Response => POST /v1 body: {'status': 'error', 'message': 'Error: Error solving the challenge. Timeout after 55.0 seconds.', 'startTimestamp': 1712164764113, 'endTimestamp': 1712164819840, 'version': '3.3.12'}

Brokeos commented 7 months ago

I just installed on a debian VM, works perfectly, maybe a problem with the docker image?

ilike2burnthing commented 7 months ago

See troubleshooting and issue linked above.

lielianjie commented 7 months ago

Follow the troubleshooting steps here -https://github.com/FlareSolverr/FlareSolverr/wiki/Troubleshooting

Is Prowlarr installed natively or also in Docker?

So I followed the troubleshooting guide but unfortunately it's still not good.

In Prowlarr :

In Flaresolverr logs:

2024-04-03 17:35:54 INFO Incoming request => POST /v1 body: {'maxTimeout': 60000, 'cmd': 'request.get', 'url': 'https://www3.yggtorrent.qa/engine/search?category=all&do=search&order=desc&sort=publish_date', 'proxy': {}} version_main cannot be converted to an integer 2024-04-03 17:36:02 INFO Challenge detected. Title found: Just a moment... 2024-04-03 17:36:06 INFO Challenge solved! 2024-04-03 17:36:07 INFO Response in 12.216 s 2024-04-03 17:36:07 INFO 192.168.1.102 POST http://192.168.1.102:8191/v1 200 OK

ilike2burnthing commented 7 months ago

So to be clear, Prowlarr and FlareSolverr are now running on the same device, both in Docker, with no VPN or proxy, and with IPv6 disabled?

Are iDope, Mac Torrents Download and Torrent[CORE] working for you?

LightSeek3r commented 7 months ago

I have the same issue since a few days on native windows install (both Prowlarr and Flaresolverr are installed natively). It used to be working fine for quite some time, until now.

ilike2burnthing commented 7 months ago

Answer the questions from https://github.com/FlareSolverr/FlareSolverr/issues/1139#issuecomment-2035221857.

LightSeek3r commented 7 months ago

So to be clear, they are both running on the same device, not on docker as I said they are both running natively on Windows (11), there is no VPN involved and IPV6 is disabled. Confirmed.

As previously mentionned, this untouched setup (system & softwares) used to work for months. As you can see from the other comments, it's not a one user issue. Wild guess here, it is most likely an issue between Flaresolverr, Cloudfare, and YGG. Specifically. Knowing how YGG admins can be a pain and somehow stubborn and off logic, I'd say maybe they changed something in their Cloudfare config. But I'm not an expert in Cloudfare, nor networking in general.

I'm not using iDope but qBittorrent which is otherwise working perfectly, why would I use Mac Torrents on Windows, and is there a specific reason why I would have to use a specific torrent client such as torrent core instead of qBittorrent?

Thanks for your helping and relevancy.

ilike2burnthing commented 7 months ago

Those are indexers in Jackett and Prowlarr, not torrent clients. Add and test them.

LightSeek3r commented 7 months ago

So, iDope and Torrent[CORE] fail the same way as YggTorrents does, the challenge is not resolved. Mac Torrents test passes. Screenshot_2024-04-04-14-13-08-677_net dwservice client-edit

ilike2burnthing commented 7 months ago

Oh, looks like Mac Torrents Download has dropped the Cloudflare challenge. Try Cinecalidad instead. Also try increasing the FlareSolverr timeout to 120s in Prowlarr's settings.

cahuete95 commented 7 months ago

@lielianjie activate debug log in flaresolver and you might have the same logs than in https://github.com/FlareSolverr/FlareSolverr/issues/1113#issuecomment-1988167935

@ilike2burnthing i think it's the same concern than the behaviour in the issue mentionned : infinite loop on cloudflare challenge for ygg. ygg only it seems because i didn't notice the same on other sites using/needing flaresolver (i've have a few and i'm with prowlarr too).

Nota : "timeout to 120s in Prowlarr's settings"-> already done ;-)

ch-boogeyman commented 7 months ago

Same timeout problem,i had try 120s. The quizzer's https://www3.yggtorrent.qa/engine/search?category=all&do=search&order=desc&sort=publish_date is OK. Can someone help me try this website https://xslist.org/zh/searchByImage/ work?

lielianjie commented 7 months ago

@ilike2burnthing Well, I did try everything you guys asked here but nothing worked. No VPN, no proxy, no IPV6. Both Prowlarr and Flare on the same host and docker. Timeout at 120s in Prowlarr.

Test with YGG:

Test with iDope:

Test with Torrent[CORE]:

So it's seems that Flare solved the captcha each time time but I still have the error message in Prowlarr and indexers are unusabled :(

Also, I tried to roll back on v3.3.15 and 3.3.9 but same.

What should I test next?

ch-boogeyman commented 7 months ago

Well, I did try everything you guys asked here but nothing worked. No VPN, no proxy, no IPV6. Both Prowlarr and Flare on the same host and docker. Timeout at 120s in Prowlarr.

try another computer,the web you curl can work on FlareSolverr

lielianjie commented 7 months ago

Well, I did try everything you guys asked here but nothing worked. No VPN, no proxy, no IPV6. Both Prowlarr and Flare on the same host and docker. Timeout at 120s in Prowlarr.

try another computer,the web you curl can work on FlareSolverr

What do you mean? Is it working for you? I have my whole infrastructure installed on a server, I can't just migrate everything from on another computer just for testing.

lielianjie commented 7 months ago

_flaresolverr_logs.txt Here I tried again with the debug logs.

ilike2burnthing commented 7 months ago

Remove the indexer from Prowlarr, restart the FlareSolverr and Prowlarr containers, add the indexer again, ensuring to add the tag for FlareSolverr. See if that works.

If not, try the YGGcookie indexer.

As a test you can also try adding a Jackett container, configuring FlareSolverr there, increasing the timeout, and seeing if YGGtorrent works in it.

ch-boogeyman commented 7 months ago

@ilike2burnthing Is this a bug,FlareSolverr can't work on https://xslist.org/zh/searchByImage

ilike2burnthing commented 7 months ago

Haven't checked, but look at https://github.com/FlareSolverr/FlareSolverr/issues/1036.

lielianjie commented 7 months ago

So I tried with Jackett and I have this error:

Tried iDope from Jacket with Flare:

I was using YGGcookie the whole time.

Challenge is solved for YGG but not for iDope.

Any idea?

ilike2burnthing commented 7 months ago

Increase the timeout, try with YGGtorrent, not YGGcookie.

lielianjie commented 7 months ago

Timeout set to 120s. Challenge solved with both YGGcookie and YGGtorrent:

ilike2burnthing commented 7 months ago

Both the FlareSolverr and Jackett containers are using the host network setting?

How have you disabled IPv6? If per container, did you also disable it for Jackett?

lielianjie commented 7 months ago

OMG

I forgot to change Jackett to host (it was on bridge). Seems to work with jackett now.

I'll try some real tests.

lielianjie commented 7 months ago

So finaly, it's working well on Jackett but still not working on Prowlarr after everything i've done. It's kinda fine for me but I don't know if you need to keep this issue open or not knowing there is a potential problem with Prowlarr. If you want, I can do more tests. Anyway, thanks for helped me.

V1ck3s commented 7 months ago

So finaly, it's working well on Jackett but still not working on Prowlarr after everything i've done. It's kinda fine for me but I don't know if you need to keep this issue open or not knowing there is a potential problem with Prowlarr. If you want, I can do more tests. Anyway, thanks for helped me.

What's all the steps you've made to fix this on jackett ?

lielianjie commented 7 months ago

So finaly, it's working well on Jackett but still not working on Prowlarr after everything i've done. It's kinda fine for me but I don't know if you need to keep this issue open or not knowing there is a potential problem with Prowlarr. If you want, I can do more tests. Anyway, thanks for helped me.

What's all the steps you've made to fix this on jackett ?

I didn't used Jackett at all at the beguining so I installed it via Docker on the same server as Flare and at first it didn't worked. I realized that the the network setting for the Jackett's container wasn't set to Host but to Bridge. I changed it to Host and it worked.

That beeing said, Prowlarr is correctly configured but it's still doesn't work.

V1ck3s commented 7 months ago

Ok. I use Jackett on an ARM server, it doesn't work anymore on it. I installed it on my PC with docker and it works. Don't know why it works on one and not on another. I'll try changing the network to home tonight.

ilike2burnthing commented 7 months ago

@lielianjie with the YGGtorrent indexer (NOT YGGcookie) you removed the indexer from Prowlarr, restarted the FlareSolverr and Prowlarr containers, added the indexer again, ensuring to add the tag for FlareSolverr, and that didn't change anything?

If not, how have you disabled IPv6?

@V1ck3s see the discussion above and the troubleshooting steps here - https://github.com/FlareSolverr/FlareSolverr/wiki/Troubleshooting

lielianjie commented 7 months ago

@lielianjie with the YGGtorrent indexer (NOT YGGcookie) you removed the indexer from Prowlarr, restarted the FlareSolverr and Prowlarr containers, added the indexer again, ensuring to add the tag for FlareSolverr, and that didn't change anything?

If not, how have you disabled IPv6?

@V1ck3s see the discussion above and the troubleshooting steps here - https://github.com/FlareSolverr/FlareSolverr/wiki/Troubleshooting

When trying to configure YGGtorrent on Prowlarr, I can't even validate the indexer configuration. It give me that error with or without Flare: This why I started to use YGGcookie few months ago.

ilike2burnthing commented 7 months ago

how have you disabled IPv6?

lielianjie commented 7 months ago

how have you disabled IPv6?

TBH I don't remember how (certainly did a long time ago) but it is disabled:

ilike2burnthing commented 7 months ago

I'm not familiar with Synology, but as far as I can tell that is their Docker manager app. Try disabling IPv6 for all network interfaces in their control panel instead.

lielianjie commented 7 months ago

I'm not familiar with Synology, but as far as I can tell that is their Docker manager app. Try disabling IPv6 for all network interfaces in their control panel instead.

Indeed. In my Syno's network interface, IPV6 is disable and since the network selected for the container is "host" this is why IPV6 is disable for the container as well.

ilike2burnthing commented 7 months ago

So do iDope, ~Cinecalidad~ and Torrent[CORE] now all work in Jackett but all fail in Prowlarr, despite being successful in FlareSolverr?

Edit: just realised Cinecalidad isn't available in Prowlarr.

lielianjie commented 7 months ago

So do iDope, ~Cinecalidad~ and Torrent[CORE] now all work in Jackett but all fail in Prowlarr, despite being successful in FlareSolverr?

Edit: just realised Cinecalidad isn't available in Prowlarr.

Yes, they all work under Jackett.

ilike2burnthing commented 7 months ago

but all fail in Prowlarr, despite being successful in FlareSolverr?

n1nj444 commented 7 months ago

Got this on my side :

2024/04/11 19:06:16 | stdout | 2024-04-11 17:06:16 INFO     Challenge detected. Title found: Just a moment...
2024/04/11 19:06:02 | stdout | version_main cannot be converted to an integer
2024/04/11 19:06:02 | stdout | 2024-04-11 17:06:02 INFO     Incoming request => POST /v1 body: {'maxTimeout': 120000, 'cmd': 'request.get', 'url': 'https://www3.yggtorrent.qa/'}
2024/04/11 19:06:02 | stdout | 2024-04-11 17:06:02 INFO     172.17.0.1 POST http://192.168.1.18:8191/v1 500 Internal Server Error
2024/04/11 19:06:02 | stdout | 2024-04-11 17:06:02 INFO     Response in 121.518 s
2024/04/11 19:06:02 | stdout | 2024-04-11 17:06:02 ERROR    Error: Error solving the challenge. Timeout after 120.0 seconds.
2024/04/11 19:04:14 | stdout | 2024-04-11 17:04:14 INFO     Challenge detected. Title found: Just a moment...

Greg1077 commented 7 months ago

Hey, I think I have the same issue, hope it's ok to share here.

I've read the troubleshooting, disabled IPv6, moved containers to the same host interface, removed the indexer and restarted, increased time out...

I'm only using Prowlarr, not Jacket, and Flaresolver stopped working a couple of weeks ago (no VPN, no proxy, same device).

Here are the logs, same outcome with iDope and YGG:


2024/04/11 22:32:16 stdout  2024-04-11 20:32:16 INFO     192.168.178.100 POST http://192.168.178.100:8191/v1 500 Internal Server Error
2024/04/11 22:32:16 stdout  2024-04-11 20:32:16 INFO     Response in 181.083 s
2024/04/11 22:32:16 stdout  2024-04-11 20:32:16 ERROR    Error: Error solving the challenge. Timeout after 180.0 seconds.
2024/04/11 22:29:17 stdout  2024-04-11 20:29:17 INFO     Challenge detected. Title found: Just a moment...
2024/04/11 22:29:15 stdout  version_main cannot be converted to an integer
2024/04/11 22:29:15 stdout  2024-04-11 20:29:15 INFO     Incoming request => POST /v1 body: {'maxTimeout': 180000, 'cmd': 'request.get', 'url': 'https://www3.yggtorrent.qa/engine/search?category=all&do=search&order=desc&sort=publish_date', 'proxy': {}}
2024/04/11 22:28:27 stdout  2024-04-11 20:28:27 INFO     192.168.178.100 POST http://192.168.178.100:8191/v1 500 Internal Server Error
2024/04/11 22:28:27 stdout  2024-04-11 20:28:27 INFO     Response in 180.987 s
2024/04/11 22:28:27 stdout  2024-04-11 20:28:27 ERROR    Error: Error solving the challenge. Timeout after 180.0 seconds.
2024/04/11 22:25:37 stdout  2024-04-11 20:25:37 INFO     Challenge detected. Title found: Just a moment...
2024/04/11 22:25:26 stdout  version_main cannot be converted to an integer
2024/04/11 22:25:26 stdout  2024-04-11 20:25:26 INFO     Incoming request => POST /v1 body: {'maxTimeout': 180000, 'cmd': 'request.get', 'url': 'https://idope.se/browse.html', 'proxy': {}}
2024/04/11 22:24:56 stdout  2024-04-11 20:24:56 INFO     Serving on http://0.0.0.0:8191
2024/04/11 22:24:56 stdout  2024-04-11 20:24:56 INFO     Test successful!
2024/04/11 22:24:56 stdout  2024-04-11 20:24:56 INFO     FlareSolverr User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
2024/04/11 22:24:55 stdout  version_main cannot be converted to an integer
2024/04/11 22:24:55 stdout  2024-04-11 20:24:55 INFO     Launching web browser...
2024/04/11 22:24:55 stdout  2024-04-11 20:24:55 INFO     Chrome / Chromium major version: 120
2024/04/11 22:24:55 stdout  2024-04-11 20:24:55 INFO     Chrome / Chromium path: /usr/bin/chromium
2024/04/11 22:24:55 stdout  2024-04-11 20:24:55 INFO     Platform: Linux-4.4.302+-x86_64-with-glibc2.31
2024/04/11 22:24:55 stdout  2024-04-11 20:24:55 INFO     Testing web browser installation...
2024/04/11 22:24:55 stdout  2024-04-11 20:24:55 INFO     FlareSolverr 3.3.13

ilike2burnthing commented 7 months ago

As posted several times now - https://github.com/FlareSolverr/FlareSolverr/issues/1036 (i.e. the pinned issue).

LightSeek3r commented 6 months ago

So, to me all indexers ended up being resolved with the latest update of FlareSolverr, with Prowlarr. But for some reason with YGG via Radarr/Sonarr, I always got "invalid torrent specified" "getting release from indexer failed". Switching from Prowlarr to Jackett solved it once and for all. Confirming there is currently an issue between FlareSolverr & Prowlarr.

FlareSolverr / FlareSolverr