1) Request the wishes of the website and don't take the screenshot 2) How exactly are they blocking
1) Request the wishes of the website and don't take the screenshot
2) How exactly are they blocking you?
2) How exactly are they blocking you?
DCloudflare antibody firewall
JI'm not sure you are going to get many tips about how to circumvent Cloudflare's Firewall on the Cloudflare Discord... 
YThere's no new code. I just pull the repo and did
npm install. I checked that I had a compatible version of node set, but it still didn't work.JCan someone explain how this works in CF's distributed network? When a browser is started, is it only in a single location? If I wanted browsers in multiple locations, how would I handle that?
PHey jason! Currently it is started on a single location, we'll be adding support for Geolocation, so that for example the content rendered might change according to the location where connection is initiated
JThanks as always @Pedro
J@Pedro Another question... one of the things that excites me most about this project is the hope of scalability. When I've run puppeteer myself on my servers, the challenge that I've always run into it trying to handle scaling it up. Trying to throttle requests to not start too many processes and run the server out of memory, etc. Is one of the goals of this project actually to be able to solve that?
Is this eventually going to work like other Workers do, where I don't need to care about how many requests I throw at it? Or am I going to have to implement all of the throttling code anyways - but now with the limitation that I can't see what's going on inside the server?
Is this eventually going to work like other Workers do, where I don't need to care about how many requests I throw at it? Or am I going to have to implement all of the throttling code anyways - but now with the limitation that I can't see what's going on inside the server?
PGreat question! We'll be providing a simple way to reuse sessions and keeping them open, so you can focus on the task at hand. We'll still be setting default limits, mostly to prevent abuse and malicious behaviour, but those can be raised according to you use case
JThanks. Another way to ask the question. Let's say that I have 1000 urls to crawl. Am I going to need to do the work to manually distribute those requests over multiple sessions, throttle them to not send too many at a time, etc? With a normal worker that doesn't use the browser rendering, I would just POST all 1000 requests as fast as possible to my worker and not worry about it. But I suspect with the browser rendering, I wouldn't be able to do that.
PYou can choose to reuse the same session (until expired) to crawls the URLs sequentially or you can choose to create concurrent sessions. It's basically up to you. We're providing an easier way to reuse the sessions, but the "puppeteer" behaviour is still up to you to define, so it's flexible enough to accommodate most use cases. (You can already reuse the same session for multiple URLs using Durable Objects as per the tutorial, we're making it easier)
JAre you saying that a single session can handle one request at a time? So if I wanted to do 1000 requests in parallel, I would need to start 1000 separate sessions?
PYou can use the same session for multiple tasks like crawling multiple URLs. But if you want to do things in parallel, you just create new concurrent sessions. It's like running a Browser and doing the tasks or Multiple Browsers at the same time and performing multiple task in each one at the same time. Hope I was clear enough 
JYep, I think I understand. 
And I think it means that it's not going to have the worker-level scalability that I hoped it would. At least not without costing a fortune. Thanks for the information!
And I think it means that it's not going to have the worker-level scalability that I hoped it would. At least not without costing a fortune. Thanks for the information!PWould love to learn more about your use case. Please feel free to ping me and let's make sure we have an offer that also suits more specific and demanding use cases such as yours
JDid you post in #Browser Rendering API Beta Access ? It’s usually within 24 hours.
KDoes this API work in dev? I'm not seeing any indication that it shouldn't but when calling a method that works in prod I'm getting
Could not start browser instance. Error: TypeError: Cannot read properties of undefined (reading 'fetch')
Cuhm, does this api work for Pages? 
JYou need to use
wrangler dev --remote@sc Hello! Did you have the chance to run the Puppeeteer fork locally? Thank you. 
YThank you!
PHey! You can use DOs, regardless of using one session or multiple concurrent sessions. Basically, using DOs allows you to reuse the same session by keeping it open longer, thus if you don't have the need to crawl or execute commands in parallel, one session should be enough. If you have the need to execute commands in parallel, then you can open new "concurrent" sessions
EYou can request access in browser-rendering-apiBrowser Rendering API Beta Access
EAnd you can see in the chat history that it doesnt take too long
EI don't see a message from you in that thread
MDoes cloudflare puppeteer support setting proxy?
Pfacing the error
Dynamic require of "node:stream" is not supported How to use head mode when debugging locally ?
FI just got access to the browser rendering API and I can't seem to get it to work. The response from puppeteer.launch(...) is null and I see a "Unabled to create new browser: code: 429: message: Too many browsers already running". I am running just this one instance for testing, is the system currently overloaded?
FWell, it just started working. It was some transient issue.
WHi, Cloudflare staff
WWhen I use local Node.js Puppeteer to access the website https://help.openai.com/en/articles/7102672-how-can-i-access-gpt-4, all content can be fully loaded. However, when using Cloudflare Browser Render to access it, not all content can be loaded, only some JavaScript scripts. What could be the reason for this?
WThis the local Node.js Puppeteer code:
WThis the worker code
YThank you. I'll try again with node 18 (although I think this is what I used the first time, but no harm in checking)
GHey folks, how can I avoid issues like this, for Google eg, whiel trying to screenshot, using the browser rendering API
G
AHi, how can I get access?
V
JIt's unlikely that you are going to be able to, or at least find support here for how to. You have to convince reCaptcha, that you aren't a bot... but since you are, you might have a hard time doing that.
GI believe there is a puppeteer stealth plugin, which I'd love an integration wtih. Not an ace programmer, so please bear with me.
Gnpm
Stealth mode: Applies various techniques to make detection of headless puppeteer harder.. Latest version: 2.11.2, last published: a year ago. Start using puppeteer-extra-plugin-stealth in your project by running
npm i puppeteer-extra-plugin-stealthFor the same browser instance, if users in different countries request and execute page actions, are the exit IP addresses through the page the same?
MWhat determines the IP of the browser? Is it possible that the IP of the same browser instance in different contexts or pages is different?
