Nope not at all! Just loggin in a user, sub 50ms locally and working fine everywhere else
Nope not at all! Just loggin in a user, sub 50ms locally and working fine everywhere else
HThat might be the issue. If you are on the free plan, your Function has to use less than 10 ms. CPU time
GOh didn't reallise that, seems incredibly restrictive no? The total request was 50ms, unsure about actual CPU time, but could be why it works so inconsitently...
HNot really, at least in my opinion. It should be more than enough for some light operations(especially since it doesn't include IO time), and if you do need more, you can always upgrade to Paid. Here's the table showing the limits of Workers/Functions, when it comes to differences between the Free and Paid plans:
GHmm thank you, unsure why my simple login is taking so long then... thanks for the help!
RI am developing a pages app locally with ‘wrangler pages dev —R2=bucket’ . Is it possible to access the bucket contents as a public bucket? Essentially the same as I could in the Cloudflare dashboard by adding a custom domain. At the moment I am proxying via the worker but it’s not how I intend to do it in production.
HNot sure I understand? In production, you would use Pages + R2 Custom Domain to expose your bucket
RYes, that's correct. The worker part of the pages application populates the R2 bucket
RAnd I'd like to access the contents of the bucket while testing locally, but just from a URL
HWrangler doesn’t support that
HYou can do what you are currently doing, and use a Worker
RAt the moment I've set up a route /resource/* that serves the contents of the bucket so will stick with that
RThanks, I thought that might be the case
BI'm having some trouble running wrangler pages dev with the KV namespaces I have setup on my cloudlfare. My functions work perfectly when published, but when I runn locally I cannot retrieve values from my namespaces. Is there something specific I need to do to point to the namespaces when working locally?
RI am just using --kv=KV where KV is the namespace and it works
I am also using --persist .. though I can't see it as an option in the docs, but I added it at some point
I am also using --persist .. though I can't see it as an option in the docs, but I added it at some point
THello, I'm hosting a remix app on cloudflare pages, I'm working on the observability of the app, traces and metrics do not work on cf pages as cf pages does not support timing, so now I'm looking into sending logs to a monitoring dashboard such as datadog, does anyone know how can I send logs to an external service from remix app hosted on cf pages?
HYou can't point to remote KV namespaces when running in dev.
BNot even to preview namespaces? Do you have to set them up in a wrangler.toml file to have kv's locally then?
HNope. Only Workers can access remote KV.
pages dev may read a wrangler.tomlWhat sort of approach would you take to simulate a dev environment locally? I want to speed up my dev process because it's getting tedious waiting for a new build each time I'm testing
HFind the data you need to get it running from your remote KV namespace, then add it locally with
wrangler kv:key put --local
VHow can I serve a common html file say 'foo/index.html' for URLs matching '/foo/*', similar to CF do for '404.html' but without the 404 status? Is it a way to make it possible in pages itself, without the assistance of wranger?
VIt will redirect to /foo/, but that's not the required result.
It should just load the
It should just load the
foo/index.html at /foo/* itself without any url redirect.BThanks! This solved my issue. I'm looking at using the --persist-to flag to make it easy for multiple developers to set the environment up. To use the values saved with the --persist-to flag, do you know if you need to specify using that as a namespace when running wrangler pages dev?
HNo, it should run based ont he binding name.
SI'm trying to setup a page rule to redirect www. to our root domain on a pages project but it doesn't seem to work, am I missing something simple?
MHello! I have a site hosted on CF pages and some people are reporting that they can load my site. If changing internet connection works. Has anyone ever experienced this?
MWe transform ideas into digital experiences that connect with your audience and help you build your dream team. Let's work together to create something remarkable?
MMy problem is basically the same, but there is no resolution:
https://community.cloudflare.com/t/site-is-not-accessible-via-some-internet-providers/382528
https://community.cloudflare.com/t/site-is-not-accessible-via-some-internet-providers/382528
Cloudflare Community
Hi, I have several sites hosted in a cloud server at IONOS with CF. Just two of them when CF is enabled they are not browseable trough the ISP NET/Claro (Brazil). Is there anything that I can do to fix this? When I disable the CF trough DNS I can access these ones. Regards,
Sis it just outright stupid to have a server-rendered next.js app on cloudflare pages and a separate backend on cloudflare workers or are there valid reasons to use such an architecture?
S
JMaybe don't use
https:?
SI can try, but I recall the rule makes you include http or https
JI use Bulk Redirects and don't need
https: so not sure.
FHey guys! I'm having trouble accessing PlanetScale from within Cloudflare Pages
Fdid anyone ever fiddle with that?
IHello, is there anyone that can hop on a call to help me fix this Error code 522 issue because I have tried everything and it cant seem to be fixed.
CIs this with a custom domain?
II guees yeha
Iyeah
CDid you go through the process in pages or did you manually add a CNAME record to your zone?
IManually
CYou need to go through the process or it will 522
From the docs:
From the docs:
To ensure a custom domain is added successfully, you must go through the Add a custom domain process described above. Manually adding a custom CNAME record pointing to your Cloudflare Pages site - without first associating the domain (or subdomains) in the Cloudflare Pages dashboard - will result in your domain failing to resolve at the CNAME record address, and display a 522 error.
Chow can I get the cf properties in request on next edge route?
ADoes anybody know if middlewares should work locally with
wrangler pages dev
EWhere in dash.cloudflare.com would I inspect 500s from my page workers?
EAnswer: in Deployment details under functions.
EIs it possible to have a NodeJS queue worker inside of the pages/functions project or does it need to be it's own standalone NodeJS project?
