It’s a website template that uses Next and Netlify CMS. Each branch is its own website with its own content and images. I pushed a change to config.yml so that all fields were not required, and now all I get is a generic “Internal Server Error” with no information.
I checked the build logs and notices that my pages come up as “0 bytes” in size, but I don’t know if that’s just me reading it wrong:
11:33:28 AM: Route (pages) Size First Load JS
11:33:28 AM: ┌ ○ / (303 ms) 56.6 kB 189 kB
11:33:28 AM: ├ └ css/18a43f90bf5ee566.css 3.5 kB
11:33:28 AM: ├ /_app 0 B 133 kB
11:33:28 AM: ├ ○ /404 2.68 kB 136 kB
11:33:28 AM: └ λ /api/contact 0 B 133 kB
11:33:28 AM: + First Load JS shared by all 133 kB
11:33:28 AM: ├ chunks/framework-5f4595e5518b5600.js 42 kB
11:33:28 AM: ├ chunks/main-40e3a245dac91539.js 29.1 kB
11:33:28 AM: ├ chunks/pages/_app-65a0af09945efe21.js 59.9 kB
11:33:28 AM: └ chunks/webpack-a3b997588ef5ecbd.js 1.86 kB
11:33:28 AM: λ (Server) server-side renders at runtime (uses getInitialProps or getServerSideProps)
11:33:28 AM: ○ (Static) automatically rendered as static HTML (uses no initial props)
11:33:28 AM: Done in 21.13s.
Similar issue. Build worked fine last night, this morning’s build is giving me a html page with no css, and some of my links go to 500 errors. I reverted to the last known working build and it works fine. I did see the following line in my build logs:
You have the following Netlify rewrites that might cause conflicts with the Next.js Runtime:
For some additional context, I just ran a deploy on another Next.JS site that has not yet been upgraded to Next.js version 13.0 and did not run into any issues. I’d interested to know if this may be a compatibility issue with Next.JS 13.0.
Same here. It worked fine and after a new deploy I have this issue.
Also, I wanted to redeploy the failing branch but with the misleading UI, I redeployed the main branch and now my site is down… Great…
Thanks for your patience, everyone. Could you please try rebuilding your sites and letting me know if the behavior changes? We have rolled back a change that we think was causing it, but it will require a rebuild to fix if our estimation is correct.
Please share your results here so we can understand if we need to continue to work on this!