@scythe I also through " single connection concurrently" is the limitation, so that why I was surpri

OOndrej @scythe I also through " single connection concurrently" is the limitation, so t...

C

Chaika•7/4/24, 1:47 PM

I thought the "Connections" number shows connections concurrently, but as it shows 3 (and the max allowedd is 2) it can not be.

It just means the total amount of connections to that browser session. If you click on it, you can view the full log

C

Chaika•7/4/24, 1:48 PM

The sessions api lets you reuse sessions, under the hood its just one worker grabbing the session, connecting to it, doing whatever, finishing and disconnecting (which releases it back to the pool)

O

OndrejOP•7/4/24, 2:12 PM

@Chaika I have this slightly modified version of DO Cloudflare Browser Rendering tutorial https://gist.github.com/OndrejDrapalik/0272a3863214a39c717dc4ca9d649bba that was able to "rank up" "Connections" to 3 and up which in my opinion shoun't have.

Gist

Cloudflare Browser Rendering tutorial with maxed out KEEP_BROWSER_A...

Cloudflare Browser Rendering tutorial with maxed out KEEP_BROWSER_ALIVE_IN_SECONDS - gist:0272a3863214a39c717dc4ca9d649bba

OOndrej @Chaika I have this slightly modified version of DO Cloudflare Browser Renderin...

C

Chaika•7/4/24, 2:13 PM

again, connections in the dashboard is not saying you have 3 concurrent connections to that session, it's saying over that sessions' entire life span, you have had 3

O

OndrejOP•7/4/24, 2:13 PM

Oh, that makes sense. Couldn't wrap my head around this

O

OndrejOP•7/4/24, 2:14 PM

Thank you!

T

TheMightyPenguin•7/5/24, 7:43 PM

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)

I

Imtiaj•7/7/24, 2:05 PM

Hello, on my cloudflare account i have access to browser workers, but on my clients account there isn't getting an error during deployment.
Can anyone point me to how to get access to browser workers on my client's account?

C

Coffee11•7/16/24, 6:18 AM

It means I don't access to browser rendering api?
TypeError: Cannot read properties of undefined (reading 'fetch')
at PuppeteerWorkers.launch (index.js:13829:32)
at Object.queue (index.js:13946:46)

Sscythe You need workers paid account

C

Coffee11•7/16/24, 6:36 AM

I'm in paid but doesn't work

C

Coffee11•7/16/24, 6:37 AM

I'm following this tutorial https://developers.cloudflare.com/queues/tutorials/web-crawler-with-browser-rendering/

Cloudflare Docs

Cloudflare Queues - Queues & Browser Rendering · Cloudflare Queues

This tutorial explains how to build and deploy a web crawler with Queues, Browser Rendering, and Puppeteer.

A

Arvind•7/16/24, 7:38 AM

I need access to Workers Browser Rendering API, already signed up for it

A

Arvind•7/16/24, 7:38 AM

can anyone help me with the access?

A

akazwz•7/16/24, 8:43 AM

you need paid worker plan

C

cloudkite•7/16/24, 8:48 AM

I have set keep_alive option to 10mins, however my browser session is closed after 10mins even if I have had active connections within the 10min timeframe. Shouldn't idle termination only happen if browser has been idle for 10mins since the most recent connection? At the moment it appears that browser is closed 10mins from the first connection

Aakazwz you need paid worker plan

A

Arvind•7/16/24, 4:23 PM

like i dont know if i have to pay for it but i need access, whether its paid or free

Ssc Where did you sign up for it? The beta access has ended. Right now, you only nee...

A

Arvind•7/16/24, 6:27 PM

Thank you for sharing the link. The Beta access URL was found somewhere on Reddit I guess.

Anyways, When I click on the URL you provided, and signup for a paid plan (which is $5 per month), I get an error that "I don't have access to that page" and then I get redirected to the worker's page. There I don't see any way to upgrade or get on the paid plan

A

Arvind•7/16/24, 6:27 PM

Screenshot_2024-07-16_at_11.54.32_PM.png

Screenshot_2024-07-16_at_11.54.47_PM.png

Sscythe I think that after the 10 mins pass, you’re back at the idle time of 1 min. So f...

