-
Notifications
You must be signed in to change notification settings - Fork 116
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
500 error Next.js SSR #3319
Comments
Hi @pruthviraj-developer 👋🏽 it looks like the requests are failing because there is a missing module:
You can view these logs in your account by navigating to Monitoring > Hosting compute logs and then selecting the log group for the desired branch. We are investigating this further and will provide an update once we have more information. |
Hi @hloriana Could you please update us, how to resolve the above issue, with more inputs. |
@hloriana @pruthviraj-developer Any update on the same, I am facing the same issue, and couldn't find any solution for it. |
Hi @hloriana Could you please update us, how to resolve the above issue, with more inputs. |
Hi, after successful deployment the static pages load fine and when try to load SSR pages I get 500 error with this error message on CloudWatch: [Error: ENOENT: no such file or directory, open '/tmp/app/.next/server/edge-chunks/wasm_a7e702bc5ba9227243abda7977c8096f59478d3f.wasm' NextJS Version: 13.3.0 |
Just to add to above issue, I deployed same repo on Vercel and it works perfectly fine. Why is Amplify throwing a 500 error for SSR pages? |
@shivpratik I don't know if you found a workaround for your issue but for me the solution was to downgrade to NextJS Version 13.2.4, for me it was a bug in v.13.3.0 as stated here https://github.com/vercel/next.js/issues/48077#issuecomment-1504501461. I don't know what version @pruthviraj-developer is using. @hloriii maybe this could be useful to have in mind. NextJS 13.2.4 is working fine even using AppDir. there's a cold start of 7 seconds but that's a totally different issue. |
Hi everyone 👋 , based on the previous comments on the thread this issue seems to have been fixed after downgrading to Next v13.2.4. Also, over the past few months we have made significant improvements to how we bundle Next.js apps and we no longer rely on the |
This issue is now closed. Comments on closed issues are hard for our team to see. |
This issue has been automatically locked. |
Before opening, please confirm:
App Id
d1l0h2bsjx0rcs
AWS Region
ap-south-1
Amplify Hosting feature
Build settings, Deployments, Frontend builds, Monorepo, SSR
Describe the bug
When loading the page https://release.d1l0h2bsjx0rcs.amplifyapp.com
getting 500 error, the build is getting generated successfully.
x-cache: error from Cloudfront
Expected behavior
the url https://release.d1l0h2bsjx0rcs.amplifyapp.com
should load successfully, but giving 500 error, in network says 500 error from cloudfront
Reproduction steps
https://release.d1l0h2bsjx0rcs.amplifyapp.com
Please load the above url
Build Settings
Log output
Additional information
The text was updated successfully, but these errors were encountered: