internal errors means something went wrong inside cloudflare pages/workers
internal errors means something went wrong inside cloudflare pages/workers
GYeah, but most likely because of some bad input? With the non-descript error + no stack trace it's a needle in a haystack problem. We dumped a ton of try/catch into our app and eventually found something. In a worker it's a bit easier to debug as you can just wrap at the entrypoint and catch any uncaught errors
Jits something going legitimately wrong on cloudflare's end if you get just 'Error: internal error', you will normally need an employee to check if they can see something for the deployment id
GHmm okay, is there anything we can check if this happens locally running with wrangler/workerd?
GWe're just running this locally while trying to get it working, haven't setup any deployments yet
Jmaybe something throwing an exception in workerd locally
GNothing visible in the output. I'll hit up our cloudflare support contacts to see if we can get someone from CF to take a look. Thanks for your help!
RHas anyone done work to optimize the bundle size of their Next.js build?
RWith the App Router, it seems that pretty much everything gets bundled together, regardless of whether it's client or server side.
SHello everyone, Do you guys build nextjs pages project using nx project.json?
FHey does someone have a good idea for how to set up your API_URL environment variables?
I am currently setting them in my wrangler.toml file and then using getRequestContext().env.API_URL to access them. This works both locally and in deployment for my functions in api/route/..
However when i try to access my apis at ”api/route” (using fetch in my page.tsx component) it works locally but seems to break in production:/
Thanks for any respons!
I am currently setting them in my wrangler.toml file and then using getRequestContext().env.API_URL to access them. This works both locally and in deployment for my functions in api/route/..
However when i try to access my apis at ”api/route” (using fetch in my page.tsx component) it works locally but seems to break in production:/
Thanks for any respons!
AIs there any way to make some built-in environment variables public?
I'm trying to access
I've looked into
UPDATE: The solution is using the env config option to map them to
I'm trying to access
CF_PAGES_BRANCHCF_PAGES_URLNEXT_PUBLIC_*I've looked into
getRequestContextUPDATE: The solution is using the env config option to map them to
NEXT_PUBLIC_*
ZHello everyone, everything ok?
I'm working on a project with nextjs 14 and when I upload the project to cloudflare pages. Only one page works in SSR. The others do not load the fetch. Has anyone had this problem and know how to solve it?
I'm working on a project with nextjs 14 and when I upload the project to cloudflare pages. Only one page works in SSR. The others do not load the fetch. Has anyone had this problem and know how to solve it?
Jdo you get any errors in your deployment logs?
Jif you tail your deployment with wrangler or use log stream, you should be able to see logs for the internal server errors
Jwouldnt know what's going on without seeing the full source code
AHi, is it possible to modify this page and put a new one?
HIf you are on the Pro, Business, or Enterprise plan you can customize and brand these pages for your whole account or for specific domains. You can design custom error pages to appear during a security challenge or when an error occurs.- Configuring Custom Pages (Error and Challenge)
Cloudflare Docs
Cloudflare uses a wide range of error codes to identify issues in handling request traffic. By default, these error pages mention Cloudflare; however, …
Nlately ive been getting some weird builds that refer variables that dont exist
Nthey're always called
Nasync__chunk_xxxxxgives me stuff like "ReferenceError: async__chunk_24831 is not defined" in prod when i call a server function
Nis that something known orrr
Nand the last time i had this happen i solved it by...
Nrandomly renaming the files it was happening in
Nchanging the functions a bit...
Nso idk
Nand it works completely fine in next dev mode
Nbut does error in preview
Nwith the exact same chunk name
Nhello, I'm building a blog website using NextJs with Cloudflare and next-on-pages. Because the blog has so many images, so it is easy to reach the size limit of Cloudflare Worker. Can you tell me how to avoid this limitation? Such as, how to exclude the static assets like images and fonts to count in Cloudflare Worker size limit.
JYou can make a custom _routes.json file in your project for your images/fonts etc. and we'll merge it with the one that gets made in the output directory
Jcan you make an issue with a repro
Nnot really
Nseems to be a nextjs issue
Nanyway, can I make an R2 binding I have upload to the live binding in dev mode?
HIIRC Pages dev is local-only
Nalright
ZHas anyone got hono+nextjs+d1 working together? i want to use this stack and deploy on cloudflare pages but wanted to know if i will jump into any bottlenecks so i can be aware of.