C

cloudkite•7/16/24, 7:29 PM

Any idea if thats intentional or a bug? If intentional seems like a very confusing API choice

C

cloudkite•7/16/24, 8:29 PM

Have submitted a bug with a minimal repo see https://github.com/cloudflare/puppeteer/issues/53

GitHub

[Bug]: Browser is closed despite having set keep_alive setting to 1...

Bug description Steps to reproduce the problem: Minimal reproduction see https://github.com/cloudkite/keep-alive-test. Have got a simple worker which crawls https://example.com every 5mins. Browser...

P

Puliczek•7/17/24, 3:57 PM

How to make Browser rendering working in local env? Can it handle like 100+ users requests per minute? I need only to scrap pages.

Sscythe Are you using @types/node >=20.10 ? Had that issue with 20.8 and an update fixe...

D

dave•7/21/24, 12:03 AM

I did

yarn add @types/node -D

yarn add @types/node -D

yarn add @types/node -D

yarn add @types/node -D, but I'm still getting this error

Ddave I did `yarn add @types/node -D`, but I'm still getting this error

J

James•7/21/24, 3:48 AM

You might be hitting https://github.com/cloudflare/workerd/issues/1298

D

dave•7/21/24, 3:50 AM

all good, I ended up switching my project away from browser rendering.

몰

몰라세스•7/26/24, 4:31 AM

It seems like you can use a string that is unlikely to be included in the URL, and then divide it by that string on the server.

For example, if divide is , (comma), you can divide the string A "a.com,b.com,c.com" with A.split(",").

몰

몰라세스•7/26/24, 4:32 AM

I'm not sure since I haven't looked at the source code in detail, but this is the simplest way to pass an Array via URL.

몰몰라세스 It seems like you can use a string that is unlikely to be included in the URL, a...

H

Hamed•7/26/24, 4:58 AM

I'm not sure really how the

split

split

split

split method could be helpful in this case. But appreciate your comment.

H

Hamed•7/28/24, 1:15 PM

Hi again!

I've got this Worker already deployed to the Cloudflare. I need to run it every

minutes. So I did it under

Settings > Triggers > Cron Triggers

Settings > Triggers > Cron Triggers

Settings > Triggers > Cron Triggers

Settings > Triggers > Cron Triggers of that specific worker (picture). But the worker never triggered and never run? And I can see the errors (picture) but I don't know where to track down the logs! I appreciate any thought!?

import puppeteer from '@cloudflare/puppeteer';
import { nanoid } from 'nanoid';

const URLS = [
    'https://cloudflare.com',
    'https://google.com',
    'https://wikipedia.org',
];

export default {
    async fetch(_, env) {
        let browser;
        try {
            browser = await puppeteer.launch(env.MYBROWSER);

            const processUrl = async (url) => {
                const page = await browser.newPage();
                await page.goto(url);
                let img = await page.screenshot();

                const filename = new URL(url).hostname.replace(/^www\./, '').replace(/\./g, '-');
                const id = nanoid(5);

                await env.BROWSER_KV_DEMO.put(`${filename}_${id}`, img);

                await page.close();
            };

            await Promise.all(URLS.map(processUrl));
        } catch (error) {
            console.error({ error });
        } finally {
            if (browser) {
                await browser.close();
            }
        }
        return new Response('ok');
    },
};

import puppeteer from '@cloudflare/puppeteer';
import { nanoid } from 'nanoid';

const URLS = [
    'https://cloudflare.com',
    'https://google.com',
    'https://wikipedia.org',
];

export default {
    async fetch(_, env) {
        let browser;
        try {
            browser = await puppeteer.launch(env.MYBROWSER);

            const processUrl = async (url) => {
                const page = await browser.newPage();
                await page.goto(url);
                let img = await page.screenshot();

                const filename = new URL(url).hostname.replace(/^www\./, '').replace(/\./g, '-');
                const id = nanoid(5);

                await env.BROWSER_KV_DEMO.put(`${filename}_${id}`, img);

                await page.close();
            };

            await Promise.all(URLS.map(processUrl));
        } catch (error) {
            console.error({ error });
        } finally {
            if (browser) {
                await browser.close();
            }
        }
        return new Response('ok');
    },
};

