Chunks files not found after upgraded to 13.4.1x

[hungcrush]

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

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

Expected Behavior

None

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[controversial]

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.

[hykelvinlee42]

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

[aXenDeveloper]

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.

[hungcrush]

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?

[hykelvinlee42]

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

[Baukaalm]

I have the same issue, described it here #54133 (comment).

[Baukaalm]

Can you show links or router.push configs with that paths?
Maybe you send asPath incorrect

[hungcrush]

Can you show links or router.push configs with that paths? Maybe you send asPath incorrect

No this is static files. they're in .next folder

[bryceAebi]

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?

[hungcrush]

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?

Yes. After I downgraded to 13.4.9 it works well...

[bryceAebi]

Perhaps my issue is not the same. My only affected routes are the dynamic routes and the error looks the same, but the chunks that are sometimes missing are not those from the [slug] directory. (13.4.9 does not solve the issue for me)

[MarceloBD]

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

[Refrezsh]

Same problem with using Nginx as reverse, all works fine on Next 13.4.12.

[shehi]

This is the same as #54008 .

[picspirit]

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.

[hungcrush]

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

[MarceloBD]

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

[shehi]

Being on IIS doesn't mean it doesn't have similar rewrite mechanism like Nginx does when URLs are terminated with a slash. I think this behaviour actually to be a standard behaviour, because several frameworks also behave this way. Have you checked your IIS vhost configuration?

…

On Wed, 13 Sept 2023, 12:09 Marcelo Bertoldi Diani, < ***@***.***> wrote: But this is still a bug in nextjs as I am having this on Windows and not running nginx — Reply to this email directly, view it on GitHub <#54120 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE7SANMH36DH4WPBHFIWXTX2GA4NANCNFSM6AAAAAA3SSG5GU> . You are receiving this because you commented.Message ID: <vercel/next. ***@***.***>

[MarceloBD]

You mean on my machine? I am running on localhost

[alexrabin]

This should still be open. 13.5.1 still has this issue with IIS

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.