just checking in on this after a while... did the weird as heck billing ever get sorted out with thi
just checking in on this after a while... did the weird as heck billing ever get sorted out with this?
Fhey, Kathy, this issue has not been fixed yet. I think it is a bug obviously, when will your team fix this.
Chey guys, your docs are messed up for the scrape endpoint. https://developers.cloudflare.com/api/resources/browser_rendering/subresources/scrape/
The result shape is
The result shape is
{result: [{ results: [{ ... }] }]} not {result: {result: {}}}Interact with Cloudflare's products and services via the Cloudflare API
CAnother serious issue. Links endpoint works with 
url, but pass in the html provided from /content of scraping that url and it doesn't work CAnother thing... I would really like to be able to get the title of the page, I'm not sure if scraping for the title element will be good enough for SPAs... I tried to do this by injecting a script that would create a new dom element with document.title content in it but that didn't seem to work.
CRunning into this as well
Kit's in progress. hopefully fixed tmrw
Kwhat do you mean? we have not yet started charging, however we have raised limits in the meantime and added browser rendering to workers free
Kthanks for raising these bugs + feature request.
MHi, I am evaluating browser rendering API for an AI agent with browsing capability and persistent session (logged in user). Is this a good solution? (I also looking at Browserbase)
CI'm receiving a ton of 429s, any chance I can get some help raising the rate limits? I'm happy to do a user interview call too with our use cases or if you're thinking through pricing
Rhello
We have a issue with puppeteer setUserAgent
we do a classical await page.setUserAgent(userAgent);
but the navigator.userAgent always returns Cloudflare-Workers, ignoring what we used. Is that expected, a known issue or something?
This is blocking us for leveraging the browser api properly since sites we analyze recognize this fact and respond differently.
We have a issue with puppeteer setUserAgent
we do a classical await page.setUserAgent(userAgent);
but the navigator.userAgent always returns Cloudflare-Workers, ignoring what we used. Is that expected, a known issue or something?
This is blocking us for leveraging the browser api properly since sites we analyze recognize this fact and respond differently.
AHello. Why i'm getting: {"error":"Unable to create new browser: code: 429: message: Browser time limit exceeded for today"}, i bought worker paid plan to avoid this...
ANo responses? 
MHello , I have issue when I using Browser rendering restfull api , I want to render url to pdf , first requests it works fine , then all request return this error "{"success":false,"errors":[{"message":"Authentication failed","code":10000}]}" the api token is valid and has permission on browser rendering
Sexactly the same issue
not sure why
not sure why
Si tried account and user both the tokens as well
Stried with "Bearer Token" as well
am i doing anything wrong here?
am i doing anything wrong here?
MI think there an issue with cloudflare
Mbut if you found any resolve to this issue mention me
Vit was related to this incident that has been resolved already https://discord.com/channels/595317990191398933/895794943182909470/1374043585124630591
Vplease let me know if you still have issues
Myes , it works now
CNope! Moved away from using CF rendering.
HHey CF team. I'm having trouble using the Browser Rendering binding in one of my workers to render a PDF of a web page. This was previously working ealier this month, but now the page.createPDFStream method is not returning a stream. Using page.pdf returns "Cannot create buffer". Any ideas on what would cause this?
RHello everyone, what is the best way to increase the rate limit on the browser rendering rest api? My account is set to startup/enterprise, so I assume it is configured to the default (60 r/min). We don't use this API constantly; however, when we do, we will have spikes in our usage for a short time, then it drops back to zero (it might increase later on) (unfortunately, our workflow is triggered by demand, and we can't schedule them in advance).
Kwe are checking on this. thanks for reporting
Kif you are on a paid plan, you can request higher limits here https://developers.cloudflare.com/browser-rendering/platform/limits/#workers-paid.
we ask that you only submit reqest if you're actively hitting limits as increasing limits requires manual action at this time and we want to prioritize customers who truly need the additional capacity. We're working on raising limits for everyone across the board, so this will become less of an issue in the future
we ask that you only submit reqest if you're actively hitting limits as increasing limits requires manual action at this time and we want to prioritize customers who truly need the additional capacity. We're working on raising limits for everyone across the board, so this will become less of an issue in the future
Mhey team - do you plan to remove this limitation?
I dont want to run my entire project in remote just because of this browser binding :/
I dont want to run my entire project in remote just because of this browser binding :/
Kyes support for local dev is coming up soon. totally understand that pain
K^Also curious about this. Loading pages like stripe.com just result in a white screen, presumably due to a lack of GPU rendering.
Kwould love to learn more about this ask. would you be open to a chat? https://calendar.app.google/DRNUac33bytqfzjj7
@kyle too
@kyle too
KDefinitely!
KAlso more generally, want to learn more about everyone's use case and how browser rendering can help. So if anyone would like to speak please schedule here! https://calendar.app.google/DRNUac33bytqfzjj7
RVery quick question before I spend sometime looking into this, I generate images from my worker app as react components, css/html. I’m using puppeteer to take screenshots of the component and turn them into .png. Can I incorporate this instead of puppeteer? Or is it as well as puppeteer?
UGreat suggestion! Using
@vercel/og via Cloudflare Pages Functions is definitely faster and more efficient than browser-based rendering, perfect for generating dynamic PNG/SVG from React components at scale.R@Luney @U.Senthil Kumar | Contributor I fully agree with vercel og/satori , in fact I used it originally when I was using vercel, before I decided to go down the cloudflare route. I might re look at it, as I was coming up with some issues passing in the component, it would defo be better,
Ui agree with vercel og/satori, i used it before when i was using vercel. then i changed to cloudflare. maybe i will try it again, before i had some issues with adding the component. but yeah, it’s definitely better.
SWould anyone happen to know the time limit on browser rendering for Workers Paid accounts? The docs here say that free only gets 10 minutes while paid gets an unspecified number, is it limitless or just higher by some amount?
Khey! we are working on pricing/billing for Browser Rendering right now. Pricing will be announced soon, with billing starting shortly after. Until then, for Workers Paid usage is limitless but once we start billing, you will pay for usage over the included amount in the Workers Paid plan
Sthanks!
BGetting this below error when I launch @Cloudflare/puppeteer like below in remote
BHow can I use virtual brower in local, I want to use it in local, its now working in remote mode also
BGetting so many debugging log when I launch cloudflarePappter browser at beginning and use it to load more then one URL like below.
How can I stop this logs?
this is how I launch
when I launch browser just before I want to use i ma not getting any kind of debugging logs like below
How can I stop this debugging logs?
How can I stop this logs?
this is how I launch
when I launch browser just before I want to use i ma not getting any kind of debugging logs like below
How can I stop this debugging logs?
B
Pthe "screenshotOptions.quality" flag is broken. Whenever I add it, the request fails.
MIs there a way to specify/change the model being used for the Browser Rendering json endpoint? I'm running into challenges exceeding the model's context window (24k tokens)
Knot yet. what model would you like to use?
