Interesting issue -- Log stream causes NextJS Edge runtime app to fail
This is kind of an intriguing one.....
1. App deploys fine via
2. I can hit the side all is dandy...
3. Go to the deployment UI, go to the "Real-time logs" section, click "Begin Log Stream"
4. Log flows begin to appear -- but now every request is an HTTP 500
5. Even after ending the log stream, the worker appears to be in a broken state and continues to throw HTTP 500s
6. Wrangler tail does not show any useful error messages:
The annoying bit is that without any code change a re-deployment ends up fixing the issue -- but I then have to wait for a full build/upload cycle (which is not that bad because of caching but still, my app is broken until I do this)
dev: https://nameplace.pages.dev/
deployment id: 0877b232-f464-44fb-bd88-fa620eb21341
account id: f1087e918dcedfd9575e5e595a817813
1. App deploys fine via
wrangler pages deploy .vercel/output/static2. I can hit the side all is dandy...
3. Go to the deployment UI, go to the "Real-time logs" section, click "Begin Log Stream"
4. Log flows begin to appear -- but now every request is an HTTP 500
5. Even after ending the log stream, the worker appears to be in a broken state and continues to throw HTTP 500s
6. Wrangler tail does not show any useful error messages:
The annoying bit is that without any code change a re-deployment ends up fixing the issue -- but I then have to wait for a full build/upload cycle (which is not that bad because of caching but still, my app is broken until I do this)
dev: https://nameplace.pages.dev/
deployment id: 0877b232-f464-44fb-bd88-fa620eb21341
account id: f1087e918dcedfd9575e5e595a817813
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
