Hello, I have an issue with a website freshly updated to NextJS App Router. The website was working perfecty with the Pages Router. After a successful build, on the main page load, I’m getting this error : Runtime.ExitError - RequestId: b60addd0-6d7f-42d1-b9f9-3ecca20acc1a Error: Runtime exited …

I managed to make It work with some adjustement on data cache params, but prefech routes still throw 500 errors. Not ideal (because there’s no client side routing…), but this will do for now :person_shrugging:

Next.js 14 is known to have several issues, this could likely be one more. You can use next.js 13.3 or 13.4 at the moment.

I went down to version 13.5.6, and exact same issue. Then I tried version 13.4.19, it’s a bit different : error 500 from netlify :frowning:

13.4.x is the latest version we recommend; later versions will not work well. Once you’ve downgraded, you should be able to see what is causing the 500 errors in your function logs, have you checked them in our admin UI?

Segmentation fault on NextJS 14/13.5 website

Support

Wykks November 17, 2023, 10:45am 6

I see thanks, looks like I’m in this situation : Server.edge not defined Error on nextJS SSR functions cause site to return 500 Errors … I’ll check what I can do

Topic		Replies	Views
Error: Runtime exited with error: signal: segmentation fault Support nextjs	3	468	May 19, 2024
404 error handler fails on Next.js 14 site Support nextjs	6	1948	March 12, 2024
Server.edge not defined Error on nextJS SSR functions cause site to return 500 Errors Support nextjs , solved-by-community	135	23045	February 18, 2024
I get the "Page not found" error after using Next.js Runtime - v5.1.2 Support deployment , nextjs	8	2782	May 3, 2024
Random 500 Errors after Deployment to Netlify with Next.js 14.1.4 Support deployment , nextjs	4	142	December 13, 2024

Segmentation fault on NextJS 14/13.5 website

Related topics