NextAuth url?error=callback on production but working on localhost:3000/ #2243
Replies: 19 comments 12 replies
-
|
did you ever fix this? facing same issue :'( |
Beta Was this translation helpful? Give feedback.
-
|
For me, I needed to update my AUTH_URL environment variable on Prod to the deployed site URL |
Beta Was this translation helpful? Give feedback.
-
|
Hard to do anything without reproduction. You can see a working google example here: https://next-auth-example.vercel.app/ So most probably a user misconfiguration. |
Beta Was this translation helpful? Give feedback.
-
|
I'm facing the same issue, did you guys figure out what was the problem? I checked the configs in Vercel, Google, Code everywhere. I couldn't figure it out. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using nextjs, next-auth, vercel, google provider and only on production I can't sign in to google. I can't figure out the issue. Has anyone found a solution? |
Beta Was this translation helpful? Give feedback.
-
|
Like someone mentioned above, quite hard to assist without reproduction. However, some of the issues/mistakes that I've faced with that setup were:
|
Beta Was this translation helpful? Give feedback.
-
|
Same issue here, working fine on localhost:3000 but not in local production build. Context:
/pages/api/auth/[...nextauth].js: import NextAuth from "next-auth";
import GithubProvider from "next-auth/providers/github"
import CredentialsProvider from "next-auth/providers/credentials";
const BASE_URL = process.env.NEXT_PUBLIC_BASE_URL;
const SAVE_TOKEN = process.env.NEXT_PUBLIC_SAVE_TOKEN;
export const authOptions = {
providers: [
CredentialsProvider({
name: 'Credentials',
credentials: {
password: { label: "Password", type: "password" }
},
async authorize(credentials, req) {
const res = await fetch(`${BASE_URL}/api/login`, {
method: 'POST',
body: JSON.stringify(credentials),
headers: {
"Content-Type": "application/json",
'Authorization': `Bearer ${SAVE_TOKEN}`
}
})
const user = await res.json()
if (res.ok && user) {
return user
}
return null
}
})
],
callbacks: {
async signIn({user, account, profile, email, credentials}){
const isAllowed = true;
if (isAllowed){
return true
} else {
return '/editor/unauthorized'
}
},
async redirect({ur, baseUrl}){
return '/editor'
}
}
}
export default NextAuth(authOptions)callbacks.signIn() executes in dev mode, not in prod build, same thing with callbacks.redirect() Here's dashboard.js, where I'm trying to get a user signed in: import { SignIn, SignOut } from "./actions";
import { getServerSession } from "next-auth";
import { authOptions } from "@/pages/api/auth/[...nextauth]"
export const dynamic = 'force-dynamic';
export default async function EditorMainPage() {
let session;
const [sessionRes] = await Promise.allSettled([getServerSession(authOptions)]);
if (sessionRes.status === "fulfilled") {
session = sessionRes.value;
} else {
console.error(sessionRes);
}
return (
<div>
{session ? <SignOut /> : <SignIn />}
</div>
)
}actions.js: 'use client';
import { signIn, signOut } from 'next-auth/react';
export function SignOut() {
return (
<button onClick={() => signOut()}>
→ Sign out
</button>
);
}
export function SignIn() {
return (
<button onClick={() => signIn()}>
<div>Sign in</div>
</button>
);
}and these are the requests headers I'm getting in prod build only: ` Request URL: http://localhost:3000/api/auth/error?error=fetch%20failed |
Beta Was this translation helpful? Give feedback.
-
|
did it got fixed cause i am getting the same thing with google provider in production |
Beta Was this translation helpful? Give feedback.
-
|
you need to change the auth url localhost:3000 in env file to the url on production |
Beta Was this translation helpful? Give feedback.
-
|
I'm facing the same issue. Has anyone find any solution for this ? |
Beta Was this translation helpful? Give feedback.
-
|
[Update] |
Beta Was this translation helpful? Give feedback.
-
|
paste the source code link |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here :( |
Beta Was this translation helpful? Give feedback.
-
|
My problem was that production database was not up to date. I'm using platnetscale where a branch is used for development and another branch for production. To update the database schema, you can either create a migration: then deploy it: Or manually update the database url in your .env file and run |
Beta Was this translation helpful? Give feedback.
-
|
My database in production is updated... I don't know I m getting this error too :/ |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here. But until a couple of days ago everything was working smoothly. How is this even possible? |
Beta Was this translation helpful? Give feedback.
-
|
The error seems to be there only from iOS mobile. I report the error: |
Beta Was this translation helpful? Give feedback.
-
|
I ran into this error before I added updated my environment variables on production. |
Beta Was this translation helpful? Give feedback.
-
|
If you deploy from Vercel it overrides the environment variables defined within the UI with the file. I'd be careful with .env or .env.local too. |
Beta Was this translation helpful? Give feedback.
-
|
There are several things to consider when deploying from local to production:
|
Beta Was this translation helpful? Give feedback.
-
|
Same issue here. In localhost everything is working smoothly. How is this even possible? |
Beta Was this translation helpful? Give feedback.
-
|
Do u solved this? Facing the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
it's most likely something wrong with your environment variables or auth setup |
Beta Was this translation helpful? Give feedback.
-
|
Something wrong here? app/api/auth/[...nextauth]/route.ts import User from "@/app/server/user/model";
import NextAuth from "next-auth";
import CredentialsProvider from "next-auth/providers/credentials";
import GoogleProvider from "next-auth/providers/google";
import bcrypt from "bcryptjs";
import dbConnect from "@/app/server/db-connect";
const handler = NextAuth({
providers: [
GoogleProvider({
clientId: process.env.GOOGLE_CLIENT_ID as string,
clientSecret: process.env.GOOGLE_CLIENT_SECRET as string,
authorization: {
params: {
prompt: "consent",
access_type: "offline",
response_type: "code"
}
}
}),
CredentialsProvider({
name: "Credentials",
id: "credentials",
credentials: {
email: { label: "Email", type: "text" },
password: { label: "Password", type: "password" },
},
async authorize(credentials) {
await dbConnect();
const userFound = await User.findOne({
email: credentials?.email,
}).select("+password");
if (!userFound) throw new Error("Invalid credentials");
const passwordMatch = await bcrypt.compare(
credentials!.password,
userFound.password
);
if (!passwordMatch) throw new Error("Invalid credentials");
return userFound;
},
}),
],
session: {
strategy: "jwt",
},
callbacks: {
async jwt({ token, user }) {
if (user) token.user = user;
return token;
},
async session({ session, token }) {
session.user = token.user as any;
return session;
},
},
secret: process.env.NEXTAUTH_SECRET as string,
});
export { handler as GET, handler as POST };Vercel Enviroment Variables
|
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue, getting Now I'm not getting an error anymore, but after sign in I'm redirected to my "/" page instead of the one used in the signIn function Anyone have an idea why the sign in doesn't redirect to my |
Beta Was this translation helpful? Give feedback.
-
|
In mine case the issue was related to wrong postinstall script for prisma, Then I just updated my postinstall script |
Beta Was this translation helpful? Give feedback.
-
Wow. This really worked. Just changing the postinstall:prisma generate to postinstall:prisma migrate deploy in the package.json file. Thank you so much. |
Beta Was this translation helpful? Give feedback.
-
|
In my case I've wrongly copied the development credentials instead of production credentials. Remember that you should have separate credentials for development (http://localhost:3000) and production, so be aware of copy the correct one. On the other side, I'm not sure in which level this errors messages can be improved to facilitate. |
Beta Was this translation helpful? Give feedback.
-
|
Same issue, looked through the logs on my vercel deployment to find my client secret was not being inferred correctly. Then checked my production environment variables to see I had typed the wrong variable for client secret, I had AUTH_CLIENT_SECRET instead of AUTH_GOOGLE_SECRET |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue and realized I had not set up my database tables, so I could not add a new database row to the user table on auth register or login for sessions. After setting up the database, it worked for me. I hope this helps. |
Beta Was this translation helpful? Give feedback.
-
|
In my case i forgot to add the 0.0.0.0 IP address (allow all IP addresses to access cluster) to my mongoDB Network Access list. Therefore it worked fine on local env (as that IP address is auto added to list) but not on secure staging and prod env. |
Beta Was this translation helpful? Give feedback.
and others
-
My development next auth google provider is working but on production (vercel) is gives an error=callback.
On production, I m still able to login with credentials but not with google provider
Beta Was this translation helpful? Give feedback.
All reactions