Next.js 15: Failed to find Server Action (Invalid Action Token)
Error: Failed to find Server Action "d6c41369b764bb7ec6ef4e08cfbc1fcf0da7d965". This request might be from an older build or an invalid action token.
Immediate Remediation
typescript
// 1. In next.config.ts - Configure allowed action origins if behind a reverse proxy/custom domain:
const nextConfig = {
experimental: {
serverActions: {
allowedOrigins: ['localhost:3000', 'app.mydomain.com', '*.vercel.app'],
},
},
};
export default nextConfig;
// 2. Clear client-cached build chunks after deploying:
// Hard-refresh browser (Ctrl+Shift+R / Cmd+Shift+R) or redeploy with purged edge cacheRoot Cause Analysis
Next.js cryptographically signs Server Actions per build. When a client holding an older page bundle submits an action after a production deployment or host proxy mismatch, the action hash fails validation.
Verification & Guardrails
- Always include the host domain in experimental.serverActions.allowedOrigins when deploying behind AWS ALB, Cloudflare, or NGINX.
- Ensure multi-container deployments share the same build deployment artifact.
Have a custom or uncategorized crash?
Run your trace through our in-memory client privacy sandbox for instant SRE remediation.