import puppeteer from '@cloudflare/puppeteer';
import { nanoid } from 'nanoid';

const URLS = [
    'https://cloudflare.com',
    'https://google.com',
    'https://wikipedia.org',
];

export default {
    async fetch(_, env) {
        let browser;
        try {
            browser = await puppeteer.launch(env.MYBROWSER);

            const processUrl = async (url) => {
                const page = await browser.newPage();
                await page.goto(url);
                let img = await page.screenshot();

                const filename = new URL(url).hostname.replace(/^www\./, '').replace(/\./g, '-');
                const id = nanoid(5);

                await env.BROWSER_KV_DEMO.put(`${filename}_${id}`, img);

                await page.close();
            };

            await Promise.all(URLS.map(processUrl));
        } catch (error) {
            console.error({ error });
        } finally {
            if (browser) {
                await browser.close();
            }
        }
        return new Response('ok');
    },
};

import puppeteer from '@cloudflare/puppeteer';
import { nanoid } from 'nanoid';

const URLS = [
    'https://cloudflare.com',
    'https://google.com',
    'https://wikipedia.org',
];

export default {
    async fetch(_, env) {
        let browser;
        try {
            browser = await puppeteer.launch(env.MYBROWSER);

            const processUrl = async (url) => {
                const page = await browser.newPage();
                await page.goto(url);
                let img = await page.screenshot();

                const filename = new URL(url).hostname.replace(/^www\./, '').replace(/\./g, '-');
                const id = nanoid(5);

                await env.BROWSER_KV_DEMO.put(`${filename}_${id}`, img);

                await page.close();
            };

            await Promise.all(URLS.map(processUrl));
        } catch (error) {
            console.error({ error });
        } finally {
            if (browser) {
                await browser.close();
            }
        }
        return new Response('ok');
    },
};

HHamed Hi again! 👋 I've got this Worker already deployed to the Cloudflare. I need ...

K

kian•7/28/24, 1:38 PM

You need a

scheduled

scheduled

handler,

fetch

fetch

is for HTTP requests

K

kian•7/28/24, 1:38 PM

https://developers.cloudflare.com/workers/configuration/cron-triggers/#1-define-a-scheduled-event-listener

Y

yangyangy•7/28/24, 3:52 PM

workers.api.error.no_access_to_browser_worker [code: 10088]

J

jjjrmy•7/28/24, 9:28 PM

is there any way to get around the Cloudflare Human Check?

Jjjjrmy is there any way to get around the Cloudflare Human Check?

H

Hello, I’m Allie!•7/28/24, 9:52 PM

Be a human, click the button?

H

Hello, I’m Allie!•7/28/24, 9:54 PM

Oh, in Browser Rendering? Not that I know of

H

Hello, I’m Allie!•7/28/24, 9:54 PM

Unless it is your website

E

Erisa•7/28/24, 10:26 PM

Well browser rendering is not a human, so it would be intentional that you can't pass it.

E

Erisa•7/28/24, 10:26 PM

If it's your website you can identify those requests in some way and bypass challenges for them

E

emil•8/2/24, 12:06 PM

Not exactly sure on the concurrent sessions pricing. If I run 10 sessions at a time max is it correct I won't ever be billed for concurrent sessions? (I'm on Workers paid)

E

emil•8/2/24, 12:07 PM

Also I have a 1/minute Cron trigger on the same worker with my Browser binding, but it doesn't actually use the browser binding, so that shouldn't start any sessions, correct?

E

emil•8/2/24, 12:51 PM

Also getting this on page.pdf() calls with Puppeteer - looks like the GitHub issue on it had no answers since April: https://github.com/cloudflare/puppeteer/issues/37

GitHub

[Bug]: Puppeteer PDF generation via Page.pdf() method · Issue #37 ·...

Bug description I was creating a simple html to pdf converter when I stumbled into a little issue with all the current version of the fork. In the current implementation of the Page.pdf method in t...

@scythe I also through " single connection concurrently" is the limitation, so that why I was surpri

Similar Threads

Similar Threads

Similar Threads