Hi, how can I get access? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

andycyz

Aandycyz Hi, how can I get access?

Vero

V

Vero•2/28/24, 12:45 PM

Hey, drop your account ID in the thread browser-rendering-apiBrowser Rendering API Beta Access

gauravwagmi

Ggauravwagmi Hey folks, how can I avoid issues like this, for Google eg, whiel trying to scre...

jason

J

jason•2/29/24, 5:21 AM

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

gauravwagmi

G

gauravwagmi•2/29/24, 10:08 AM

I believe there is a puppeteer stealth plugin, which I'd love an integration wtih. Not an ace programmer, so please bear with me.

gauravwagmi

G

gauravwagmi•2/29/24, 10:08 AM

https://www.npmjs.com/package/puppeteer-extra-plugin-stealth

npm

puppeteer-extra-plugin-stealth

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-stealthnpm i puppeteer-extra-plugin-stealth. There are 523 other projects in the npm registry using puppeteer-extra-plugin-stealth.

MyBuddhaMercy

M

MyBuddhaMercy•3/5/24, 3:34 PM

For the same browser instance, if users in different countries request and execute page actions, are the exit IP addresses through the page the same?

MyBuddhaMercy

M

MyBuddhaMercy•3/5/24, 3:37 PM

What determines the IP of the browser? Is it possible that the IP of the same browser instance in different contexts or pages is different?

MyBuddhaMercy

MMyBuddhaMercy For the same browser instance, if users in different countries request and execu...

jason

J

jason•3/5/24, 4:02 PM

Once you start a session, the browser remains in that location until it's closed. Your cannot move the browser to different locations. I'd imagine that the browser is opened in a location close to the request that it was opened; though I don't know that for sure.

gauravwagmi

G

gauravwagmi•3/6/24, 2:48 PM

Hey folks, is there a way we can increase these limits? I'd love to have ~5 a minute. https://developers.cloudflare.com/browser-rendering/platform/limits/ Maybe @Vero

can help?

Cloudflare Docs

Limits · Browser Rendering docs

The Workers Browser Rendering API is currently in beta. Add yourself to the waitlist to reserve your spot, and as we expand availability, we will …

Isaac McFadyen

I

Isaac McFadyen•3/6/24, 7:04 PM

?pings

Flare

F

Flare•3/6/24, 7:04 PM

Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.

gauravwagmi

Ggauravwagmi Hey folks, is there a way we can increase these limits? I'd love to have ~5 a mi...

Vero

V

Vero•3/7/24, 5:00 PM

Hey, not sure if those limits can be increased but I've asked internally

gauravwagmi

Ggauravwagmi Hey folks, is there a way we can increase these limits? I'd love to have ~5 a mi...

Vero

V

Vero•3/7/24, 5:30 PM

and they just told me that Browser Rendering limits can't be increased currently

Ilmerainen

I

Ilmerainen•3/8/24, 5:58 PM

Hey!
Is there a way to set userDataDir in puppeteer.launch()?

Ilmerainen

IIlmerainen Hey! Is there a way to set userDataDir in puppeteer.launch()?

jason

J

jason•3/11/24, 2:03 PM

I would imagine not.

vikiival | koda.art

Vvikiival | koda.art I am trying to make this via cloudflare workers. But sadly WebGL does not work i...

Deep

D

Deep•3/18/24, 9:08 PM

hey did you ever make some progress on this? i'm doing the same thing for my app.... using 3JS to render some 3D and was even considering setting up my own GPU servers around the US to do my own "edge" rendering.... but would prefer to use cloudflare instead. but, in my research so far the WebGPU support and the browser rendering both don't really have a "real-time 3D rendering" feature as far as i can tell.....

Dobroslav

D

Dobroslav•3/20/24, 6:12 PM

Thanks for the access. Is there some roadmap for the full release and increasing rate limits? Current rate limits are not usable, if I want to build product around it.

Or if there is a way to increase these limits, while API is in beta, I would really appreciate it.

Also, is there some pricing available yet?

Thanks!

Dobroslav

