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:

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	397	May 19, 2024
Segmentation fault on SSR Astro 5 site Support deployment	7	35	February 26, 2025
NextJS Error 500 after deploy when fetching data on API route Support deployment , nextjs	11	2723	January 6, 2024
Nextjs 13 Dynamic routing to single view page error 500 Support deployment , redirects , nextjs	5	954	August 25, 2023
500 Internal Server Error with NextJS Support deployment , nextjs	6	1532	November 9, 2023

Segmentation fault on NextJS 14/13.5 website

Related topics