You are not allowed to perform this action when ran in production

[BigHoss]

Steps to Recreate

1. create a 3.0 beta website on my local machine
2. connect to the production postgres database
3. seed the database
4. activate localization an l18n
5. edit pages and content in debug
6. push changes into repo
7. coolify builds and deploys payload
8. when editing anything in the admin interface, I get errors and strange behavior
9. error log messages
10. validation errors in ui and ui breaking

Am I doing something wrong here or how am I supposed to do this properly?

errors in log

validation errors when publishing a page

breaking ui when switching locale

[BigHoss]

Now i dropped all the tables and let the published installation do the migration and reregister. Still the same issue.

Can please someone help me with this?

[fazofazaal]

I'm also having the same issue.

The prod site is on Vercel. I've connected to a Mongo DB Atlas instance on both local and live sites.

Can create, update, and delete resources locally, but getting the same errors on the live site.

[JP-HoneyBadger]

I am seeing something similar to this related to Auth. If you change create and update to anyone in the collection, does it work?

[fazofazaal]

Yeah, it does work. However, there is still a 401 unauthorized error response from the form_state endpoint, which is used by the Lexical editor to update its state. The media blocks within Lexical editor don't work in production

[sekiranat]

Yeah, it does work. However, there is still a 401 unauthorized error response from the form_state endpoint, which is used by the Lexical editor to update its state. The media blocks within Lexical editor don't work in production

Try use blank template

Edit: The template has no effect on this issue

[sekiranat]

This error is only reproduced for the template website and is due to user === null during request validation in src/access/authenticated.ts

Edit: The template has no effect on this issue

[exoer]

Check if there is a mismatch between the env-variable PAYLOAD_PUBLIC_SERVER_URL and the actual domain you are running on

[sekiranat]

Yes, the problem was that localhost:3000 was busy and the panel automatically opened on port 3001. Env is set to port 3000 by default.