ExtraTorrent indexer challenge solved by FlareSolverr but fails "blocked by CloudFlare Protection"
UjCbFwtBayFM opened this issue · 15 comments
Is there an existing issue for this?
- I have searched the existing open and closed issues
Current Behavior
Attempting to add ExtraTorrent indexer gives a "blocked by CloudFlare Protection" error despite FlareSolverr showing challenge as solved.
Expected Behavior
The indexer should be able to be added without issue.
Steps To Reproduce
- Attempt to add ExtraTorrent indexer
- Add the FlareSolverr proxy tag
- Click "Test" or "Save"
Environment
- OS: Windows 10 Pro x64 22H2
- Prowlarr: 1.13.3.4273
- FlareSolverr: 3.3.15
- Docker Install: no
- Using Reverse Proxy: noWhat branch are you running?
Master
Trace Logs?
FlareSolverr log:
2024-03-10 18:22:30 INFO Incoming request => POST /v1 body: {'maxTimeout': 120000, 'cmd': 'request.get', 'url': 'https://extratorrent.st/', 'proxy': {}}
2024-03-10 18:22:32 INFO Challenge detected. Selector found: #challenge-spinner
2024-03-10 18:22:38 INFO Challenge solved!
2024-03-10 18:22:38 INFO Response in 7.811 s
2024-03-10 18:22:38 INFO 127.0.0.1 POST http://localhost:8191/v1 200 OK
Prowlarr log
prowlarr.trace.txt
Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.
- I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain
trace- that are relevant and show this issue.
are cloudflare and prowlarr using the same IP?
Both FlareSolverr and Prowlarr are on the same machine, and FlareSolverr works fine with all other configured indexers.
Follow the troubleshooting steps here - https://github.com/FlareSolverr/FlareSolverr/wiki/Troubleshooting
What other indexers are working with FlareSolverr?
1337x and TorrentGalaxy.
1337x has their site broken and is in an endless loop
Are you using a proxy or VPN for Prowlarr, FlareSolverr, or the system as a whole?
Have you tried disabling IPv6 for your network adapter?
Are iDope, Mac Torrents Download, and Torrent[CORE] also working for you with FlareSolverr?
Are you using a proxy or VPN for Prowlarr, FlareSolverr, or the system as a whole?
Not using a proxy/VPN at all.
Have you tried disabling IPv6 for your network adapter?
It was already disabled when I noticed the issue.
Are iDope, Mac Torrents Download, and Torrent[CORE] also working for you with FlareSolverr?
iDope does not work (same error as ET). Mac Torrents Download does not work (same error as ET).
Torrent[CORE] does not work at all (no error message in both Prowlarr and FlareSolverr) probably because I could not set a base URL.
The URLs you're using for 1337x and TorrentGalaxy, do they present a Cloudflare challenge in browser? Are there logs in FlareSolverr when you access them in Prowlarr?
The URLs you're using for 1337x and TorrentGalaxy, do they present a Cloudflare challenge in browser? Are there logs in FlareSolverr when you access them in Prowlarr?
1137x and TorrentGalaxy do not always trigger a Cloudflare challenge, but when any of them do it is correctly detected and solved by FlareSolver and properly recognized by Prowlarr. As an example:
2024-03-12 14:20:00 INFO Incoming request => POST /v1 body: {'maxTimeout': 120000, 'cmd': 'request.get', 'url': 'https://1337x.to/cat/Movies/time/desc/1/', 'proxy': {}}
2024-03-12 14:20:04 INFO Challenge detected. Selector found: #challenge-spinner
2024-03-12 14:20:09 INFO Challenge solved!
2024-03-12 14:20:10 INFO Response in 9.539 s
As a test, install Jackett, configure FlareSolverr with it, add all the indexers mentioned above, test them and see which work.
If they all work then we may have an issue with Prowlarr, whereas if the same ones fail then the issue is with FlareSolverr, your computer, or your network.
On Jackett v0.21.2011, same machine:
- 1337x (through base URL https://1337x.to/) test passes and a manual search return correct results.
- Only the initial test appears in FlareSolverr, not the manual search.
- ExtraTorrent (though base URL https://extratorrent.st/) test passes and a manual search return correct results.
- Only the initial test appears in FlareSolverr, not the manual search.
- TorrentGalaxy (through base URL https://torrentgalaxy.to/) test passes but nothing appears in FlareSolverr. Manual search works and returns correct results.
Jackett was restarted between the three indexer tests to make sure the cache was empty.
Should be noted I already had Jackett installed on the same machine prior to installing Prowlarr.
iDope and Mac Torrents Download work as well? (Torrent[CORE] is currently down, hence it not working at all)
Are you on Windows 10 Home or Pro?
Machine is running Windows 10 Pro.
iDope works (first FlareSolverr test failed with a timeout, subsequent tests passed, Jackett manual search returns correct results).
FlareSolverr correctly detects and solves challenges for Mac Torrents Download but Jackett returns the same error every time:
Exception (mactorrentsdownload): The cookies provided by FlareSolverr are not valid: The cookies provided by FlareSolverr are not valid
Enable the Windows Sandbox feature if it isn't already, start Windows Sandbox, install Prowlarr and FlareSolverr, see if the same issue occurs.
The error makes me think the IPs are different (IPv4 vs IPv6) and the cookies aren't valid anymore.