Flaresolverr Next

Flaresolverr-next is a build of FlareSolverr made for Quasarr.

  • Development
  • Network Services
  • Tools & Utilities
Flaresolverr-next is a build of FlareSolverr made for Quasarr. FlareSolverr is a proxy that bypasses Cloudflare and other site security checks in a real browser, and this fork adds back executeJs results, trusted clicks, and a Google reCAPTCHA solver on top. It is a drop-in replacement for the original, so you point Quasarr at it to fetch pages that would otherwise be blocked, and when a site shows an interactive reCAPTCHA it can solve the token through 2Captcha if you supply an API key (without a key it only attempts the checkbox).

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

58/100 Fair

Maintained
100last commit 17 days ago
Popular
165 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
502 GB minimum RAM

Availability: platform listings confirmed today

GitHub stars
5
Open issues
0
Last commit
2026-11-04
Latest release
v3.5.2-executejs-2
License
MIT
Activity
steady

Checked 16 days ago - source: GitHub (rix1337/flaresolverr-next)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 100 MB disk.

Checked 16 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Use the legacy page only if it matches This wiki page is marked LEGACY and is for a FreeBSD or TrueNAS CORE jail (a separate container-like section of the OS) install. If you are using a different FlareSolverr install method, skip these commands because the packages and service name may not apply. source
  • Install the needed packages first If you are following that FreeBSD/TrueNAS jail guide, run the `pkg install` commands for Python, Chromium (a web browser), and Linux-base compatibility files. Those pieces let FlareSolverr drive a real browser behind the scenes, so missing them can make page requests fail. source
  • Start the service after setup Once installed, run `service flaresolverr start` so the named background program turns on and keeps listening for requests. Without this final step, other tools time out because they cannot connect to FlareSolverr. source
  • Point Quasarr at the service and optionally add a 2Captcha key Flaresolverr-next is a drop-in replacement for FlareSolverr. Once the container is running, point Quasarr at http://[IP]:8191/v1 (replace [IP] with the host's address). By default it only attempts the reCAPTCHA checkbox; if a site serves an interactive reCAPTCHA, create an API key at 2captcha.com and set it in the service so it can hand the token solve to 2Captcha. source

Fetched 16 days ago - each note links to its source

Alternatives (1)

  • byparr - Byparr is a self-hosted proxy that fetches URLs through a real browser to help bypass Cloudflare and similar captcha challenges.

Checked 16 days ago - source: AlternativeTo

Common questions

Can flaresolverr-next run JavaScript after solving a page?

Yes, it adds an executeJs request parameter. That lets you run JavaScript on the solved page and return the result.

Which port should be exposed for the proxy?

The Docker example maps host port 8191 to container port 8191.

What resource limitation should I watch when using it?

With each request a new browser is launched. Web browsers consume a lot of memory, so do not make many requests at once on a machine with little RAM.

Why might challenge solving fail in Docker?

Disable or remove proxies and VPNs for FlareSolverr and the client making requests. Disable IPv6 for the host or all relevant Docker containers. If using Docker, make sure all relevant containers are on the host network.

How is the Docker image updated?

The latest image is built on every push to master.

Answers sourced from github.com, github.com

Community

No community discussions collected yet.