negabar
CDCloudflare Developers
•Created by negabar on 8/25/2023 in #workers-help
The deployment to the workers is successful, but I get a 500 error when accessing it. (nextjs13)
I'm deploying Next.js13 using the wrangler command. Although the deployment succeeds, I'm encountering a 500 error.
The Next.js page fetches from the API and server-side rendering(all pages)
I'm not using App router
It's puzzling because sometimes it works. Occasionally, after running yarn vercel build, I am prompted to execute vercel pull, and it succeeds afterward. However, this is also sporadic. I cannot determine a consistent way to reproduce the issue. How should I troubleshoot this?
The static images are loading fine, so it seems the issue lies with the workers. Is there a way to check the logs to ensure the workers are operating correctly?
This is my deployment procedure.
6 replies
CDCloudflare Developers
•Created by negabar on 8/22/2023 in #workers-help
how to disable edge environment only locally(export const runtime = 'edge')
When I only want to run it in a non-edge environment locally, how should I configure the pages in Next.js?
In summary,
I would like to do it as follows locally
//export const runtime = 'edge'
When deploying to Cloudflare, I would like to do it as follows.
export const runtime = 'edge'
It seems that runtime settings cannot be configured dynamically.
const test = 'eidge'
export const runtime = test
Even with the above settings, I encountered an error when running npx @cloudflare/next-on-pages@1
Please let me know if there are any other solutions or improvements.
2 replies
CDCloudflare Developers
•Created by negabar on 7/22/2023 in #pages-help
SLA for Cloudflare Pages 100%?
I saw in a document that Cloudflare’s Business plan Service Level Agreement (SLA) is 100%
Does this mean it includes the features of Cloudflare pages and Cloudflare workers?
If it’s the Business plan, then the SLA is 100% for everything?
please let me know if my understanding is incorrect.
Thanks reading my question
3 replies