just switched to surfshark for this and used your affiflate code, thanks for all the effort! anyway, when i send a request from seerr it doesnt get sent to my radarr. i added 1337, eztv and nyaa as my indexers (tpb is down rn) and in prowlarr under systemstatus, it says all indexers are unavailable due to failures. i cant figure out why. Also when it states the initial failure, last failure, then the disabled until, mine says until tomorrow. why would it be disabled and what can i do about that? also side thing, what are the chances 1337 is banned on my ip through my vpn because it says access denied but works on other devices. sorry theres a lot to unpack here lol but thanks a lot for any help! looking forward to having this setup by tonight
8 replies
tomspark wrote:
Thanks so much for using the Surfshark link — that genuinely helps keep the project going! The "access denied but works on other devices" is the key to everything else here. Those other devices aren't going through the VPN, so 1337x is blocking the VPN server's IP — not yours personally. Since Prowlarr also routes through the VPN, it hit the same wall, failed several times, and automatically said "I'll stop trying until tomorrow" to avoid hammering a blocked site. That's expected behavior, not a broken setup. Easiest fix: in the Surfshark app, switch to a different server (try a different city). You'll get a fresh IP and Prowlarr should recover on its own. Once the indexers work, Seerr → Radarr requests will flow through too.
delax wrote:
thanks for the reply. so i was able to figure it out but now my issue is the lack of indexers but more specifically cloud flare problems. cloud flare has been updated and now makes 1337x and eztv inaccessible . so that's why i could not receive anything. do you know any work around for this, i saw somethings online but im getting in over my head with how far my understanding for all this goes. not sure if its possible since this was like an automated thing rather than me doing everything myself. And whether you have any free alternatives or maybe whether going down the private route is the move... (is tpb good enough to roll with solo?? its down as of right now)
tomspark wrote:
That 'cloud flare has been updated and now makes 1337x and eztv inaccessible' problem has a standard fix for Prowlarr: FlareSolverr. It's a small extra container that handles Cloudflare challenges automatically — once it's running, you link it in Prowlarr under Settings Indexers using the FlareSolverr URL field, and those indexers work again. As for TPB solo, it's okay for popular movies and shows but misses a lot of niche content. Private trackers are the better long-term move if you want reliable results.
delax wrote:
is flaresolverr not already built into the stack? i have the flaresolverr that is included and shown on prowlarr
tomspark wrote:
Yes, FlareSolverr being in the stack and showing in Prowlarr is exactly right — you're halfway there. The last step is linking it to each individual indexer. In Prowlarr, go to Indexers, click the pencil to edit 1337x (or eztv), and look for a FlareSolverr dropdown in the indexer settings — pick the one you see listed. Do the same for each broken indexer and save. After that, those sites should bypass Cloudflare automatically.
delax wrote:
im a little confused. im on the edit screen for 1337 but theres no flaresolverr dropdown besides 1 thing that says, flaresolverr info. then theres a blue box next to it saying. "this site may use cloudflare ddos protection, therefore prowlarr requires flaresolverr to access it." thats all i see. but also i wnt to specift i never saw a pencil tool i figured you meant the wrench looking thing to edit it
delax wrote:
does this have anything to do with tags??
tomspark wrote:
Yep — tags are exactly it, good instinct! That blue warning box is just info; the actual hookup lives in a different spot. Two steps: first, in Prowlarr go to Settings → Indexers and scroll down to the 'Indexer Proxies' section, click the + to add FlareSolverr, and give it a tag name like 'flare'. Then go back and edit your 1337x indexer (the wrench, you've got it), and in its Tags field type that same 'flare' tag. Save, and Prowlarr will start routing 1337x through FlareSolverr. Do the same tag on eztv. That's the piece the edit screen never spells out.