Is this available anywhere? I would like to do the same so I can use my own playwright server instea
Is this available anywhere? I would like to do the same so I can use my own playwright server instead of the browser rendering api
DNope wont work cuz cloudflare workers has limitation on ws size message so even if you patch it cdp messages will be too big inside cloudflare workers see https://github.com/cloudflare/workerd/issues/4649
edit see someone else tried and wrote up way more about it:
https://github.com/cloudflare/playwright/pull/59
edit see someone else tried and wrote up way more about it:
https://github.com/cloudflare/playwright/pull/59
GitHub
I’m working on adding support to connecting to any arbitrary websocket chrome dev protocol server for @cloudflare/playwright (in draft cloudflare/playwright#59) but seeing errors when the incoming ...
GitHub
This adds support for using any ws CDP based server to connect to, without breaking existing usage of the browser rendering api. Example usage with Browserbase:
import { Browserbase } from &#39...
import { Browserbase } from &#39...
DThat’s too bad, guess I’ll stick with aws lambdas for now
J#browser-rendering-api
Koh so timely. actually just finished PR for docs to add info on how you can add your own fonts!
will be at the bottom of this page in ~10 min https://developers.cloudflare.com/browser-rendering/reference/supported-fonts/
will be at the bottom of this page in ~10 min https://developers.cloudflare.com/browser-rendering/reference/supported-fonts/
Cloudflare Docs
Browser Rendering uses a managed Chromium environment that includes a standard set of fonts. When you generate a screenshot or PDF, text is rendered using the fonts available in this environment.
WUnable to create new browser: code: 503
Got this error a few times yesterday
Got this error a few times yesterday
PPossibly related to https://www.cloudflarestatus.com/incidents/wvkqmzqz8f08.
There are still some reports of the error happening, which the team is currently taking a look at
There are still some reports of the error happening, which the team is currently taking a look at
WI've been periodically getting this error (invoking browser rendering via workers binding)
redacted
redacted
<uuid>K
when did it start happening? and had you made any changes?WGetting this a bunch right now - is there a known issue?
Pthere's a somewhat big incident going on right now, might be related: https://www.cloudflarestatus.com/incidents/ff4947s38tlb
Kyes that's it. we're working on it rn
LI keep getting “Workers are too busy” right now. Is that because of the current downtime in the Workers KV and effecting the REST API for PDF generation too?
LThis seems to be resolved now. Back at
{"success":false,"errors":[{"message":"Browser is too busy","code":2000}]}Kis this still happening? incident was resolved already
LNo, it has been resolved already. Thanks!
Cyour my hero
Bhello, im constantly getting "The browser context is undefined. This means the CDP connection to the browser failed". this is for stagehand. using the following code as taken from the docs..
const stagehand = new Stagehand({
env: "LOCAL",
localBrowserLaunchOptions: { cdpUrl: endpointURLString(env.BROWSER) },
llmClient: new WorkersAIClient(env.AI),
verbose: 1,
});
await stagehand.init(); //errors here
const page = stagehand.page;
await page.goto('https://demo.playwright.dev/movies');
anyone get this working.
its being called from a CF workflow for context.
i have used the CF browser rendering successfully with pupetteer from the same project.
const stagehand = new Stagehand({
env: "LOCAL",
localBrowserLaunchOptions: { cdpUrl: endpointURLString(env.BROWSER) },
llmClient: new WorkersAIClient(env.AI),
verbose: 1,
});
await stagehand.init(); //errors here
const page = stagehand.page;
await page.goto('https://demo.playwright.dev/movies');
anyone get this working.
its being called from a CF workflow for context.
i have used the CF browser rendering successfully with pupetteer from the same project.
WUnable to create new browser: code: 503: message: No browser availablegetting this on my Workers
MHi, hope that somebody can give me a hand: I want to develop a headless browser, where the user can browse like in a nowmal browser & can press a button to scrape the page that he sees? Is there something like that already out there that i might be capable to use or to build upon? Thx 4 the tipp
KI also keep getting this, even though I have way less browser instances than "workers paid" allow
KOn my browser rendering page I have "Average number of concurrent sessions - 0" and the history of browser sessions mostly have "Normal closure", but some sessions are missing "end time". Aren't they supposed to time out in 60s even if they weren't properly closed?
KI might be hitting this: "Rate limits are enforced with a fixed per-second fill rate. For example, a limit of 60 requests per minute translates to 1 request per second. This means you cannot send all 60 requests at once; the API expects them to be spread evenly over the minute. If your account has a custom higher limit, it will also be enforced as a per-second rate." source
KNo, that wasn't it. I even check my limits with puppeteer.limit(browser) first, and even though it says I have available browser - I get the same error anyway.
Kthanks for reporting. we made a change that should have resolved the 503s. can you confirm if working properly now?
cc: @kol3x as you had the same issue
cc: @kol3x as you had the same issue
Kthis is odd - can you dm me with account id and session ids so we can look into this please?
RHey @BlockMinister , are you running that code in the worker directly or is it in some Durable Object? Can you try the following code change?
(instead of passing
(instead of passing
env.BROWSER binding object, pass the "BROWSER" string to endpointURLString)
SHow do I get
X-Browser-Ms-Used value with typescript sdk? I think it is impossible with typescript sdk right now.
Bthanks for the reply, im using it in a Cloudflare Workflow step. I get a type script error when using the string as you suggested...
i deployed it anyway but it didnt work ,it failed with the same error as I reported previously.
Argument of type 'string' is not assignable to parameter of type 'BrowserWorker'.ts i deployed it anyway but it didnt work ,it failed with the same error as I reported previously.
Rthat's strange, I have it running like this:
Can you check you're using
Can you check you're using
@cloudflare/playwright@1.0.0 and that you have a browser binding named BROWSER?
Khey WebGL should work now. Can yall confirm if working for your use cases?
@marek @katu @Jon M.
@marek @katu @Jon M.
KChecked with the team -
I think it should work with .asResponse() method. Something like this:
const contentRes = await client.browserRendering.content.create({ account_id: 'account_id' }).asResponse();
const browserMsUsed = parseInt(contentRes.headers.get('X-Browser-Ms-Used') || '');
I think it should work with .asResponse() method. Something like this:
const contentRes = await client.browserRendering.content.create({ account_id: 'account_id' }).asResponse();
const browserMsUsed = parseInt(contentRes.headers.get('X-Browser-Ms-Used') || '');
WAnyone else getting 503 errors when invoking from a worker binding?
GHello, can I cancel Browser Rendering calls with an abort signal?
Wand again...
Kyou're right we had an incident yesterday and today. it's our top priority to get to the bottom of. major apologies
E@JDoc I've had this happen a ton locally, but it seems better in production. Did you experience that Playwright(-MCP), too? (I have)
AThe issue concerns the parser start time.
EEThis may be more about #agents , but I'm surprised (or terrible at investigation) that https://github.com/cloudflare/playwright-mcp isn't
I would've expected it to internally do something like
acquireing a dedicated browser for each agent session.I would've expected it to internally do something like
routeAgentRequest . I'm afraid that my agents are all referencing the same env.BROWSER (but separate contexts)
NHad a question regarding the Browser Rendering’s Rest API: In the docs it mentions that if a request is rate-limited, it’ll return a “Retry-After” header with the number of seconds until you can try again: https://developers.cloudflare.com/browser-rendering/platform/limits/#error-429-too-many-requests
From testing the api in curl it doesn’t seem to be including this header though. Even using the sample JS code shown ends up with a null retry count. When I was testing it last week I feel like it was including this header, so is this related to the outage that happened?
From testing the api in curl it doesn’t seem to be including this header though. Even using the sample JS code shown ends up with a null retry count. When I was testing it last week I feel like it was including this header, so is this related to the outage that happened?
AHiya, we're trying to port our PDF rendering from DocRaptor to the Browser Rendering API, but it seems like loading custom fonts via the REST API isn't working, and we'd like to avoid spinning up a worker just for this purpose. Is there a way to allow loading fonts via
style tags via the REST API that I'm not seeing or is that not an option? If not, is it on the roadmap?
WI've loaded custom fonts from Google fonts - but invoking via Worker, might be different via API
AYeah unfortunately we can't use Google fonts, we've got a custom font we self-host on our CDN. I know we can do this with a Worker, but we'd really rather not do that - our main app is hosted on GCP right now and building a GCP <> CF auth integration is more effort than it's worth to get fast PDF rendering
