-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuxt Internal 500 Error on static build with Vercel #643
Comments
I'm wondering if this has something to do with Apollo. The reason I am saying that is because I made an identical version of this site just now but used Prismic as the CMS which didn't require me to use Apollo, since they have a '@nuxtjs/prismic' module for the API. It worked here: https://github.com/daletom/prismiccmstonuxt |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Was deploying a Nuxt.js target: static site using the vercel-builder. It works locally, but when deployed on Vercel, I was getting a 500 level Nuxt Internal Server Error. It was looking a lot like this issue: #509
The main difference is that this is not a Nuxt project using content module. It is using Apollo to access an API from Dato CMS. I still tried the recommended fix of deleting the vercel.json file and adding nuxt generate to the build command in Vercel. I no longer get the 500 error, but now the graphql endpoint is just erroring out since it is using nuxt generate. Like below:
Any recommendations on still being able to use the vercel-builder to not get the 500 level error? I added it back to show the 500 level error. The site is this: https://datocmstonuxt.vercel.app/. The repo is this: https://github.com/daletom/datocmstonuxt
The text was updated successfully, but these errors were encountered: