Payload Admin 500 on Custom Domain in Vercel Despite CSRF/CORS Config

[imrankhanjoya]

Describe the Bug

Payload admin panel works fine on Vercel preview URL but throws 500 on custom domain (onionpose.com).
I set serverURL, updated CSRF and CORS lists, and redeployed — still no change.
Env var is set to SERVER_URL=https://onionpose.com for production, yet Payload appears to still bundle admin panel for preview domain or reject CSRF from custom domain.
Error log
⨯ TypeError: Cannot read properties of undefined (reading 'id') at d (/var/task/.next/server/chunks/8549.js:1:10273) at nC (/var/task/node_modules/.pnpm/next@15.0.0-canary.104_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-_5f6q75h2dzprt4skqwjuf4pdzm/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:20:42763) at nE (/var/task/node_modules/.pnpm/next@15.0.0-canary.104_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-_5f6q75h2dzprt4skqwjuf4pdzm/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:20:44535) at nE (/var/task/node_modules/.pnpm/next@15.0.0-canary.104_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-_5f6q75h2dzprt4skqwjuf4pdzm/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:20:59297) at nA (/var/task/node_modules/.pnpm/next@15.0.0-canary.104_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-_5f6q75h2dzprt4skqwjuf4pdzm/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:20:62303) at nP (/var/task/node_modules/.pnpm/next@15.0.0-canary.104_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-_5f6q75h2dzprt4skqwjuf4pdzm/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:20:59946) at nO (/var/task/node_modules/.pnpm/next@15.0.0-canary.104_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-_5f6q75h2dzprt4skqwjuf4pdzm/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:20:65184) at nj (/var/task/node_modules/.pnpm/next@15.0.0-canary.104_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-_5f6q75h2dzprt4skqwjuf4pdzm/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:20:64414) at nA (/var/task/node_modules/.pnpm/next@15.0.0-canary.104_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-_5f6q75h2dzprt4skqwjuf4pdzm/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:20:62567) at nP (/var/task/node_modules/.pnpm/next@15.0.0-canary.104_babel-plugin-react-compiler@0.0.0-experimental-48eb8f4-20240822_react-_5f6q75h2dzprt4skqwjuf4pdzm/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:20:59946) { digest: '1477207072' }

Please help

Link to the code that reproduces this issue

https://onionpose.com/admin

Reproduction Steps

https://onionpose.com/admin

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

area: core

Environment Info

payload-3.0-demo@0.1.0 payload /Users/imran/Documents/GitHub/onionposecms
> payload "info"


Binaries:
  Node: 23.5.0
  npm: 11.2.0
  Yarn: 1.22.22
  pnpm: 8.6.2
Relevant Packages:
  payload: 3.0.0-canary.0374de4
  next: 15.0.0-canary.104
  @payloadcms/db-mongodb: 3.0.0-canary.0374de4
  @payloadcms/db-postgres: 3.0.0-canary.0374de4
  @payloadcms/graphql: 3.0.0-canary.0374de4
  @payloadcms/next/utilities: 3.0.0-canary.0374de4
  @payloadcms/plugin-cloud-storage: 3.0.0-canary.0374de4
  @payloadcms/richtext-lexical: 3.0.0-canary.0374de4
  @payloadcms/richtext-slate: 3.0.0-canary.0374de4
  @payloadcms/storage-uploadthing: 3.0.0-canary.0374de4
  @payloadcms/storage-vercel-blob: 3.0.0-canary.0374de4
  @payloadcms/translations: 3.0.0-canary.0374de4
  @payloadcms/ui/shared: 3.0.0-canary.0374de4
  react: 19.0.0-rc-06d0b89e-20240801
  react-dom: 19.0.0-rc-06d0b89e-20240801
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Fri Jul  5 17:56:39 PDT 2024; root:xnu-10063.141.1~2/RELEASE_ARM64_T8122
  Available memory (MB): 8192
  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@latest -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

[JarrodMFlesch]

You might need to use this one? https://vercel.com/docs/environment-variables/system-environment-variables#VERCEL_PROJECT_PRODUCTION_URL