workers deployment v2 produces an [nuxt] instance unavailable, works when build is compiled locally
I have a weird issue with the pages deployment.
When i compile localhost, and then use wrangler pages deploy, everything is fine.
When i use either the v2 github pull function (autodeploy) or a github action (cloudflare/pages-action@v1.5.0) then the Nuxt server constantly produces a [nuxt] instance unavailable
i.e.: https://1615b361.app-hub.pages.dev/ (deployed via local worker, no issues)
https://ff5d1bbe.app-hub.pages.dev/ ( deployed via github action)
https://d88b02f2.mc2-mono.pages.dev/ (deployed via pages v2 hook)
what can i do to debug it? i already figured out that if i turn nuxt SSR off, all works fine, but then my seo is total crap - so not an option.
When i compile localhost, and then use wrangler pages deploy, everything is fine.
When i use either the v2 github pull function (autodeploy) or a github action (cloudflare/pages-action@v1.5.0) then the Nuxt server constantly produces a [nuxt] instance unavailable
i.e.: https://1615b361.app-hub.pages.dev/ (deployed via local worker, no issues)
https://ff5d1bbe.app-hub.pages.dev/ ( deployed via github action)
https://d88b02f2.mc2-mono.pages.dev/ (deployed via pages v2 hook)
what can i do to debug it? i already figured out that if i turn nuxt SSR off, all works fine, but then my seo is total crap - so not an option.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,529Members
Resources
Similar Threads
Was this page helpful?
