Replies: 3 comments 2 replies
-
did you configured the redirect url correctly in discord? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I did set up the redirect URL as the following: |
Beta Was this translation helpful? Give feedback.
2 replies
-
This is likely an issue with your setup. I tried it multiple times, and multiple accounts, and it works correctly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description 🐜
I am trying to use DiscordProvider to connect with Discord OAuth.
I am successfully getting Discord OAuth authorization page, and am successfully redirected to
localhost:3000
, but mysession
is currentlyunauthorized
and I am not signed in.Toggling
debug
to true in[...nextauth].js
show me a correct[next-auth][debug][OAUTH_CALLBACK_RESPONSE]
informations, but session doesn't change and return{data: null, status: "unauthenticated"}
.I tried signing in with Github and did not encounter any problem.
Is this a bug in your own project?
No
How to reproduce ☕️
.env.local.example
to.env
DISCORD_ID
andDISCORD_SECRET
in.env
file.[...nextauth].js
Screenshots / Logs 📽
No response
Environment 🖥
System:
OS: Windows 10 10.0.22000
CPU: (8) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Memory: 1.91 GB / 15.92 GB
Binaries:
Node: 16.8.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
npm: 7.21.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.22000.120.0), Chromium (96.0.1054.34), ChromiumDev (97.0.1072.13)
Internet Explorer: 11.0.22000.120
npmPackages:
next: ^12.0.1 => 12.0.4
next-auth: ^4.0.1 => 4.0.1
react: ^17.0.2 => 17.0.2
Contributing 🙌🏽
No, I am afraid I cannot help regarding this
Beta Was this translation helpful? Give feedback.
All reactions