cresdock
Home Apps Deploy Pricing
Cresdock  /  Apps  /  FlareSolverr
Media automation

How to set up FlareSolverr without Docker

Helps Prowlarr and Jackett reach sites that sit behind Cloudflare. Cresdock runs it on a server you own, from a catalogue, with no Docker and no reverse proxy to configure.

What Cresdock does for you with FlareSolverr

Why run FlareSolverr yourself

The whole point of these tools is that they run unattended. On a desktop that gets shut down, they simply miss things.

What kind of server FlareSolverr needs

These are small, patient programs. They spend most of their time asleep and wake up to check for something new, so 1 GB of memory covers several of them at once. What they need is to be running when you aren't watching.

Cresdock itself is undemanding — it runs on a small rented server, an old desktop or a mini PC, on Ubuntu or Debian. Everything it installs shares that machine, so the honest question is not "will this app run" but "how much am I going to put on here in total".

Where to run FlareSolverr

FlareSolverr runs wherever Cresdock runs, and the choice is about the machine, not the app:

Installing FlareSolverr

  1. Put Cresdock on a server

    One line on any Ubuntu or Debian machine — a rented VPS, a spare PC, a home server. It sets itself up.

  2. Pick FlareSolverr from the catalogue

    Click Install. The panel pulls the image, writes the configuration, gets a certificate and starts it.

  3. Open it from your dashboard

    Its address and any login details are on its card. Start, stop, update, roll back or remove it from the same place, any time.

What this replaces

Doing it by hand means writing something like this, then keeping it working:

services:
  flaresolverr:
    image: ghcr.io/flaresolverr/flaresolverr:v3.5.0
    restart: unless-stopped
    ports:
      - "8191:8191"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - ./flaresolverr/config:/config

And that is the easy half. Still to do:

On Cresdock, FlareSolverr is one click and none of the above exists.

Common questions

Do I need to know Docker to run FlareSolverr?

No. Cresdock installs FlareSolverr in one click from its catalogue: it pulls the image, writes the configuration, gets an HTTPS certificate and starts it. FlareSolverr's configuration is written before it first starts, so it opens already set up.

What happens to my FlareSolverr data when it updates?

Cresdock updates the FlareSolverr image and leaves its stored data in place. FlareSolverr keeps its own files in its own folder, which survives an update, a rebuild and a reinstall — and Cresdock never writes into it.

Can I run FlareSolverr at home instead of on a VPS?

Yes. Cresdock runs on a mini PC, an old desktop or anything that boots Debian, behind a normal home router with no port forwarding, and FlareSolverr is reachable on your own network first. A rented server is only needed when FlareSolverr must be reachable from anywhere without a VPN.

Can I remove FlareSolverr later?

Yes. Cresdock removes FlareSolverr in one click, and asks whether to keep its configuration for a future reinstall. Nothing else you have installed is affected.

Looking for what FlareSolverr itself can do? That lives in its own documentation — this page is only about running it.

Pairs well with: Jackett  ·  Lidarr  ·  FreshRSS  ·  how FlareSolverr connects to your other apps

Before you start: where to rent a server  ·  what it needs to run  ·  Cresdock vs QuickBox  ·  the seedbox panel in full  ·  sell workspaces to your customers