Failed to find server action but I am not using server actions?
Unanswered
Armenian Gampr dog posted this in #help-forum
Armenian Gampr dogOP
I have some simple websites that has a form which makes a post request to an external platform. I run nextjs self hosted using docker inside linux vps.
I don't have any use server or anything that would lead it to use Server Action. I simply use api route.js files. When i run docker exec <container> cat .next/server/server-reference-manifest.json
{
"node": {},
"edge": {},
"encryptionKey": "xxx"
}
which according to Claude says that I am not using server actions. However I every once in a while get the error Error: Failed to find Server Action "x". This request might be from an older or newer deployment.
Read more: https://nextjs.org/docs/messages/failed-to-find-server-action
at async m (.next/server/chunks/ssr/98bdcdf8..js:1:6573)
with some variations to path to the ssr file and the name of the server action. When this error occurs the entire application crashes and i cant reach the websites until i restart the container.
Does anyone know anything about this situation and how I can fix it?
I don't have any use server or anything that would lead it to use Server Action. I simply use api route.js files. When i run docker exec <container> cat .next/server/server-reference-manifest.json
{
"node": {},
"edge": {},
"encryptionKey": "xxx"
}
which according to Claude says that I am not using server actions. However I every once in a while get the error Error: Failed to find Server Action "x". This request might be from an older or newer deployment.
Read more: https://nextjs.org/docs/messages/failed-to-find-server-action
at async m (.next/server/chunks/ssr/98bdcdf8..js:1:6573)
with some variations to path to the ssr file and the name of the server action. When this error occurs the entire application crashes and i cant reach the websites until i restart the container.
Does anyone know anything about this situation and how I can fix it?
7 Replies
@Armenian Gampr dog I have some simple websites that has a form which makes a post request to an external platform. I run nextjs self hosted using docker inside linux vps.
I don't have any use server or anything that would lead it to use Server Action. I simply use api route.js files. When i run docker exec <container> cat .next/server/server-reference-manifest.json
{
"node": {},
"edge": {},
"encryptionKey": "xxx"
}
which according to Claude says that I am not using server actions. However I every once in a while get the error Error: Failed to find Server Action "x". This request might be from an older or newer deployment.
Read more: https://nextjs.org/docs/messages/failed-to-find-server-action
at async m (.next/server/chunks/ssr/_98bdcdf8._.js:1:6573)
with some variations to path to the ssr file and the name of the server action. When this error occurs the entire application crashes and i cant reach the websites until i restart the container.
Does anyone know anything about this situation and how I can fix it?
you need to reinstall your vps since it might be a sign that your vps is breached by the recent Next.js vulnerability
upgrade to latest version and see if the issue persists
Armenian Gampr dogOP
I upgraded the version of nextjs and checked through the server and nothing seemed to be out of order, and also if next runs inside docker container is there any real way for the vulnerability to make them get out on the actual server?
@Armenian Gampr dog I upgraded the version of nextjs and checked through the server and nothing seemed to be out of order, and also if next runs inside docker container is there any real way for the vulnerability to make them get out on the actual server?
no but the problem is just that the attacker will try to probe potentiall unprotected server actions so u might see those messages
Armenian Gampr dogOP
But if i dont have any server actions on the nextjs application? Or is the errors im seeing that they're just trying to access server actions even if i dont have any?
yes they're just probing it
Armenian Gampr dogOP
Ah alright, thank you