FlareSolverr on a Seedbox: Cloudflare Bypass for Indexers

Install Byparr, Not FlareSolverr

If you came here looking for FlareSolverr, install Byparr instead. FlareSolverr is archived upstream, and its last release loses to the Cloudflare checks trackers use now, so it fails even when the process is perfectly healthy. Byparr is the drop-in replacement: same JSON API, same field in Prowlarr and Jackett, a browser engine that still gets through. It is what the Bytesized panel installs, and the rest of this guide is written for it.

What It Does

Byparr is a small proxy server. Its only job: solve Cloudflare's anti-bot challenges so other apps (mainly Prowlarr and Jackett) can read pages behind them.

Some torrent trackers sit behind Cloudflare's anti-bot stack. Without a solver in the chain, Prowlarr or Jackett gets a Cloudflare challenge page back instead of search results. With one, the request goes through a real headless browser that clears the challenge, and the tracker page comes back clean.

When You Actually Need It

You need Byparr if:

• A tracker you've added to Prowlarr or Jackett returns "Cloudflare challenge" errors
• Searches that used to work suddenly stopped (Cloudflare may have raised the protection level)
• A specific tracker's connection-test fails inside Prowlarr or Jackett with a Cloudflare-related message

If your indexers are working without errors, you don't need Byparr running.

Why Run It on a Seedbox?

Byparr only does its job if Prowlarr or Jackett can hit it on a stable URL. Same box as those apps is the cleanest way:

• One-click install in the panel
• Internal URL works without HTTPS or auth fuss
• Always on
• Uses the same shared infrastructure

Installing Byparr

Open the Bytesized Panel, find Byparr in the app catalog, click install. The panel takes care of the container, the browser it needs, and the port.

The app card then shows an API URL (something like http://127.0.0.1:4410). That is the address your indexers use, and it is the only thing you need from this page. Byparr does have a page of its own at byparr.<user>.<server>.bysh.me, protected with your appbox username and the password on the card, but you rarely need to open it. Your indexers talk to the API and send no credentials.

Wiring It Into Prowlarr

In Prowlarr's Settings > Indexers > Add Indexer Proxy > FlareSolverr:

• Host: the address from the app card, without the scheme
• Port: the port from the app card
• Tags: add a tag (e.g., cf); apply this tag to indexers that need it

Save, then for each tracker hitting Cloudflare problems, add the cf tag in its indexer config. Prowlarr routes those requests through Byparr automatically.

The proxy type is still called FlareSolverr in Prowlarr's menu. That is the protocol name, and it is the right one to pick.

Wiring It Into Jackett

In Jackett, Settings > FlareSolverr API URL. Paste Byparr's API URL there. The field keeps the old name; Jackett routes Cloudflare-protected requests through Byparr automatically.

One field, one URL. If you were already running FlareSolverr, pointing this at Byparr replaces it rather than adding to it.

Common Gotchas

A solver eats CPU. A headless browser isn't free. Heavy use (lots of concurrent searches across many CF-protected indexers) can spike CPU. Limit concurrency in Prowlarr or Jackett if it's a problem.

Still getting Cloudflare errors. Cloudflare's protection levels change over time, and a solver can lag behind the newest checks. Bytesized pins the Byparr build we have measured against live Cloudflare rather than tracking latest, and moves the pin when a newer one tests better. If a tracker is failing, check the app card shows Byparr running before you go further.

Tracker says "Captcha required." Byparr handles automatic challenges, not human captchas. If a tracker is asking for an interactive captcha, you'll need to solve it in a browser and paste the cookie into Jackett or Prowlarr.

Service crashed. Byparr can run out of memory under heavy load. The panel auto-restarts it; if you keep hitting this, throttle concurrency.

FAQ

Is Byparr free? Yes. Free and open source, like FlareSolverr before it.

Do I always need to run it? No. Only when a tracker behind Cloudflare's anti-bot stack starts returning challenges.

Does it work with Sonarr or Radarr directly? No. Sonarr and Radarr talk to your indexers through Prowlarr or Jackett. Byparr sits in front of those, not directly in front of Sonarr.

Will it slow my searches down? A little. The CF challenge solve adds a second or two. Trivial in normal use, noticeable if you're running parallel searches across many CF-protected trackers.

Is it legal? The tool is. What you scrape with it is your concern, the same as any other indexer setup.

Ready to Set It Up?

Browse Appbox plans, install Byparr from the panel, paste its API URL into Prowlarr or Jackett, tag the affected trackers.