Open joeledwardson opened 9 months ago
Try using the start-up tab and see if it works. We have more info on this problem here: https://github.com/berstend/puppeteer-extra/issues/832
I am now recently (within last two weeks) seeing the exact same thing. Using the start-up tab doesn't seem to make a difference.
@krkeegan @joeledwardson @NodePuppeteer @peterblazejewicz @bclougherty
I am now recently (within last two weeks) seeing the exact same thing. Using the start-up tab doesn't seem to make a difference.
I had luck up until now. Now, anything that is protected by Cloudflare, simply doesn't let me do anything... even if I solve captcha myself... it continues spinning, or reporting that I've failed to pass the test as human being.
Is there anyone that had luck resolving this issue?
I am now recently (within last two weeks) seeing the exact same thing. Using the start-up tab doesn't seem to make a difference.
I had luck up until now. Now, anything that is protected by Cloudflare, simply doesn't let me do anything... even if I solve captcha myself... it continues spinning, or reporting that I've failed to pass the test as human being.
Is there anyone that had luck resolving this issue?
https://medium.com/@zfcsoftware/how-to-bypass-cloudflare-with-node-js-869fa6e21dd5
Friend, your article is absolutely wrong... You completely do not understand the cause of this issue. Please stop spamming these threads.
Friend, your article is absolutely wrong... You completely do not understand the cause of this issue. Please stop spamming these threads.
The article is about passing Cloudflare. 2 pieces of code are given. Both can easily pass including the corporate plan. Which part is wrong? I am trying to convey a source because they constantly say that we cannot pass Cloudflare. Explain the wrong part and let's learn together. Also, I'm not spamming. My first message was to link a github discussion. It has nothing to do with me and there are dozens of people in that discussion. I am waiting for you to explain what is wrong.
i had this issue, some website have more advanced scraper detection. The solution was to use a proxy residential service like brightdata, and pass the proxy args to pupeteer.
const BROWSER_CONFIG: PuppeteerLaunchOptions = {
headless: 'new',
defaultViewport: null,
ignoreHTTPSErrors: true,
args: ['--proxy-server=xxxx:xxxx'],
};
const browser = await puppeteer.launch(BROWSER_CONFIG);
const page = (await browser.pages())[0];
await page.authenticate({
username: 'xxxxx',
password: 'xxxxxx',
});
I have not queried or clicked anything using puppeteer, simply connected to the browser seems enough for cloudflare to block access to a site.
I have used the simplest possible example in puppeteer with a real browser (no headless) and no automation scripts.
I have replicated this without puppeteer and clicking on the cloudflare verification button I pass through to the website, which means I suspect that somehow they are able to detect Puppeteer?
The video below shows manual clicking but cloudflare refuses access:
https://github.com/berstend/puppeteer-extra/assets/25906558/973501b3-25e5-40a4-98ad-888315930b4b
I have also replicated this on android, forwarding the port to chrome dev tools via ADB and connected to the debugging port and experience the same result.
For mobile, I:
adb forward tcp:9000 localabstract:chrome_devtools_remote