Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with Async Dynamic APIs #8701

Closed
todor0v opened this issue Oct 14, 2024 · 1 comment
Closed

Error with Async Dynamic APIs #8701

todor0v opened this issue Oct 14, 2024 · 1 comment
Assignees

Comments

@todor0v
Copy link

todor0v commented Oct 14, 2024

Link to reproduction

No response

Environment Info

Binaries:
Node: 20.12.2
npm: 10.5.0
Yarn: N/A
pnpm: 9.12.1
Relevant Packages:
payload: 3.0.0-beta.111
next: 15.0.0-canary.173
@payloadcms/db-mongodb: 3.0.0-beta.111
@payloadcms/graphql: 3.0.0-beta.111
@payloadcms/next/utilities: 3.0.0-beta.111
@payloadcms/plugin-cloud-storage: 3.0.0-beta.111
@payloadcms/richtext-lexical: 3.0.0-beta.111
@payloadcms/storage-s3: 3.0.0-beta.111
@payloadcms/translations: 3.0.0-beta.111
@payloadcms/ui/shared: 3.0.0-beta.111
react: 19.0.0-rc-3edc000d-20240926
react-dom: 19.0.0-rc-3edc000d-20240926

Describe the Bug

When opening the Payload admin panel using the versions described in the environment info, I get the following errors:
Image

Reproduction Steps

I am aware that we closed #8463, however, I still get the above mentioned errors. Solutions I've tried:

  • I deleted node_modules and .next and installed again.
  • I made sure the content of all payload files is absolutely exactly the same as these.
  • I do not have any usage of next/headers

Adapters and Plugins

db-mongodb

@todor0v todor0v added status: needs-triage Possible bug which hasn't been reproduced yet v3 labels Oct 14, 2024
@todor0v todor0v changed the title Support Async Dynamic APIs Error with Async Dynamic APIs Oct 14, 2024
@github-actions github-actions bot removed the status: needs-triage Possible bug which hasn't been reproduced yet label Oct 15, 2024
@jmikrut
Copy link
Member

jmikrut commented Oct 15, 2024

@todor0v is it possible that this is coming from some custom code in your project? We don't have a single reference to x-forwarded-proto at all in our code.

A new blank Payload project with your versions above does not show this behavior. We will need a reproduction in order to help here. Will convert to Q&A discussion as I don't believe this is an issue with Payload, but if it is, we will re-open / fix accordingly.

@payloadcms payloadcms locked and limited conversation to collaborators Oct 15, 2024
@jmikrut jmikrut converted this issue into discussion #8713 Oct 15, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants