Starting today, Next.js deployed with amplify is showing an internal server error

[jangmang]

No description provided.

[espenbye]

We have the same issue. Tried downgrading Next.js version, but that did not help.

Tried the following:

export NEXT_PRIVATE_STANDALONE=true
npm run build

cp -r .next/static .next/standalone/.next/static
cp -r public .next/standalone/public

node .next/standalone/server.js

It runs successfully locally, but not when deployed to Amplify Hosting.

AppId: d3pgmzdoktuvon
Environment: develop

Logs:

Field | Value
-- | --
@ingestionTime | 1683545776456
@log | 052097004422:/aws/amplify/d3pgmzdoktuvon
@logStream | develop/2023/05/08/80fb0d8d83e54c348a7c7467effb0013
@message | [x-amplify-log][INFO] app response status_code=500 Internal Server Error headers=date: Mon, 08 May 2023 11:36:12 GMT, connection: keep-alive, keep-alive: redacted (9), content-length: 21, x-amplify-internal-request-id: 8bc97529-bd84-4f38-aaf8-6e23736942f1, x-amplify-internal-metrics: RuntimeTotal;dur=302, RuntimeInitialization;dur=254, CustomerServerReadinessCheck;dur=244, CustomerServerCall;dur=44
@timestamp | 1683545772422

[abepuentes]

Same test and same results as @espenbye.

[Lezzio]

What's your package manager ? Using pnpm with symlinks broke our apps. We're now using another mode to avoid symlinks as a hot fix #3467

[ghost]

This appears to be a duplicate of #3466. Please continue any further engagements on that issue. We will provide an update there shortly. Thank you for your patience!

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.