Open Slasar41 opened 1 month ago
Hello,
Thank you for this very well-explained guide!
Is there a possibility to use flaresolverr hosted on Docker?
I apologize if this question requires opening a new issue.
Thanks again 🙏
Sorry, I don't use Docker.
Is there a possibility to use flaresolverr hosted on Docker?
I tried out using a Docker and it did work in the end. I had to make sure the docker was hosting through the vm into the host machine so the cloudflare bypass could correctly connect to it through localhost.
Even though it does work I realised it does take a lot longer per connection and will generally timeout with the default 60s when connecting to the docker instead of the .exe or cmd run python which roughly takes ~20s.
Preparation
{FMD Directory}\lua\websitebypass
and rename it touse_webdriver
with no extenstionMethod 1: FlareSolverr (64-bit only)
requests
withpip install requests
{FMD Directory}\lua\websitebypass
{FMD Directory}\lua\websitebypass\flaresolverr\flaresolverr.exe
flaresolverr.exe
and wait for it to sayServing on http://0.0.0.0:8191
200 OK
responseTo test if everything is working properly, run in CMD or Powershell from your
{FMD Directory}\lua\websitebypass
directory the following command:python customcloudflare.py "https://dragontea.ink"
to see if any errors pop up or notMethod 1a: FlareSolverr Fork (64-bit only)
<> Code
in green button and clickDownload ZIP
. The current working fork is herepython src/flaresolverr.py
Method 2: rookiepy
rookiepy
withpip install rookiepy
Chrome, Edge, Firefox, Opera, Opera GX
Please make sure FlareSolverr is running.
Options -> Websites -> Advanced
and search for your site to see if cookies were applied correctly* Currently has issues decrypting cookies from Chrome and doesn't work. Use an alternative browser until the issue is fixed
To test if everything is working properly, run in CMD or Powershell from your
{FMD Directory}\lua\websitebypass
directory the following command:python cloudflare.py "https://dragontea.ink"
to see if any errors pop up or notManual workaround For Chromium based browser
F12
-> selectNetwork
tabName
section, select the first one -> seeHeaders
tab and search forcookie
anduser-agent
, copy all of itOptions -> Websites -> Advanced -> {Website Name}
, changeEnabled
option toTrue
, paste thecookie
anduser-agent
from browser