what's the pricing for browser-rendering-api, it's really vague
what's the pricing for browser-rendering-api, it's really vague
CCurrently, no pricing, but Workers Paid only (and limited to two browsers concurrent/per minute)
They're working on getting pricing set
They're working on getting pricing set
Tthank you, when do we expect the new pricing to come alive? I just don't want to be surprised with a bill 
CI don't know of any exact date but should be plenty of emails and notification beforehand
Tsounds good. another question, the browser session has a cf physical location right? so if the session was created on the edge in cf-sfo, then when try to use the same session on a worker in dublin, then, the speed will be slow, because the sfo session is trying to access resources in dublin.
Tis my understanding correct?
CThe idea of reusing a session is to avoid the cost of spinning up a new session, so it moving locations wouldn't make sense, would need a new session
Tthank you, makes sense
Pis the beta still going on or is it over?
Pim looking to get access to the browser rendering api
Ranyone get the browser integation working goodwith sessions? etc ?
HAnyone else running into this when trying to use Browser Rendering? Any ideas how to get around it? https://github.com/cloudflare/puppeteer/issues/50
GitHub
Bug description Steps to reproduce the problem: Create worker following the guide here. Try to make a request to the worker. Puppeteer version 0.0.10 Node.js version 20.13.1 npm version 10.5.2 What...
BYeah getting the same, tried older versions and that isn't working either. I assumed they've changed the API?
BYeah have paid plan
BI've tried it before will no problems, not sure whats changed
CCan the browser rendering api load pdfs? I’m interested in grabbing the text in them
Bany updates?
Bit still not working
Bsame everything
BI will give that a go
BYep that works perfectly!
BI guess it was an API change then?
Btry this ^
SI was having the same issue as well. This fixed it.
Sthat's quick! cheers!
took me a minute to realise the version you're referring to is @cloudflare/puppeteer
took me a minute to realise the version you're referring to is @cloudflare/puppeteer
VHello, I have a objective, please help me
To configure automatic protection against DDoS attacks on Cloudflare using firewall rules and rate limiting. This involves detecting suspicious traffic spikes and automatically triggering challenges or blocks to protect the website without manual intervention.
Objective
To configure automatic protection against DDoS attacks on Cloudflare using firewall rules and rate limiting. This involves detecting suspicious traffic spikes and automatically triggering challenges or blocks to protect the website without manual intervention.
IWhy are you asking this in the #browser-rendering-api channel? Does this have anything to do with the browser rendering API?
BIs there any way to control where the worker is deployed? We'd like to have the browser visit a website which has geo specific content, so we'd like to be able to control where the worker is run?
ZYou can probably just check the Region with one of the cf request properties and block every other region
Z
BNot sure where I would apply the blocking you're talking about? You mean I should apply it to the firewall rules of the worker route? Or in some other way make the worker aware that its been run from the wrong region. But then I would need to still try and trigger the worker from an IP which routes to that edge right, (Like going through a vpn)?
HNot really? There is Smart Placement, but I'm not sure how that interacts with #browser-rendering-api, if it does at all...
Rdurable objects ?
CMultiple tabs for each user and DO to keep the browser alive
AHello!, i'm trying to use browser-rendering with puppeteer and cloudflare workers but its giving me this error in dev/deploy, its mandatory to applo for the whitelist of the beta? or do i have to pay the 5 dollars workers subscription in order to use this feature?, im a little bit confused, thanks!
{
text: 'A request to the Cloudflare API
(/accounts/account_id/workers/scripts/browser-test/edge-preview) failed.',
notes: [
{
text: 'workers.api.error.no_access_to_browser_worker [code: 10088]'
}
],
location: undefined,
kind: 'error',
code: 10088
}
{
text: 'A request to the Cloudflare API
(/accounts/account_id/workers/scripts/browser-test/edge-preview) failed.',
notes: [
{
text: 'workers.api.error.no_access_to_browser_worker [code: 10088]'
}
],
location: undefined,
kind: 'error',
code: 10088
}
