Hello Netlify Community,
I recently started experiencing (mid-day GMT 18th July) a critical issue with my Next.js application hosted on Netlify. The application shows intermittent 404 errors, slow page loads, and inconsistent functionality. These problems occur even though no recent changes to the application.
The 404 errors are as follows:
/_next/static/chunks/webpack-9550a8ccb8d52fdd.js:1 Failed to load resource: the server responded with a status of 404 ()
/_next/static/IZRV9RPWo82lSwelJQnuY/_buildManifest.js:1 Failed to load resource: the server responded with a status of 404 ()
/_next/static/chunks/9496-ad402dba953b6ca4.js:1 Failed to load resource: the server responded with a status of 404 ()
/_next/static/IZRV9RPWo82lSwelJQnuY/_ssgManifest.js:1 Failed to load resource: the server responded with a status of 404 ()
/_next/static/chunks/9001-a1f5baa10cb6159f.js:1 Failed to load resource: the server responded with a status of 404 ()
On some refreshes, when the page loads, the main content doesn’t appear and the errors mentioned above are logged in the console. Here is a screenshot:
On other refreshes, the application doesn’t seem to load JavaScript, resulting in enlarged icons and other misbehaviour (I can only include one screenshot so will try post image in the comments).
Weirdly, the page does load some of the time. However, even when the page loads, it’s significantly slower than usual. I also see these errors in my console log:
GET https://<myapp>/_next/static/IZRV9RPWo82lSwelJQnuY/_ssgManifest.js net::ERR_ABORTED 404
worldwide:41 GET https://<myapp>/_next/static/IZRV9RPWo82lSwelJQnuY/_buildManifest.js net::ERR_ABORTED 404
Additionally, I have noticed an apparent caching issue with the Netlify functions. The data returned by these functions varies slightly between requests, suggesting some problem with caching might be occurring.
Interestingly, some users in different parts of the world have reported no issues, making the problem harder to pinpoint and debug.
I’d greatly appreciate any assistance in diagnosing and resolving this issue, as it’s causing a significant disruption to my application’s operation…
