Replies: 2 comments 1 reply
-
Did you manage to resolve this? I have the same issue |
Beta Was this translation helpful? Give feedback.
1 reply
-
Err... Maybe late, but I figured out that you need to fixed like these. const nextConfig = {
experimental: {
serverActions: {
allowedOrigins: [
'mydomain.com',
'**.mydomain.com', // <<----- double-wildcard for ignore front part, e.g. x.y.z.mydomain.com which "x.y.z." would be ignore.
],
}
},
(...) This could be work! happy coding. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
We are trying to configure
allowedOrigins
forserverActions
. We have been using the following configuration, as suggested by the documentation: Server ActionsOur configuration
Still while using this config, we see that we get the following error:
This yields two questions:
1. Are wildcards not supported, and the documentation with examples are wrong?
2. If wildcards are supported, what are we doing wrong here?
Additional information
Using next 14.2.3
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions