While deploy to AWS with SST getting below error

[KBambharoliya]

Describe the Bug

[Error: Failed to collect configuration for /[child]/[subChild]/[result]] {
[cause]: TypeError: Invalid URL
at 62543 (.next/server/chunks/2501.js:226:52141)
at Function.t (.next/server/webpack-runtime.js:1:128) {
input: '',
code: 'ERR_INVALID_URL'
}
}

Build error occurred
[Error: Failed to collect page data for /[child]/[subChild]/[result]] {
type: 'Error'
}
node:internal/errors:865
const err = new Error(message);
^
Error: Command failed: pnpm build
at __node_internal_genericNodeError (node:internal/errors:865:15)
at checkExecSyncError (node:child_process:890:11)
at Object.execSync (node:child_process:962:15)
at buildNextjsApp (file:///home/runner/.npm/_npx/e014fccbbe7e583d/node_modules/@opennextjs/aws/dist/build.js:95:8)
at build (file:///home/runner/.npm/_npx/e014fccbbe7e583d/node_modules/@opennextjs/aws/dist/build.js:44:5)
at async file:///home/runner/.npm/_npx/e014fccbbe7e583d/node_modules/@opennextjs/aws/dist/index.js:9:1 {
status: 1,
signal: null,
output: [ null, null, null ],
pid: 2247,
stdout: null,
stderr: null
}

Link to the code that reproduces this issue

pnpx create-payload-app@latest -t blank

Reproduction Steps

Getting build error while push changes to github.

Which area(s) are affected? (Select all that apply)

Not sure

Environment Info

Binaries:
  Node: 20.18.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  payload: 3.17.1
  next: 15.1.4
  @payloadcms/db-mongodb: 3.17.1
  @payloadcms/email-nodemailer: 3.17.1
  @payloadcms/graphql: 3.17.1
  @payloadcms/live-preview: 3.17.1
  @payloadcms/live-preview-react: 3.17.1
  @payloadcms/next/utilities: 3.17.1
  @payloadcms/payload-cloud: 3.17.1
  @payloadcms/plugin-cloud-storage: 3.17.1
  @payloadcms/plugin-nested-docs: 3.17.1
  @payloadcms/plugin-redirects: 3.17.1
  @payloadcms/plugin-seo: 3.17.1
  @payloadcms/richtext-lexical: 3.17.1
  @payloadcms/storage-s3: 3.17.1
  @payloadcms/translations: 3.17.1
  @payloadcms/ui/shared: 3.17.1
  react: 19.0.0
  react-dom: 19.0.0
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 16130
  Available CPU cores: 8

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@beta -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload

[KBambharoliya]

Actually I can't provide the github repo link as it's my company's project

[cgilly2fast]

Hi @KBambharoliya I use Payload and SST as well, can I see your sst.config for the the payload app? I assume you are using the container (AWS Fargate) deployment?