same everything

B

bryce•6/9/24, 11:24 AM

I will give that a go

Ssc @bun @bryce Can you set the `compatibility_date` in `wrangler.toml` to `2024-06-...

B

bryce•6/9/24, 3:44 PM

Yep that works perfectly!

B

bryce•6/9/24, 3:44 PM

I guess it was an API change then?

Bbun same everything

B

bryce•6/9/24, 3:44 PM

try this ^

Ssc @bun @bryce Can you set the `compatibility_date` in `wrangler.toml` to `2024-06-...

S

Sinderella•6/10/24, 1:05 AM

I was having the same issue as well. This fixed it.

S

Sinderella•6/10/24, 3:05 PM

that's quick! cheers!
took me a minute to realise the version you're referring to is @cloudflare/puppeteer

V

Valentin•6/11/24, 6:59 AM

Hello, I have a objective, please help me

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.

VValentin Hello, I have a objective, please help me ### Objective To configure automati...

I

Ian•6/11/24, 7:45 AM

Why are you asking this in the #browser-rendering-api channel? Does this have anything to do with the browser rendering API?

B

Bernd•6/11/24, 9:49 AM

Is 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?

BBernd Is there any way to control where the worker is deployed? We'd like to have the ...

Z

Zetax•6/11/24, 9:50 AM

You can probably just check the Region with one of the cf request properties and block every other region

Z

Zetax•6/11/24, 9:51 AM

B

Bernd•6/11/24, 9:51 AM

Not 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)?

BBernd Is there any way to control where the worker is deployed? We'd like to have the ...

H

Hello, I’m Allie!•6/11/24, 10:43 AM

Not really? There is Smart Placement, but I'm not sure how that interacts with #browser-rendering-api, if it does at all...

R

rob•6/11/24, 9:23 PM

durable objects ?

RRahul Only two browser in one minute, how to use in production with 100+ users per min...

C

cj•6/12/24, 6:34 AM

Multiple tabs for each user and DO to keep the browser alive

A

achesui•6/13/24, 7:34 PM

Hello!, 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
}

Sscythe You need the workers subscription

A

achesui•6/13/24, 9:12 PM

Thank you for clarify!

S

Sameer Ali•6/20/24, 6:29 PM

I am trying to create pdf from an html using

const pdf = await page.createPDFStream();

const pdf = await page.createPDFStream();

const pdf = await page.createPDFStream();

const pdf = await page.createPDFStream(); but getting error

Error: Cannot create a stream outside of Node.js environment.

Error: Cannot create a stream outside of Node.js environment.

Error: Cannot create a stream outside of Node.js environment.

Error: Cannot create a stream outside of Node.js environment. even though i have

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

in wrangler.toml
What am I missing?

S

Sameer Ali•6/20/24, 6:33 PM

nvm, i had to change compatibility_date

D

daguang•6/21/24, 8:42 AM

Hello! I am experiencing some issues with the Browser Rendering feature of Workers. Specifically, there is a discrepancy between the
puppeteer.BrowserWorker
puppeteer.BrowserWorker
puppeteer.BrowserWorker
puppeteer.BrowserWorker and the
Fetcher
Fetcher
type generated by
wrangler types
wrangler types
.

Solved. The reason is that my node version too new,
then downgrade @types/node 20.5.7 to solve it, hope fix on the new version

M

MyBuddhaMercy•6/24/24, 8:14 AM

@schello, does support connect to browser like this?

const browser = await puppeteer.connect({
browserWSEndpoint:

wss://chrome.browserless.io/

wss://chrome.browserless.io/

wss://chrome.browserless.io/

wss://chrome.browserless.io/,
});

D

dakom•6/24/24, 12:02 PM

I am sure this has been asked before - but a friend was looking for a simple host for his puppeteer scraper thing... does the free tier of workers support that?

F

f12i•6/26/24, 11:41 PM

Taking screenshots stopped working for us all a sudden today.

We're seeing the worker hang on

page.screenshot(...)

page.screenshot(...)

page.screenshot(...)

page.screenshot(...) call and eventually throw after quite a while.

