puppeteer-extra
puppeteer-extra copied to clipboard
puppeteer-extra does not bypass cloudfare ddos protection
Thank you very much for your work.
I use import puppeteer from 'puppeteer'; I'm getting a cloudfire error with a permanent redirect. Tried headless false, headless true - still redirect.
tried using import puppeteer from 'puppeteer-extra'; import StealthPlugin from 'puppeteer-extra-plugin-stealth';
and this solved the problem in headless false. But if I use headless true, I get a cloudfare redirect again.
After investigating the problem, I found that 'cookie': 'cf_clearance' is not set in headless true But at the same time cf_chl_2 cf_chl_prog - is.
Enable headless false - sets cf_clearance=vPcVJnlOhq6EsUjgYzWhTt0S8iGQIn1IuI_sAxWXlng-1642361020-0-150; hash=rsIsXDMFvkkL9poXMtIRutCAWPdBWsRg
Thank you very much for the future solution of the problem. I think everyone who parses sites with cloudfare protection has this problem now
System: OS: macOS 12.0.1 CPU: (8) x64 Apple M1 Memory: 33.10 MB / 8.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 14.17.1 - /usr/local/bin/node npm: 6.14.13 - /usr/local/bin/npm npmPackages: puppeteer: ^12.0.1 => 12.0.1 puppeteer-extra: ^3.2.3 => 3.2.3 puppeteer-extra-plugin-adblocker: ^2.12.0 => 2.12.0 puppeteer-extra-plugin-stealth: ^2.9.0 => 2.9.0
Any progress? I'm ready to help.
Any progress? I'm ready to help.
yes, i still struggle with problem
I'm being detected on Heroku (with no solution so far), but not on my home network, so maybe IP could have to do with it? Are you on residential IP?
I'm being detected on Heroku (with no solution so far), but not on my home network, so maybe IP could have to do with it? Are you on residential IP?
I'm using my home internet and residential proxy, detected on both of them
I'm being detected on Heroku (with no solution so far), but not on my home network, so maybe IP could have to do with it? Are you on residential IP?
I'm using my home internet and residential proxy, detected on both of them
+1 I'm the same...
@kossykhalexandr I got the same issue recently, do you have new idea?
In your comment Enable headless false - sets cf_clearance=vPcVJnlOhq6EsUjgYzWhTt0S8iGQIn1IuI_sAxWXlng-1642361020-0-150; hash=rsIsXDMFvkkL9poXMtIRutCAWPdBWsRg
means if I want to use headless:true, should I set up cf_clearance
in cookie? Thank you for your response.
Any progress about this ? I'm still having the same issue
I am having the same issue. The page never shows any captcha to solve, just stays where it says "Checking for your connection". I have tried several thing like adding the --disable-web-security (worked for me in the past) but as it for today I can't access the page.
We need to switch proxies constantly to solve this problem. Residential IP doesn't help so much in my experience.