CallbackUrl not redirecting with Next.js middleware on Vercel

[jinsley8]

I setup a custom login using next-auth and I'm using a Next.js middleware to force login for three pages. It works fine on localhost but redirecting back to the callbackUrl does not work when hosted on Vercel.

Am I missing anything where this wouldn't work with edge functions?

// middleware.ts
import withAuth from 'next-auth/middleware';

export default withAuth(
    function middleware(req) {
        console.log('NEXTAUTH REQ', req.nextauth);
    },
    {
        callbacks: {
            authorized: ({ req, token }) => token?.user?.role === 'authenticated',
        },
        pages: {
            signIn: '/auth/connect',
            signOut: '/',
        },
    }
);

export const config = { matcher: ['/account/settings', '/propose-trade', '/trades'] };

My login function uses the following to redirect back to the callbackUrl:

const router = useRouter();
const callbackUrl = (router.query?.callbackUrl as string) ?? router.asPath;
    
const result = await signIn('credentials', {
    message: message,
    signature,
    redirect: false,
    callbackUrl: callbackUrl,
});

// Redirect to callback URL
router.push(callbackUrl);

[jacquesdev]

@jinsley8 - were you ever able to resolve this, I'm experiencing the same issue

[Linuhusainnk]

Have you got any solution for this redirecting to a specific page with callbackUrl

[p-hronesis]

I'm facing similar issue too. It redirects to http://localhost:3000/?callbackUrl=%2Fusers instead of redirecting to localhost:3000/users