Unable to bypass bot check

[Crease29]

Description

This tool is not able to bypass bot check pages like on primedice.com anymore. It has also hit other projects, as Cloudflare seems to have made adjustments. Also it seems like this project is no longer maintained? Are there any reliable alternatives? Very unfortunate that this project is no further maintained.

Full steps to reproduce the issue

Try to pass the cloudflare bot check on primedice.com.

Issue Type

Bug

Operating System

Linux

Do you use Docker?

Docker

[iamyegor]

Have you found a solution?

[Crease29]

Have you found a solution?

I'm using FlareSolverr in combination with flaresolverr-mitm-proxy now.

[iamyegor]

Thank you for the recommendation, I'll definitely try that out. But don't you find it strange that Flaresolver was last updated 2 months ago and still works for you despite the recent Cloudflare patch?

[Crease29]

Thank you for the recommendation, I'll definitely try that out. But don't you find it strange that Flaresolver was last updated 2 months ago and still works for you despite the recent Cloudflare patch?

To be fair I don't know what the differences are between the two. From my experience a little difference in the browser fingerprint can play a big role when passing the Cloudflare challenge.

[iamyegor]

Sadly, Flaresolver didn't work for me, so I'll search for alternatives. I may drop a link here if I find something.

[Crease29]

Sadly, Flaresolver didn't work for me, so I'll search for alternatives. I may drop a link here if I find something.

Feel free to drop your discord or telegram, we may be able to exchange some ideas

[kacybennett]

@iamyegor @Crease29 were y'all able to figure out a resolution for this? I am in the same boat.

[iamyegor]

@kacybennett You can try my solution: Unflare, or if it doesn't work for you, try this docker image instead: alexfozor/flaresolverr:pr-1300-experimental, here's the example docker compose for it:

services:
  flaresolverr:
    image: alexfozor/flaresolverr:pr-1300-experimental
    container_name: flaresolverr
    environment:
      - LOG_LEVEL=${LOG_LEVEL:-info}
      - LOG_HTML=${LOG_HTML:-false}
      - CAPTCHA_SOLVER=${CAPTCHA_SOLVER:-none}
      - TZ=Europe/London
    ports:
      - "${PORT:-8191}:8191"
    restart: unless-stopped

As far as I understand this image is compatible with the original FlareSolverr settings

[kacybennett]

@kacybennett You can try my solution: Unflare, or if it doesn't work for you, try this docker image instead: alexfozor/flaresolverr:pr-1300-experimental, here's the example docker compose for it:

services:
flaresolverr:
image: alexfozor/flaresolverr:pr-1300-experimental
container_name: flaresolverr
environment:
- LOG_LEVEL=${LOG_LEVEL:-info}
- LOG_HTML=${LOG_HTML:-false}
- CAPTCHA_SOLVER=${CAPTCHA_SOLVER:-none}
- TZ=Europe/London
ports:
- "${PORT:-8191}:8191"
restart: unless-stopped
As far as I understand this image is compatible with the original FlareSolverr settings

I plan on using your solution Unflare. So I would just run it in a Docket container and then utilize the API for my browser automation?

[iamyegor]

Unflare simply scrapes the CF clearance token from the webpage you’re trying to access. It doesn’t offer any kind of API for browser automation. It’s similar to cf-clearance-scraper, which is the project where this discussion is taking place.