Next Pages 1101 Error Logs
I have recently just published a Page for a Nuxt SSR application. The build is successful and deploys. When I access the page, I get the dreaded 1101 error page. This page does not show my details, as I expected, but I realize there are no runtime logs accessible to see what errors are occuring.
How is one supposed to debug these 1101's without logs or any feedback as to what's happening under the hood?
13 Replies
?pages-logs
If you're looking to tail a Pages Function you can do so in the UI here: https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment/functions
or with Wrangler:
wrangler pages deployment tail [deploymentId/url]What?
Not not really. I have a Nuxt application deployed via pages. I dont have any functions created, just an SSR website.
did go to the
Functions tab and enabled Real-time Logs to figure out what exception was occurring. But this is an http response and not like a node runtime log sort of thing. Is there anyway to get access to that?SSR means you have functions
SSR is sever side
Ya I know
And no, because I have SSR doesnt mean I am using functions
So my the error response is showing the following:
I don't really know how to interpret the error. I also preview the application locally and it works as expected. I have no idea how to debug the
pages-worker... script that its refering to since I don't have acces to it.how else do you do ssr :p
I just publish to Cloudflare pages. I am not creating any Cloudflare functions.
Means there's a code path not generating a response, sadly these can be hard to debug
Nuxt is still making a function, it's impossible to SSR without a function - ssr is by definition server-side rendering, functions are server-side code
ok well I am not creating a cloudflare function explicity then. whatever cloudflare does, I dont know about under the hood. besides that point....I am publishing to pages with little configuration. Everything works locally, even production build, so Cloudflare is causing the issue somewhere and does little to tell you what
Nuxt is doing it not Cloudflare
And Nuxt is generating the code
Cloudflare just runs the code we get, we aren't generating it and we aren't the ones that made the code here
So I'd say report this to Nuxt if you aren't doing anything special on top
Mmmk