DDobroslav Thanks for the access. Is there some roadmap for the full release and increasing...

jason

J

jason•3/20/24, 7:29 PM

They've published pricing here: https://blog.cloudflare.com/running-serverless-puppeteer-workers-durable-objects

slusatel

S

slusatel•3/21/24, 4:19 PM

Whats the best approach for handling SSR with browser rendering, mostly for SEO/social links preview. Would it be Pages middleware that catches and renders pages if bot, and forward the original html if not?
I saw an article somewhere cloudflare already has a similar service, but can't find

Wrapper

W

Wrapper•3/22/24, 9:40 AM

Cloud I get access for browser API please:

cd3066af0931b7b92c5a9dcbb387779d

Sam

S

Sam•3/25/24, 2:54 PM

Just wanted to +1 some of the pricing comments - the idea of having a durable object constantly keeping itself alive in order to avoid creating browser sessions seems very strange. I feel I'm in a weird valley of not having consistent-enough traffic to warrant keeping a durable object alive (though I don't know the cost of that on its own), but I'll also probably have >500 requests that need a browser per month at some point. $0.10/session is still very kind pricing, but compared to D1/Workers/KV/R2/etc it seems like a lot (my use case is just PDF generation).

rob

R

rob•3/25/24, 6:33 PM

is there any support for using proxys on the browser rendering api ?

Wrapper

WWrapper Cloud I get access for browser API please: cd3066af0931b7b92c5a9dcbb387779d

jason

J

jason•3/27/24, 8:40 PM

You should post in #Browser Rendering API Beta Access

Sam

SSam Just wanted to +1 some of the pricing comments - the idea of having a durable ob...

jason

J

jason•3/27/24, 8:41 PM

There is supposed to be an update coming regarding better session mangement - hopefully some of these concerns will be addressed.

villainy

V

villainy•3/28/24, 6:59 PM

Is it possible, if so has anyone tried using the puppeteer fork together with puppeteer-extrapuppeteer-extra ?

Y

ye•4/1/24, 6:32 AM

has anyone had trouble with the reusing session sample code on https://developers.cloudflare.com/browser-rendering/get-started/reuse-sessions/ ?

Usually the first load works fine as it uses a new session, but if i refresh/etc it doesn't use the old session and instead creates a new session and eventually hits the session limit

I'm creating the second request when the image is returned and the browser is disconnected

Cloudflare Docs

Reuse sessions · Browser Rendering docs

The best way to improve the performance of your browser rendering worker is to reuse sessions. One way to do that is via Durable Objects. Another way …

Advany

A

Advany•4/2/24, 10:24 AM

How many resources does a session have? I just tried to do 100 pdf generations with one session (opened 100 pages, loaded content, generated pdf). It did then without any issues?

Advany

A

Advany•4/2/24, 10:25 AM

How do I know when I am sending to many resources so I can apply some rate limits

Ssc If you consume too much memory, the browser session will crash. You can look at ...

Advany

A

Advany•4/2/24, 5:46 PM

Awesome. Is there a way to force the browser to crash

Advany

A

Advany•4/3/24, 11:39 AM

I just want to see if my test setup can 'catch' it

Would It just throw an error by puppeteer?

zegevlier

Z

zegevlier•4/3/24, 2:47 PM

