Hey! I am Joe, nice to meet you

The error suggests that Next.js cannot find the 500.js file. Can you check the build output in .next/server/pages/ to ensure that the 500.js page is generated properly? Also, the redirection to .nl when an error occurs may point to an issue with the locale or how the domain routing is set up. Let's also ensure that your domain locale settings are correct in the Next.js config, and there are no unintended effects with locale fallback.

Are your Cloudflare logs for any requests to the .com domain resulting in 301/302 redirects, particularly around the 500 error pages?

HI Joe,

Thanks for replying.

The 500.js file does exist in the build output on the given path, as well as a JSON and HTML file in each locale folder. That is for a local build. The output folder in Vercel only has a 500 file for each locale folder.

And this the i18n config.

1
  i18n: {
2
    locales:  ['en-gb', 'nl', 'nl-be', 'en', 'fr', 'de'],
3
    defaultLocale: 'nl',
4
    localeDetection: false,
5
    domains: [
6
      {
7
        domain: 'www.diamondsbyme.nl',
8
        defaultLocale: 'nl',
9
      },
10
      {
11
        domain: 'www.diamondsbyme.be',
12
        defaultLocale: 'nl-be',
13
      },
14
      {
15
        domain: 'www.diamondsbyme.de',
16
        defaultLocale: 'de',
17
      },
18
      {
19
        domain: 'www.diamondsbyme.fr',
20
        defaultLocale: 'fr',
21
      },
22
      {
23
        domain: 'www.diamondsbyme.com',
24
        defaultLocale: 'en',
25
      },
26
      {
27
        domain: 'www.diamondsbyme.co.uk',
28
        defaultLocale: 'en-gb',
29
      },
30
    ],
31
  }

Our Cloudflare logs have no 302 or 301 redirects that are linked to the 500 error page.

There is a chunk for _next/static/chunks/pages/500-[HASH].js which in my mind should be referenced in when rendering the error page instead.

Hi @gijsbotje Apologies for the delayed response.

Given that the 500.js file is present in the Vercel output but still causing a missing module error, there could be possibly a routing or locale-specific issue affecting error page handling?

Since you’re using middleware to handle the /product/[...slug] routing, can you try logging its behavior during error scenarios? I wonder if the middleware is affecting locale-specific paths for the 500 page.

Also I assume, 500.js for en is served without any disturbance caused from custom routing rules.

Can you also check if any caching rules or edge functions on Cloudflare could be interfering with locale handling?

I totally understand how tiresome troubleshooting might be but it will all be totally worth it once we found the root cause! Also, given that Vercel Team is so helpful, I believe they will be able to help us get to the root of this and make it work as expected!

Let me know if you have made some progress here!

We are using the pages router and using i18n config. Our middleware does not use the locale to reroute or redirect requests. Logging the errors locally works just fine.

The 500.js chunk is served properly: https://www.diamondsbyme.com/_next/static/chunks/pages/500-fb35dc0774e07ed3.js

We do not use Cloudflare workers or edge functions. We only cache the JSON files in Cloudflare.

I have a feeling it might be connected to my other issue: https://community.vercel.com/t/domain-routing-i18n-adds-default-locale-to-link-hrefs/1676