Cloudflare Developers•2y ago

Didn't need that on local puppeteer weirdly

ConnerOP•5/23/24, 8:37 PM

@Ian Thanks so much for your help
True hero

CConner Didn't need that on local puppeteer weirdly

Ian•5/23/24, 8:39 PM

Most likely it's doing something like using your local chrome which has slightly different settings or whatever.

Ian•5/23/24, 8:40 PM

If you really want to do a clean room test, run it locally inside Docker.

ConnerOP•5/23/24, 8:44 PM

Ah it works, so good to go haha

ConnerOP•5/23/24, 8:45 PM

Walkme probably didn't like some headers that the headless browser was sending

ConnerOP•5/23/24, 8:45 PM

Until I set those things

eric•5/27/24, 10:30 AM

Hey! Is the render api still in private beta? I've signed up on the page, but the workers docs doesn't mention ıt anywhere. Keep getting the workers.api.error.no_access_to_browser_workerworkers.api.error.no_access_to_browser_worker, so I'd assume so!

Wwingeva Can cloudflare@puppeteer be used together with puppeteer-extra?

Dan Claroni•5/28/24, 10:05 PM

did you ever get an answer to this?

JJosiah Bryan I was able to get this code all approved to be shared: https://gist.github.com/j...

Advany•5/29/24, 7:32 AM

You are awesome!!!!

sam.parry•5/29/24, 8:49 AM

Super excited to get browser rendering live for our use case!

When did it come out of invite only?

I've done some testing locally, and all is working awesome. I have a question regarding fonts though, when I generate a screenshot it is generating with a rather ugly system font (perhaps windows / linux default?)

Is there any way we can configure the default font? Ideally to use something neurtral and clean like Helvetica or San Fransisco?

Google Fonts seem to work well, but wondering if there is a built in approach?

Dan Claroni•5/29/24, 6:07 PM

Does anyone have any experience getting past security on API requests using puppeteer on workers? I can easily get past it with this code using AWS Lambda, but I cant seem to get around this using the cloudflare workers implementation:

code:

const [page] = await browser.pages();

// Hijack browser navigation and instead send requests.
await page.setRequestInterception(true);
page.once('request', async (interceptedRequest) => {
    const headers = {};
    // eslint-disable-next-line @typescript-eslint/no-explicit-any
    request.headers.forEach((v, k) => ((headers as any)[k] = v));
    interceptedRequest.continue({
        method: request.method,
        postData: requestBody,
        headers,
    });

    await page.setRequestInterception(false);
});

// Trigger the requests
const response = await page.goto(request.url);

const [page] = await browser.pages();

// Hijack browser navigation and instead send requests.
await page.setRequestInterception(true);
page.once('request', async (interceptedRequest) => {
    const headers = {};
    // eslint-disable-next-line @typescript-eslint/no-explicit-any
    request.headers.forEach((v, k) => ((headers as any)[k] = v));
    interceptedRequest.continue({
        method: request.method,
        postData: requestBody,
        headers,
    });

    await page.setRequestInterception(false);
});

// Trigger the requests
const response = await page.goto(request.url);

I keep getting 403's with the site giving me a generic Sorry, you have been blockedSorry, you have been blocked error page

TTTT•5/30/24, 12:32 AM

what's the pricing for browser-rendering-api, it's really vague

TTTTT what's the pricing for browser-rendering-api, it's really vague

Chaika•5/30/24, 2:07 AM

Currently, no pricing, but Workers Paid only (and limited to two browsers concurrent/per minute)
They're working on getting pricing set

CChaika Currently, no pricing, but Workers Paid only (and limited to two browsers concur...

TTTT•5/30/24, 2:29 AM

thank you, when do we expect the new pricing to come alive? I just don't want to be surprised with a bill

Chaika•5/30/24, 2:30 AM

I don't know of any exact date but should be plenty of emails and notification beforehand

TTTT•5/30/24, 2:36 AM

sounds 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.

TTTT•5/30/24, 2:36 AM

is my understanding correct?

TTTTT sounds good. another question, the browser session has a cf physical location ...

Chaika•5/30/24, 3:06 AM

The 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

CChaika The idea of reusing a session is to avoid the cost of spinning up a new session,...

TTTT•5/30/24, 3:28 AM

thank you, makes sense

Paradox_77•6/5/24, 6:53 AM

is the beta still going on or is it over?

Paradox_77•6/5/24, 6:53 AM

im looking to get access to the browser rendering api

rob•6/7/24, 1:34 AM

anyone get the browser integation working goodwith sessions? etc ?

hmnd•6/7/24, 7:09 AM

Anyone 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]: Invalid URL `/v1/acquire` thrown from `PuppeteerWorkers.laun...

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...

Hhmnd Anyone else running into this when trying to use Browser Rendering? Any ideas ho...

bryce•6/7/24, 7:06 PM

Yeah getting the same, tried older versions and that isn't working either. I assumed they've changed the API?

Sscythe Working for me with those exact versions (mac os). Do you have workers paid plan...

bryce•6/7/24, 9:34 PM

Yeah have paid plan

bryce•6/7/24, 9:34 PM

I've tried it before will no problems, not sure whats changed

Chief•6/8/24, 5:30 PM

Can the browser rendering api load pdfs? I’m interested in grabbing the text in them

bun•6/9/24, 5:53 AM

any updates?

bun•6/9/24, 5:53 AM

it still not working

Hhmnd Anyone else running into this when trying to use Browser Rendering? Any ideas ho...

bun•6/9/24, 5:53 AM

same everything

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-...

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

Yep that works perfectly!

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

I guess it was an API change then?

Bbun same everything

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

try this ^

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

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

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

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

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...

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?

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 ...

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

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

const [page] = await browser.pages(); // Hijack browser navigation and instead send requests. await page.setRequestInterception(true); page.once('request', async (interceptedRequest) => { const headers = {}; // eslint-disable-next-line @typescript-eslint/no-explicit-any request.headers.forEach((v, k) => ((headers as any)[k] = v)); interceptedRequest.continue({ method: request.method, postData: requestBody, headers, }); await page.setRequestInterception(false); }); // Trigger the requests const response = await page.goto(request.url);

Didn't need that on local puppeteer weirdly

Objective

Similar Threads

Similar Threads

Objective

Similar Threads