Replies: 10 comments 16 replies
-
|
Also. the action name is "x" not a random id like other issues. and I can't replicate this in dev envrionment or manually triggering action on production. This just happens randomly at some point. I am self hosting on a vps with docker |
Beta Was this translation helpful? Give feedback.
-
|
I got it after updating to 16.0.10 |
Beta Was this translation helpful? Give feedback.
-
|
same issue, start getting it today |
Beta Was this translation helpful? Give feedback.
-
|
Same issue, we started encountering it last week too, Next 15.2.8 + fix from nextjs.org/docs/messages/failed-to-find-server-action. |
Beta Was this translation helpful? Give feedback.
-
|
On 16.1.1 and facing the same issue |
Beta Was this translation helpful? Give feedback.
-
This doesn't fix the issue for me. i am still getting same issue even after updating process.env.NEXT_SERVER_ACTIONS_ENCRYPTION_KEY |
Beta Was this translation helpful? Give feedback.
-
|
Yep, just got this as well. Application went down with timeouts (no crash, just infinite loading) accompanied by a spam of that log. Running on 15.1.9. Here's our full log: |
Beta Was this translation helpful? Give feedback.
-
|
https://nextjs.org/docs/messages/failed-to-find-server-action works for next 16.1.1 |
Beta Was this translation helpful? Give feedback.
-
|
doesn't work for me :( |
Beta Was this translation helpful? Give feedback.
-
|
@DaywisonSilva didn't work what I expected for me too, but at least it's not crashing anymore, it just logs the error and keeps running, idk how safe it is 😞 |
Beta Was this translation helpful? Give feedback.
-
|
@07CalC Do you mean that the failed to find server action ‘x’ error still is logged but your app runs fine? |
Beta Was this translation helpful? Give feedback.
-
|
@jrig95 yes, previously the app was crashing after this error (server side error), but after upgrading next js to 16.x.x and using this method prevents the app from crashing but error is still there |
Beta Was this translation helpful? Give feedback.
-
|
@07CalC Same scenario for us as well. Doesn’t seem to be impacting anything but also no sure how safe it is. Hopefully vercel acknowledges this. |
Beta Was this translation helpful? Give feedback.
-
|
The same issue occurs in version 14.2.35. The server doesn't crash, but CPU usage spikes to 100%. |
Beta Was this translation helpful? Give feedback.
-
|
If you're getting spammed with this error message on an app that is accessible externally, it's likely attackers looking for app deployments that are still vulnerable to the recent For OP, I'm not sure about the "original error" part, or why your server subsequently crashes - did you upgrade to a safe version of next? |
Beta Was this translation helpful? Give feedback.
-
|
We updated nextjs to 16.1.1 after a react2shell incident. Since then, on one nextjs app, the page goes into a reloading loop, 3 to 10 reloads, sometimes more. The logs are full of Failed to find Server Action "x". Mismatching ids of server actions are known to cause page reloading, so I'm assuming for the moment that the log errors and the reloading share a common cause. |
Beta Was this translation helpful? Give feedback.
-
|
I have personally tried all possible fixes but still have the issue. I am personally contemplating to never use nextjs at all after this. every upgrade breaks things. i tried older versions and newer version nothing changes. and react2shell issue as well nothing changes |
Beta Was this translation helpful? Give feedback.
-
|
Ok I think we're out of the woods. The page reloading loop was related to the nextjs upgrade. The fast fix was to downgrade to a (patched) v15. The failed to find server action is not impacting the user experience. We'll keep watching it but our app is working. |
Beta Was this translation helpful? Give feedback.
-
|
I have been getting these error logs in production as well. The confusing part is that I'm not using server actions at all in my codebase. I've already reviewed the documentation here: https://nextjs.org/docs/messages/failed-to-find-server-action, but I can't wrap my head around why I'm seeing this error. |
Beta Was this translation helpful? Give feedback.
-
|
any solution for this? Error: Failed to find Server Action "x". This request might be from an older or newer deployment. |
Beta Was this translation helpful? Give feedback.
-
|
Same here This happening only in prod (coolify), i guess. |
Beta Was this translation helpful? Give feedback.
-
|
In our recent experience, Failed to find Server Action "x" will not put your CPU at 100%, but cryptomining crap arriving via react2shell will. Look carefully at what's running on your box. |
Beta Was this translation helpful? Give feedback.
-
|
Been having this error for the past month as well. Recently massively increased, I assume from attackers trying to test react2shell exploit. Still, extremely annoying to not have a way of dealing with this error. At the very least I wish they would change it to a warning, which it seems to have previously been. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe it's not a discussion anymore but really an issue? I think so! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
in production I keep getting
"[Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Original error: Cannot read properties of undefined (reading 'workers')]"
which then completely destorys backend of the app then users can't even login or logout or perform any other actions.
when i rebuild the project and it passes the ci/cd and deploys it for some time works without problems then in couple of hors this happens randomly. I haven't been able to find anything related to this as well. anyone have any idea how to solve this?
Additional information
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions