I’m not sure what’s going on here but I’m hoping for a solution. This is very strange and I’m not sure what information to provide aside from a screenshot of what is happening.

I have set up a next.js app with next-auth.js, authenticating with a custom OIDC identity provider. I’m currently using next-auth version 5.0.0-beta.19, which I believe is part of the proposed migration to auth.js.

after creating my next auth file :

I have been trying to debug this since a while now but I can’t can somwone help me with this. Here I am using next-auth the route just keeps on redirecting to dashboard causing error.

I’m using next-auth 5.0.0-beta.19 and next 14.2.4.
I have a modal login component so that you can login from any unprotected route. This is my Next-Auth configuration and authorize works exactly as expected.

My app is running fine on my local env but after I deployed it on vercel, I am not able to sign in because it’s getting redirected to /api/auth/error and displaying the following message:

I have successfully implemented a payment system where users can pay with cryptocurrency, and their balance gets updated accordingly. The server-side logic works perfectly, and the balance is correctly updated in the database.

I have an auth.js file that authenticates users by checking a PostgreSQL database:

I have what seems to be a conceptual doubt about where and how to implement user role logic in a next-auth app and which approach is the most conventional.

Just trying to figure out a few things here: