I’m getting errors and I want to pick better indexers.
I use:
1337x Bangumimoe Bitmagnet Bitsearch BT.etree CrackingPatchin Ebookbay Kickasstorrents Limetorrents Linuxtracker Nipponsei Nyaa.si Shana Project Subsplease Uindex
But my prowlarr stats show that only these are used much
1337x ~ 500 grabs Bitsearch ~ 400 grabs Limetorrents ~ 250 grabs Kickasstorrents ~ 240 grabs Nyaa.si ~ 150 grabs Bitmagnet ~ 100 grabs
First rule about (torrent) indexers, don’t share which ones you are with.
Why?- Get banned (because powertrip)
- Get banned (rules said to not talk about it)
- Tracker gets taken down because of notoriety (which is bad)
- Feds ;)
My advice: Lurk on r/opensignups and similar tracker sharing pages (Either users are sharing the info and it’s fine with the mods of the tracker, or the mods don’t carr but you wont be banned).
For usenet there are some public ones you can sign up with.
Some usually open during specific times or events.But I’ll talk about 1 (and break the rule): TorrentLeech usually opens during the usual holidays like Eastern, Summerbreak, Halloween/Thanksgiving/BF, Christmas.
As for public trackers, I use 1337x and nyaa. Others arent as reliable or fail to find content I want.A bit off-topic, but, anyone else having issues with the Lidarr docker container refusing to boot? Had it working a few months ago now after updating the image i get “port already in use” errors in the logs? Is it just my setup or did something break upstream?
Mine runs fine.
Maybe your container port is actually in use?I checked and there doesnt seem to be anything running on that port, i closed a working container on another port and tried running it on that one but it still errored out. Hence why i thought it wasnt on my side.
I’ll have to do some more digging it seems…
I’m not using it atm, but you probably are running another service on the same port. Try mapping lidarr to a different port.
I have prowlarr set up with all of the available public trackers that it has built in capabilities for, and have sonarr/radarr set up to use prowlarr.
Only things I get errors for (at least that I’m noticing) is if I forget to have FlareSolverr on for some of em.
Haven’t used it in a little while. Cause there’s not shit out that I care enough to even pirate. But have used nzbgeek off and on for years. Even before an arr stack. It’s great.
What kind of errors? Usually issues are to do with incorrect quality profiles and custom formats.
If you don’t understand those then just follow the trash guides to the letter to start with.
To answer your actual question I use use the basics. Eztv, 1337, therarbg and kickass torrents. I rarely have any problems downloading mainstream stuff.
Just to clarify here, @tuff_wizard@aussie.zone means TRaSH Guides not that the guides are trash.
I have to concur by the way, aside from a handful Hungarian private trackers, I too use pretty much the same public trackers (with a few added from Prowlarr’s built in list for specific subtopics).
Yes good clarification, TRaSH is almost synonymous with *arr in my head, but there is a chance someone got to this point without running into them.
I rarely have issues, but occasionally I see errors like these:
All rss-capable indexers are temporarily unavailable due to recent indexer errors Indexers unavailable due to failures: The Pirate Bay (Prowlarr) All search-capable indexers are temporarily unavailable due to recent indexer errors Indexers unavailable due to failures for more than 6 hours: RuTracker.RU (Prowlarr)Digging into the logs
Warn|Torznab|API Request Limit reached for The Pirate Bay (Prowlarr). Disabled for 00:00:59|Warn|Torznab|API Request Limit reached for RuTracker.RU (Prowlarr). Disabled for 00:00:58Any recommendations to avoid API limits?
I have EZTV
1337 gave me an error. Are you using Flaresolverr?
Unable to connect to indexer. This is typically caused by DNS/SSL issues. Check DNS settings, ensure IPv6 is working or disabled, consider using different DNS servers, or try a VPN/proxy if needed. See: 'https://wiki.servarr.com/prowlarr/troubleshooting#dns-ssl-connection-issues' An error occurred while sending the request.I don’t see therarbg in the list, and I see two for kickass: ‘kickasstorrents.to’ and ‘kickasstorrents.ws’
Nb I use prowler to manage my indexers and point sonar/radarr at prowler but similar options should be available though sonar And radar.
You can limit the amount of queries and grabs your client will try per amount of time for each indexer. It is under advanced settings on the indexer page once you select an indexer.
This isn’t really a problem when you are just downloading one or two series but is a problem when you first start out and are downloading everything under the sun. Try limiting to 10 queries and grabs per hour for now. Might be a good idea to pause all requests for 24 hours as well as your ip may be temporarily flagged.
And yes I use flare solver for 1337
I also vaguely remember needing to have an account on ru tracker to make it work but it was all in Russian, and no English option I think. I had to use the browser auto translate
Use kickass.to, but they are just mirrors of each other.
I’d recommend setting up prowler now so you don’t have to do it all twice and if you want to spin up another radar or sonar later it’s easy to cover all your indexers.
Not sure about therarbg I can’t seem to add it either, despite having it as an active tracker.
I use NinjaCentral, DrunkenSlug, and nzbgeek, all paid. AnimeTosho is free and good.
Why would you need those, what do you use them for?
For the first three, those are so they can download via Usenet/Newsgroup instead of torrents.
I’ve never heard of the anime one, could also be Usenet.
