Self-host FlareSolverr with Levelrail

A headless-browser proxy that solves Cloudflare and DDoS-Guard challenges for other self-hosted tools.

  • AuthorFlareSolverr
  • LicenceMIT
  • Memory512 MiB
  • Archarm64
  • Services1

How to self-host FlareSolverr

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/flaresolverr/flaresolverr:v3.5.0
  2. Create the app

    One service starts in a single Compose app, on port 8191.

  3. Fill in the secrets

    2 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

FlareSolverr requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
8191
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 8191 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then FlareSolverr. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the FlareSolverr docs page.

Deploy FlareSolverr your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy FlareSolverr from the CLI

levelrail-cli templates deploy flaresolverr --name my-flaresolverr

Deploy FlareSolverr with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/flaresolverr/deploy

FlareSolverr configuration

FlareSolverr services

ServiceImagePortsVolumes
flaresolverr ghcr.io/flaresolverr/flaresolverr:v3.5.0 8191 none

FlareSolverr environment variables

VariableServiceValue
LOG_LEVEL flaresolverr Preset by the template
TZ flaresolverr Preset by the template

Ports and volumes

Ports
8191
Volumes
none

FlareSolverr FAQ

How much memory does FlareSolverr need?

The catalog lists about 512 MiB of memory for FlareSolverr.

Does FlareSolverr run on arm64?

For FlareSolverr, an arm64 image is published; amd64 is image published.

What licence is FlareSolverr under?

FlareSolverr is licensed under MIT, which is permissive, with few conditions on reuse.

Does FlareSolverr need configuration before it starts?

No. The template fills in its own defaults.

Which ports does FlareSolverr use?

FlareSolverr listens on port 8191 inside the stack.

Can I deploy FlareSolverr on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id flaresolverr for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/flaresolverr/flaresolverr:v3.5.0 is what you deploy there.

levelrail-cli templates deploy flaresolverr --name my-flaresolverr