server actions not working when published to vercel #10704
Replies: 1 comment
-
looking at this some more - the problem is redirecting to the signin page. I made a test button here https://next-auth-nextjs-gold.vercel.app/ which just redirects to any link. If I try and redirect to the sign in page from this deployment https://next-auth-nextjs-gold.vercel.app/auth/signin?callbackUrl=https%3A%2F%2Fnext-auth-nextjs-gold.vercel.app%2F (which is what the sign in button does) then it gives this error. I can point my browser to it and it works fine however if I redirect to the equivalent page on another deployment it redirects fine eg https://next-auth-nextjs-git-working-main-gilesbs-projects.vercel.app/auth/signin?callbackUrl=https%3A%2F%2Fnext-auth-nextjs-git-working-main-gilesbs-projects.vercel.app%2F |
Beta Was this translation helpful? Give feedback.
-
I am running the example application deployed in vercel.https://next-auth-nextjs-g2tkj0nv4-gilesbs-projects.vercel.app/
On my localhost server actions are posted to root and 303 with a {} and a redirect.
on vercel they 303 but return a not found page. The redirect url goes in the address bar but the browser does not redirect.
Does anyone know why this is?
Here's it working on my local host nb the {} returned:
this is the result on vercel
Beta Was this translation helpful? Give feedback.
All reactions