[next 14.0.4] Getting Server Actions error from non server actions request/response (Working on Chromium, not for Safari or FireFox) #59105
Replies: 43 comments 23 replies
-
|
i have the same error, but for now all my component are client |
Beta Was this translation helpful? Give feedback.
-
|
same here |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue while using |
Beta Was this translation helpful? Give feedback.
-
|
Also getting this error: |
Beta Was this translation helpful? Give feedback.
-
|
Same issue for me |
Beta Was this translation helpful? Give feedback.
-
|
Also having the same issue. "Error: Failed to find Server Action "null". This request might be from an older or newer deployment. Original error: Invariant: Missing 'next-action' header." Unsure how to resolve it. |
Beta Was this translation helpful? Give feedback.
-
|
Add this to header and try again. It worked for me: |
Beta Was this translation helpful? Give feedback.
-
|
Yes, this also worked for me. I only used the key: 'Access-Control-Allow-Origin' |
Beta Was this translation helpful? Give feedback.
-
|
What Header ? |
Beta Was this translation helpful? Give feedback.
-
|
I'm a newbie, please elaborate which header, or provide code with the fix. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for delay. You also need to define NEXT_PUBLIC_APP_URL in your env file. in your next.config.js file: https://nextjs.org/docs/pages/api-reference/next-config-js/headers |
Beta Was this translation helpful? Give feedback.
-
|
I tried this and am still getting the error. Any way to reproduce this issue to debug on local dev? I'm only seeing this after deployment |
Beta Was this translation helpful? Give feedback.
-
|
same error i got Error: Failed to find Server Action "c44e2f10789ec4c5fbc4dad37671bce191042615". This request might be from an older or newer deployment. Original error: Invariant: Couldn't find action module ID from module map. |
Beta Was this translation helpful? Give feedback.
-
|
i had the same issues while i deploy my nextjs app in docker, i fixed using a session duration in next auth config |
Beta Was this translation helpful? Give feedback.
-
|
I have the same error in a nextjs 14.1.0 project. |
Beta Was this translation helpful? Give feedback.
-
|
Yep I'm getting the same problem: |
Beta Was this translation helpful? Give feedback.
-
|
Getting the same error after deploying to next 14.1.0 |
Beta Was this translation helpful? Give feedback.
-
|
@jjang16, I have precisely the same issue. Could you let me know if you found a solution? |
Beta Was this translation helpful? Give feedback.
-
|
Same thing here, next 14.1.0, using a component with "use client" and <Script/>: Maybe this is an “internal bug” ? |
Beta Was this translation helpful? Give feedback.
-
|
OK, so I got what happened to me: Where I work, we need to use some “external” scripts, one of them after being called runs a request: Since next is “handling” routes after it receives this post request, it returns a default 404 error page. So, the only solution I found, for me, since I can't change this external script, was to actually create a middleware and do a proper re-routing of the request. So the question I make is, this message was generated in my terminal because of the request was “wrong” (not intended to next to be honest), OR, because when generating the error message next also throws an error? |
Beta Was this translation helpful? Give feedback.
-
|
Same Error
|
Beta Was this translation helpful? Give feedback.
-
|
Okay, this was the issue for me personally. I was writing a server actions file. Which then I converted into a standard REST API route. I forgot to remove the "use server" tag. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there. Pretty new to web dev so if you think of a better solution please share. What solved the problem for me was adding "preventDefault()" and "location.reload()". My next.config.js file is using default settings, I didn't change anything there ( I tried, but it didn't work for me). |
Beta Was this translation helpful? Give feedback.
-
|
Same. 14.0.4 |
Beta Was this translation helpful? Give feedback.
-
|
Many forget to switch from onSubmit to "action" when using a form; this might help. |
Beta Was this translation helpful? Give feedback.
-
|
Could you please explain that in more detail? |
Beta Was this translation helpful? Give feedback.
-
|
Or possibly many changed the action prop to onclic prop of form element. Then you will change type prop of button to "button". This resolve the error for me. |
Beta Was this translation helpful? Give feedback.
-
|
I hade the same exact problem, |
Beta Was this translation helpful? Give feedback.
-
|
This is happening for me for a completely empty nextjs project with only the default Tried the following things to get rid of it but nothing worked:
I don't even have any server actions defined yet. It also happens in an infinite loop and creates thousands of log statements saying Does anyone else have the same issue as me? Has anyone been able to figure this out? This seems like an extremely critical bug to me, why has the NextJS team been ignoring it for 3+ months since it was first reported? |
Beta Was this translation helpful? Give feedback.
-
|
I haven't tried a completely empty NextJS project, but I am also running on AWS ECS fargate and seeing this same issue. |
Beta Was this translation helpful? Give feedback.
-
|
FWIW since I was just starting off a new project and also fairly new to frontend dev in general (with several years of backend exp), I just switched to Remix. Couldn't be happier. Feels like an order of magnitude better framework than NextJS. There are no weird gotchas (that I've come across yet), very well designed and stable API with non overlapping surfaces, and can achieve everything I wanted with nextjs without all the complicated concepts. |
Beta Was this translation helpful? Give feedback.
-
|
I was getting that same "Missing 'next-action' header" error with Next 14.1.3. Then I discovered that I was passing a bad URL to axios (due to a missing env variable) in one of my server actions. Once I fixed the axios request, the error went away and it works fine. |
Beta Was this translation helpful? Give feedback.
-
|
This is probably not the answer for everyone. |
Beta Was this translation helpful? Give feedback.
-
|
I use pnpm, but have this issue. So, this won't apply to everyone. |
Beta Was this translation helpful? Give feedback.
-
|
I use next 14.1.2 App Router. when I was using next-auth v5 to implement user login in my app, I got the error message you guys mentioned here.
I call signIn to do login in my customized form, but I get above error message. It shows "HTTP/1.1 404 Not Found" when I check the http response using Fiddle. I am sure to implement route.ts under /api/auth/[...nextauth] correctly.
|
Beta Was this translation helpful? Give feedback.
-
|
Not sure if you tried this solution, but I created my authentication options in a separate module and imported it into the route.ts in the /api/auth/[...nextauth] path to handle the get and post requests. Hope this helps any |
Beta Was this translation helpful? Give feedback.
-
|
It's imported handler to deal with the post request cause I am using 5.0.0-beta.16 |
Beta Was this translation helpful? Give feedback.
-
|
Same issue, is not reproducible every time but happens... And happens only on prod |
Beta Was this translation helpful? Give feedback.
-
|
Do you think if we revert back to 14.0.3 or even 14.0.0 for example might solve the issue? |
Beta Was this translation helpful? Give feedback.
-
|
Same issue. Next version 14.1.4 |
Beta Was this translation helpful? Give feedback.
-
How did you fix this? We're getting the same issue |
Beta Was this translation helpful? Give feedback.
-
|
my case is resolved by fixing api usage, but it looks like there's several cases which occurs and it turned out that 'working on chrome/chromium' looks like bug, or chromium handles/modifies request. |
Beta Was this translation helpful? Give feedback.
-
|
I believe this is related to undici |
Beta Was this translation helpful? Give feedback.
-
|
In my case i think it's related to internationalization. I highly suspect it doesn't like the The solution of adding a import { Domains } from "..."
import createMiddleware from "next-intl/middleware"
const intlMiddleware = createMiddleware({
locales: Domains?.map(({ defaultLocale }) => defaultLocale),
defaultLocale: "us",
domains: Domains,
localePrefix: "never",
timeZone: "Europe/Madrid"
})
const middleware = req => {
// GET DEFAULT LOCALE
const host = req.headers.get("host")
const { defaultLocale = "us" } = Domains.find(({ domain }) => domain === host)
req.cookies.set("NEXT_LOCALE", defaultLocale)
// APPLY TRANSLATION MIDDLEWARE
return intlMiddleware(req)
}
export default middleware
export const config = {
matcher: ["/", "/((?!api|_next|_vercel|.*\\..*).*)"]
}This started appearing after switching to the |
Beta Was this translation helpful? Give feedback.
-
am still getting the error in my log , the discussion is closed but still cannot find a solution, should i consider it as a bug or what am i supposed to do ? |
Beta Was this translation helpful? Give feedback.
-
|
well i created a new one here since this one is closed --> #64214 |
Beta Was this translation helpful? Give feedback.
and others
-
Edited at Dec, 11. 2023, after tested with 14.0.4
Summary
What I want to implement
(1) service: request with authorization request (on same tab or popup) with return URL parameters passed
(2) third party: do authorization process -> open page of return URL with result
(3) service: check result and doing rest job
Return component (at current status)
Client Component
Errors i got and what i did
This is first error message i got from return url
After search, i found #58295 #58019
I found that
So, I
which made error changed into
So, I added
to server component but it shows same error.
As this is not a server-actions component, what should I do to resolve this?
Additional information
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions