next-auth local vs deployed error

I did a vanilla setup with the t3 stack, setup my db on supabase, setup dicsord Oauth2 with Redirects. Logging in works in on localhost, but I get a callback error when It's hosted on vercel. I setup the callback URI for the domain vercel generates. I am not sure if I am missing a step. error url
https://t3-auth-test-three.vercel.app/api/auth/signin?error=Callback
https://t3-auth-test-three.vercel.app/api/auth/signin?error=Callback
1 Reply
Steven
Steven4mo ago
Which provider are you using for users? I know with AWS Cognito you need to add in the list of callback url's in the app client. Perhaps this is something similar where you need to add the vercel domain as a callback url which would "whitelist" the domain and allow interaction between your hosted app and your provider. You mention Oauth, is that what you're using for users?