next.js: Chunks files not found after upgraded to 13.4.1x

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #26~22.04.1-Ubuntu SMP Mon Apr 24 01:58:15 UTC 2023
    Binaries:
      Node: 18.16.1
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.16
      eslint-config-next: 13.4.16
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
    Next.js Config:
      output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

None

To Reproduce

git pull yarn build

pm2 stop vf pm2 delete vf

image

Describe the Bug

My chunks files in static/chunks/app/[locale]/… not found ( I checked the file on server and they’re exist. other files normal

ex: /_next/static/chunks/app/%5Blocale%5D/layout-38b8ac0a0766c23e.js

image

Expected Behavior

None

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

About this issue

  • Original URL
  • State: closed
  • Created 10 months ago
  • Reactions: 7
  • Comments: 21 (3 by maintainers)

Most upvoted comments

Issue #54008 described the same and provided a reproducible example.

Same problem here with next 13.4.19, chunks are created but they are not found

Yes, the same for me in docker container.

https://github.com/vercel/next.js/tree/canary/examples/with-docker Example for docker also not working.

It’s fixed by remove slash ‘/’ end of link on nginx config. Thank you.

I’ve been experiencing the same issue when deploying the project in a Nginx server (docker container).

I’m experiencing a similar issue, though it only manifests when I test my site via Google Search Console.

Do folks know which version I can downgrade to to solve this error? Is it 13.4.9?

You didn’t provide any code for a reproduction, but try stopping your server, removing the .next folder, and then running next build && next start (or next dev) from there.

But this is still a bug in nextjs as I am having this on Windows and not running nginx

I’ve been experiencing the same issue. Debian, Nginx, PM2. If visite the app by http://ip:3000, there would be no problem. But if I visit the domain, got the same issure. nextjs’s version: 13.4.19.

You didn’t provide any code for a reproduction, but try stopping your server, removing the .next folder, and then running next build && next start (or next dev) from there.

I tried it. But it same 😦 It only happens on [locale] folder: app/[locale]/…

Do you have any ideas for it?