The trackers that hide behind Cloudflare, answered. A tracker behind Cloudflare shows every visitor a challenge page first, and a search engine, which is not a browser, gets that page instead of results. This package is FlareSolverr as a QPKG: a real Chromium on this NAS that opens the page, passes the challenge and hands the cookie to the search engine. Until now it meant Container Station and a docker line.
Nothing to set up: install it beside Rtorrent 16 Search and the search add-on finds it on the loopback interface by itself at the next sync; the sources Cloudflare had stopped come back on. Inside: FlareSolverr 3.5.2 (upstream's own build) with its Chromium 153, the matching driver, a virtual display (Xvfb) and four DejaVu faces, everything a browser needs and QTS lacks. x86_64 only (upstream builds the bundle for x64 alone). About 800 MB on the volume; around 100 MB of RAM while it waits and up to 1.4 GB for the ten seconds a challenge is being solved (a real Chromium), so a NAS with 4 GB or less will feel that moment.
Nothing to set up: install it beside Rtorrent 16 Search and the search add-on finds it on the loopback interface by itself at the next sync; the sources Cloudflare had stopped come back on. Inside: FlareSolverr 3.5.2 (upstream's own build) with its Chromium 153, the matching driver, a virtual display (Xvfb) and four DejaVu faces, everything a browser needs and QTS lacks. x86_64 only (upstream builds the bundle for x64 alone). About 800 MB on the volume; around 100 MB of RAM while it waits and up to 1.4 GB for the ten seconds a challenge is being solved (a real Chromium), so a NAS with 4 GB or less will feel that moment.
Install
Add the QNAP Utilities repository to App Center once, then install it from there: how to add the repository.What you can do
- Pass Cloudflare challenges with a real Chromium on the NAS
- Bring back the sources Cloudflare had stopped
- Let the Search add-on find it at its next sync, with nothing to set up
- See on the Trackers page whether the solver is on