Are there any plans to support WebGL in browser rendering? I was trying to automate taking screenshots of 3d models using (Blockbench)[https://web.blockbench.net/], but it gave an error regarding creating a WebGL context.

zegevlier

Z

zegevlier•4/3/24, 2:47 PM

FWIW you get the same error when trying to use RBI to access blockbench.

GenieTheGamer

G

GenieTheGamer•4/3/24, 7:42 PM

Is there a time limit or an inactive time limit for the beta access? I requested access a month ago and got it, but haven't had a chance to work with the browser api. I finally got a chance to work on it, but I'm still getting an authentication error

GenieTheGamer

G

GenieTheGamer•4/3/24, 7:46 PM

^Nevermind, I was signed into a different account in my terminal

Ssc If you consume too much memory, the browser session will crash. You can look at ...

Advany

A

Advany•4/4/24, 5:51 AM

I just discovered the easy way to manage sessions

didnt know about reusing sessions

Advany

A

Advany•4/4/24, 9:43 AM

I rewrote the logic for getting session for anyone doing the same. It first tries to connect to a existing session, if that isn't available (anymore), it tries to launch one.

async function getSession(browser) {
    const sessions = await puppeteer.sessions(browser);
    console.log(`getSession: sessions - ${JSON.stringify(sessions)}`);
    const sessionsIds = sessions
        .filter((v) => {
            return !v.connectionId;
        })
        .map((v) => {
            return v.sessionId;
        });

    console.log(`getSession: Available sessionsIds - ${JSON.stringify(sessionsIds)}`);

    if (sessionsIds.length !== 0)
        try {
            const sessionId = sessionsIds[Math.floor(Math.random() * sessionsIds.length)];

            console.log(`getSession: re-using session ${sessionId}`);

            return await puppeteer.connect(browser, sessionId);
        } catch (e) {
            console.log(`getSession: Error connecting to session - Might already be in use. ${JSON.stringify(await puppeteer.sessions(browser))}`);
        }

    try {
        console.log(`getSession: creating new session`);
        return await puppeteer.launch(browser);
    } catch (e) {
        console.log(`getSession: Error creating new session - ${JSON.stringify(await puppeteer.history(browser))}`);
    }
}

async function getSession(browser) {
    const sessions = await puppeteer.sessions(browser);
    console.log(`getSession: sessions - ${JSON.stringify(sessions)}`);
    const sessionsIds = sessions
        .filter((v) => {
            return !v.connectionId;
        })
        .map((v) => {
            return v.sessionId;
        });

    console.log(`getSession: Available sessionsIds - ${JSON.stringify(sessionsIds)}`);

    if (sessionsIds.length !== 0)
        try {
            const sessionId = sessionsIds[Math.floor(Math.random() * sessionsIds.length)];

            console.log(`getSession: re-using session ${sessionId}`);

            return await puppeteer.connect(browser, sessionId);
        } catch (e) {
            console.log(`getSession: Error connecting to session - Might already be in use. ${JSON.stringify(await puppeteer.sessions(browser))}`);
        }

    try {
        console.log(`getSession: creating new session`);
        return await puppeteer.launch(browser);
    } catch (e) {
        console.log(`getSession: Error creating new session - ${JSON.stringify(await puppeteer.history(browser))}`);
    }
}

onnimonni

O

onnimonni•4/4/24, 11:38 AM

Hey!

I was trying out the Browser Rendering demo from here:
https://developers.cloudflare.com/browser-rendering/platform/puppeteer/

which resulted in following error:

{
    text: 'A request to the Cloudflare API
  (/accounts/XXXXXXXXXXX/workers/scripts/browser-worker/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/XXXXXXXXXXX/workers/scripts/browser-worker/edge-preview) failed.',
    notes: [
      {
        text: 'workers.api.error.no_access_to_browser_worker [code: 10088]'
      }
    ],
    location: undefined,
    kind: 'error',
    code: 10088
  }

And by googling the error I noticed this github issue https://github.com/cloudflare/workers-sdk/issues/3433 which lead me here to apply for the Browser Rendering private beta

onnimonni

O

onnimonni•4/4/24, 11:41 AM

Would there be a chance for me to try this out already? I'm currently starting a new greenfield project using solely CF and there are some cases where the browser automation would be very handy for me.

I've used puppeteer earlier for example when certain payment providers for my company didn't have any API to download monthly accounting reports and we needed to download them by logging into their portal with headless chrome

onnimonni

O

onnimonni•4/4/24, 11:44 AM

Ah sorry for the noice. I didn't notice the separate thread for asking the access: Browser Rendering API Beta Access

Advany

A

Advany•4/4/24, 4:27 PM

also in the past we where able to connect to external chromium (as a backup):

const browser = await puppeteer.connect({
    browserWSEndpoint: `wss://chrome.browserless.io/`,
});

const browser = await puppeteer.connect({
    browserWSEndpoint: `wss://chrome.browserless.io/`,
});

thats not working anymore with version 0.0.6

Mackenly

M

Mackenly•4/5/24, 3:05 PM

So with the new GA announcement there are still no changes to limits or pricing right? Just a somewhat cleaner way to handle reusing a session. Doesn't solve the pricing problem at all. PMs were a no show on a research call they requested a few weeks ago and never followed up. Feels like a pattern with this product.

Sam

S

Sam•4/5/24, 3:11 PM

Glad there were changes made to session management, but the hard limits are still very concerning - I have more than two environments so it's already a no-go. Would be happy to pay for a "max concurrent browser" increase, it would be a far-cry from the $200/mo for Browserless.

Original message was deleted

Mackenly

M

Mackenly•4/5/24, 3:18 PM

Yes, and that pricing puts you at $4,270 to take a screenshot every minute for 30 days (assuming you don't hackily keep a session open through a durable object alarm).

Original message was deleted

Mackenly

M

Mackenly•4/5/24, 3:19 PM

It's still limited to 60 seconds without interaction. Sessions don't solve the pricing problem.

Original message was deleted

Mackenly

M

Mackenly•4/5/24, 3:23 PM

Yeah in practice every 60s might work within the 60s limit, however let's say it's instead every 61s. (And that's also not considering that it would take a bit for the page to load). Point still stands even if you let's say take a screenshot every 120s, still crazy pricing only avoidable through hacky DO implementations.

async function getSession(browser) {
    const sessions = await puppeteer.sessions(browser);
    console.log(`getSession: sessions - ${JSON.stringify(sessions)}`);
    const sessionsIds = sessions
        .filter((v) => {
            return !v.connectionId;
        })
        .map((v) => {
            return v.sessionId;
        });

    console.log(`getSession: Available sessionsIds - ${JSON.stringify(sessionsIds)}`);

    if (sessionsIds.length !== 0)
        try {
            const sessionId = sessionsIds[Math.floor(Math.random() * sessionsIds.length)];

            console.log(`getSession: re-using session ${sessionId}`);

            return await puppeteer.connect(browser, sessionId);
        } catch (e) {
            console.log(`getSession: Error connecting to session - Might already be in use. ${JSON.stringify(await puppeteer.sessions(browser))}`);
        }

    try {
        console.log(`getSession: creating new session`);
        return await puppeteer.launch(browser);
    } catch (e) {
        console.log(`getSession: Error creating new session - ${JSON.stringify(await puppeteer.history(browser))}`);
    }
}

async function getSession(browser) {
    const sessions = await puppeteer.sessions(browser);
    console.log(`getSession: sessions - ${JSON.stringify(sessions)}`);
    const sessionsIds = sessions
        .filter((v) => {
            return !v.connectionId;
        })
        .map((v) => {
            return v.sessionId;
        });

    console.log(`getSession: Available sessionsIds - ${JSON.stringify(sessionsIds)}`);

    if (sessionsIds.length !== 0)
        try {
            const sessionId = sessionsIds[Math.floor(Math.random() * sessionsIds.length)];

            console.log(`getSession: re-using session ${sessionId}`);

            return await puppeteer.connect(browser, sessionId);
        } catch (e) {
            console.log(`getSession: Error connecting to session - Might already be in use. ${JSON.stringify(await puppeteer.sessions(browser))}`);
        }

    try {
        console.log(`getSession: creating new session`);
        return await puppeteer.launch(browser);
    } catch (e) {
        console.log(`getSession: Error creating new session - ${JSON.stringify(await puppeteer.history(browser))}`);
    }
}

{
    text: 'A request to the Cloudflare API
  (/accounts/XXXXXXXXXXX/workers/scripts/browser-worker/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/XXXXXXXXXXX/workers/scripts/browser-worker/edge-preview) failed.',
    notes: [
      {
        text: 'workers.api.error.no_access_to_browser_worker [code: 10088]'
      }
    ],
    location: undefined,
    kind: 'error',
    code: 10088
  }