If youve used Prowlarr, you might have experienced cloudflare blocking access to certain trackers.

There's a docker-based solution called cloudsolverr which automatically bypasses these cloudflare challenges by spinning up a headless chromium browser.

Main issue is it's heavy on resources (I have an rpi4b) and doesn't have an easy native setup (I've not had time to practice with docker stuff yet).

Is there a manual way for me to resolve these cloudflare challenges so I can add the trackers? It's mainly for public shit like 1337x just to fill out my access to TV shows where my other trackers fail or get rate-limited.

  • American_Jesus@lemm.ee
    ·
    15 days ago

    I use a TOR proxy, it requires a little more knowledge.

    Have a docker container running TOR as SOCKS/HTTP proxy.

    NAME       CPU %     MEM USAGE
torproxy   0.07%     46.78MiB

    Added SOCKS proxy to Prowlarr. Added a tag to this proxy.

    Create/modify indexer with TOR/Onion domain, with proxy tag.

    I have that for 1337x and BTdig.

    Instead of connecting to 1337x.to wich requires CloudFlare, it connects to l337xdarkkaqfwzntnfk5bmoaroivtl6xsbatabvlb52umg6v3ch44yd.onion via TOR proxy.

    Also i can use that TOR proxy for other containers/software.

    HOW TO:

    1. Use a TOR proxy docker container.
    • https://github.com/PeterDaveHello/tor-socks-proxy
    • https://github.com/shahradelahi/docker-torproxy
    1. Add TOR proxy to Prowlarr (Settings -> Indexers), with a tag (ex: TOR)
    2. Create a new Prowlarr indexer
    • Copy indexer from prowlarr/Definitions to prowlarr/Definitions/Custom (ex: 1337x.yml)
    • Change the indexer URL and ID/Name
    id: 1337x-TOR
name: 1337x-TOR
...
links:
    - http://l337xdarkkaqfwzntnfk5bmoaroivtl6xsbatabvlb52umg6v3ch44yd.onion/
...
    1. Restart Prowlarr
    2. Add indexer (1337x-TOR) with Base URL .onion URL and with tag from TOR proxy (ex: TOR).

    Other onion torrent sites:

    • TorrentGalaxy: http://galaxy3yrfbwlwo72q3v2wlyjinqr2vejgpkxb22ll5pcpuaxlnqjiid.onion/
    • btdig: http://btdigggink2pdqzqrik3blmqemsbntpzwxottujilcdjfz56jumzfsyd.onion/
  • catloaf@lemm.ee
    ·
    17 days ago

    I use flaresolverr. Seems to work okay for me, I've had no issues getting stuff.

    https://github.com/FlareSolverr/FlareSolverr

    You could also try Usenet.

  • Appoxo@lemmy.dbzer0.com
    ·
    15 days ago

    Alternative: flaresolverr

    https://github.com/FlareSolverr/FlareSolverr

    Edit: Regarding your question to reduce issues:

    1. I had it on a Pi, and it didnt tac it very much (BUT I used flaresolverr!)
    2. Limit the request times of your trackers?
    • guybrush_threepwood_MP@lemmy.dbzer0.com
      ·
      14 days ago

      Turns out, my ISP has silently done a transparent DNS redirection. And their DNS servers are bad. Had to change to DoT to get it working. Something I should have done long ago anyway.