Browser Rendering Error: 429

Hey, I have a simple browser-rendering API worker (code below). But I frequently get this error:

Error: Unabled to create new browser: code: 429: message: Too many browsers already running

Error: Unabled to create new browser: code: 429: message: Too many browsers already running

Error: Unabled to create new browser: code: 429: message: Too many browsers already running

Error: Unabled to create new browser: code: 429: message: Too many browsers already running

It happens locally when testing with —remote but also in prod. I had to switch my backend to another service as my tool went viral this weekend.

My code to get html for a url:

import puppeteer from "@cloudflare/puppeteer";

let browser;
export default {
    async fetch(request, env, ctx) {
        const { searchParams } = new URL(request.url);
        let url = searchParams.get("url");
        if (!url) {
            return new Response("Missing url parameter", { status: 400 });
        }
        url = new URL(url).toString(); // normalize
        console.log(`Fetching ${url}`);
        const browser = await puppeteer.launch(env.MYBROWSER);
        const page = await browser.newPage();
        await page.goto(url, { waitUntil: 'networkidle0' });
        const data = await page.content();
        await browser.close();
        // send as txt
        return new Response(data, {
            headers: {
                "content-type": "text/plain",
            },
        });

    },
};

import puppeteer from "@cloudflare/puppeteer";

let browser;
export default {
    async fetch(request, env, ctx) {
        const { searchParams } = new URL(request.url);
        let url = searchParams.get("url");
        if (!url) {
            return new Response("Missing url parameter", { status: 400 });
        }
        url = new URL(url).toString(); // normalize
        console.log(`Fetching ${url}`);
        const browser = await puppeteer.launch(env.MYBROWSER);
        const page = await browser.newPage();
        await page.goto(url, { waitUntil: 'networkidle0' });
        const data = await page.content();
        await browser.close();
        // send as txt
        return new Response(data, {
            headers: {
                "content-type": "text/plain",
            },
        });

    },
};

import puppeteer from "@cloudflare/puppeteer";

let browser;
export default {
    async fetch(request, env, ctx) {
        const { searchParams } = new URL(request.url);
        let url = searchParams.get("url");
        if (!url) {
            return new Response("Missing url parameter", { status: 400 });
        }
        url = new URL(url).toString(); // normalize
        console.log(`Fetching ${url}`);
        const browser = await puppeteer.launch(env.MYBROWSER);
        const page = await browser.newPage();
        await page.goto(url, { waitUntil: 'networkidle0' });
        const data = await page.content();
        await browser.close();
        // send as txt
        return new Response(data, {
            headers: {
                "content-type": "text/plain",
            },
        });

    },
};

import puppeteer from "@cloudflare/puppeteer";

let browser;
export default {
    async fetch(request, env, ctx) {
        const { searchParams } = new URL(request.url);
        let url = searchParams.get("url");
        if (!url) {
            return new Response("Missing url parameter", { status: 400 });
        }
        url = new URL(url).toString(); // normalize
        console.log(`Fetching ${url}`);
        const browser = await puppeteer.launch(env.MYBROWSER);
        const page = await browser.newPage();
        await page.goto(url, { waitUntil: 'networkidle0' });
        const data = await page.content();
        await browser.close();
        // send as txt
        return new Response(data, {
            headers: {
                "content-type": "text/plain",
            },
        });

    },
};

Aasad Hey, I have a simple browser-rendering API worker (code below). But I frequently...

Chaika•4/16/24, 4:31 PM

You'll want to use Sessions
https://developers.cloudflare.com/browser-rendering/get-started/reuse-sessions/
or Durable Objects directly:
https://developers.cloudflare.com/browser-rendering/get-started/browser-rendering-with-do/
to reuse browser instances

Chaika•4/16/24, 4:31 PM

https://developers.cloudflare.com/browser-rendering/platform/limits/
You only get

Two new browsers per minute per account.
Two concurrent browsers per account.
A browser instance gets killed if it does not get any command for 60 seconds, freeing one instance.
browser.close() or disconnecting from the API WebSocket releases the browser instance.

asadOP•4/16/24, 4:33 PM

thanks. is there a limit to how many pages i can open if i wrap this in a durable object.

Aasad thanks. is there a limit to how many pages i can open if i wrap this in a durabl...

Chaika•4/16/24, 4:34 PM

only in the sense that a DO can only handle so many connections/a browser can only do so much Work. You'll hit a memory limit if you don't dispose your resources as well: browser-rendering-api

asadOP•4/16/24, 4:40 PM

hmmm

that makes this a bit awkward to use. I guess my assumption was that I don’t need to worry about putting any load on the API

In comparison, I fell back to using browserless.io where I don’t need to manage browser instance myself… i just remote connect to one.

Aasad hmmm 🤔 that makes this a bit awkward to use. I guess my assumption was that I d...

Chaika•4/16/24, 4:41 PM

I agree, I think it really should be as simple as just calling an endpoint to get a page and not having to worry about the backing session/browser or anything like that. Sadly, it is how it is right now

Browser Rendering Error: 429

Similar Threads

Similar Threads

Similar Threads