We're seeing this in the worker logs:

ProtocolError: Protocol error (Page.captureScreenshot): Target closed

ProtocolError: Protocol error (Page.captureScreenshot): Target closed

ProtocolError: Protocol error (Page.captureScreenshot): Target closed

ProtocolError: Protocol error (Page.captureScreenshot): Target closed

We've had no code changes to the worker in the past month.

F

f12i•6/27/24, 7:45 AM

Things started working again with us making no changes about an hour after I posted that message.

N

NamiW•7/1/24, 2:33 AM

quick question: I'm confused by the limitation

Two concurrent browsers per account.

Two concurrent browsers per account.

Two concurrent browsers per account.

Two concurrent browsers per account. . Can I still have >2 concurrent worker instances connect to the same browser instance and open individual pages within each worker?

If yes, then Is there a limitation for how many concurrent workers can connect to the same browser instance?

N

NamiW•7/1/24, 11:02 AM

still confused. please bear with me:MeowHeartCloudflare: . so the bottom line is my worker can handle 10 concurrent request for a screenshot function right? by 1) saving the worker-browser connection in durable object, 2) each worker connect to this durable object and open a new tab

T

TheMightyPenguin•7/3/24, 1:12 AM

Hey all! Are there future plans to support browser rendering locally? Working on an app that uses queues, ai, and browser rendering, and browser rendering is the main friction point for local dev (I could also do remote dev, but queues don’t work on remote dev)

N

NamiW•7/4/24, 5:47 AM

want to report an issue. I'm following the official typescript sample but encountered a type error. this only happens in local dev env (

wrangler dev

wrangler dev

) not in production.

const browser = await puppeteer.launch(env.BROWSER)

Argument of type '{ fetch(input: RequestInfo<unknown, CfProperties<unknown>>, init?: RequestInit<CfProperties<unknown>> | undefined): Promise<Response>; connect(address: string | SocketAddress, options?: SocketOptions | undefined): Socket; }' is not assignable to parameter of type 'BrowserWorker'.
  The types returned by 'fetch(...)' are incompatible between these types.
    Type 'Promise<Response>' is not assignable to type 'Promise<global.Response>'.
      Property 'type' is missing in type 'Response' but required in type

const browser = await puppeteer.launch(env.BROWSER)

Argument of type '{ fetch(input: RequestInfo<unknown, CfProperties<unknown>>, init?: RequestInit<CfProperties<unknown>> | undefined): Promise<Response>; connect(address: string | SocketAddress, options?: SocketOptions | undefined): Socket; }' is not assignable to parameter of type 'BrowserWorker'.
  The types returned by 'fetch(...)' are incompatible between these types.
    Type 'Promise<Response>' is not assignable to type 'Promise<global.Response>'.
      Property 'type' is missing in type 'Response' but required in type

const browser = await puppeteer.launch(env.BROWSER)

Argument of type '{ fetch(input: RequestInfo<unknown, CfProperties<unknown>>, init?: RequestInit<CfProperties<unknown>> | undefined): Promise<Response>; connect(address: string | SocketAddress, options?: SocketOptions | undefined): Socket; }' is not assignable to parameter of type 'BrowserWorker'.
  The types returned by 'fetch(...)' are incompatible between these types.
    Type 'Promise<Response>' is not assignable to type 'Promise<global.Response>'.
      Property 'type' is missing in type 'Response' but required in type

const browser = await puppeteer.launch(env.BROWSER)

Argument of type '{ fetch(input: RequestInfo<unknown, CfProperties<unknown>>, init?: RequestInit<CfProperties<unknown>> | undefined): Promise<Response>; connect(address: string | SocketAddress, options?: SocketOptions | undefined): Socket; }' is not assignable to parameter of type 'BrowserWorker'.
  The types returned by 'fetch(...)' are incompatible between these types.
    Type 'Promise<Response>' is not assignable to type 'Promise<global.Response>'.
      Property 'type' is missing in type 'Response' but required in type

Objective

Similar Threads

Similar Threads

Objective

Similar Threads