Challenge solved, but Prowlarr reports blocked

[lielianjie]

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: 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

[ilike2burnthing]

@KATTIX #1036

@lielianjie where are you seeing a timeout?

[lielianjie]

@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]

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

Is Prowlarr installed natively or also in Docker?

[lielianjie]

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]

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 :)

[lielianjie]

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]

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?

[lielianjie]

@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?

[lielianjie]

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

[ilike2burnthing]

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.

[lielianjie]

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]

Increase the timeout, try with YGGtorrent, not YGGcookie.

[lielianjie]

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

[ilike2burnthing]

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]

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]

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]

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]

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]

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]

@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]

@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]

how have you disabled IPv6?

[lielianjie]

how have you disabled IPv6?

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

[ilike2burnthing]

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]

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]

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]

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]

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

[ilike2burnthing]

As posted several times now - #1036 (i.e. the pinned issue).

[LightSeek3r]

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.

[ilike2burnthing]

It's an open issue.

[ilike2burnthing]

If the challenge is completed successfully in FlareSolverr for multiple indexers, is successful in Jackett but not Prowlarr, and both Jackett and Prowlarr are configured identically in Docker, then it points to some sort of issue with Prowlarr, although one I can't replicate.

Feel free to contact Prowlarr on their Discord to troubleshoot with them further, and point them to this issue.

[spamoi33]

Hello, I had this problem too. I managed to resolve it by removing the Flaresolver from Prowlarr's configuration and then putting it back with the tag. I then added YGGtorrent with the flaresolverr tag, and the connection was made.