Hello,
When I developed locally all sign-in options works properly - simple email sign in option, several oauth sign in with providers ( Google, Github, Discord).
But when I deployed it to vercel, when I click to any sign in option ( Email sign -in option works), it always gives me an error. .env local variables made with NEXT prefix, also tried by adding manualy seperate and as a whole .env file Used this tutorial as guidance for Next.js SSR auth: https://appwrite.io/docs/tutorials/nextjs-ssr-auth/step-1
Also, at Vercel's Runtime Logs got this error:
at e.redirect (/var/task/.next/server/chunks/545.js:61:10317)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async o.createOAuth2Token (/var/task/.next/server/chunks/545.js:61:32699)
at async d (/var/task/.next/server/app/sign-up/page.js:1:12389)
at async /var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:418
at async rR (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:7978)
at async r7 (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:18:1144)
at async es (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:16:26324)
at async en.responseCache.get.routeKind (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:17:1026)
at async r6.renderToResponseWithComponentsImpl (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:17:508) {
code: 400,
type: '',
response: '',
digest: '363716791'
}```
Recommended threads
- SELF HOSTING ISSUE, DATA NOT MIGRATING T...
Hey, devs, I recently tried to migrate my cloud instance to a self hosted version but my data is not transferred fully only the table structure is transferred ...
- How to determine if a user is anonymous?
This is probably a silly question, but I have not yet found a good answer. Is there a method to determine if the current session is anonymous aside from seein...
- ACTIVATE DEPLOYMENT PROBLEM...
It's not giving me the option to activate a deployment that says it's ready..