Welcome to the Kinde community

Updated 6 months ago

Authenticator error - "Something went wrong when we tried to authenticate you..."

At a glance

A community member is experiencing an issue with authentication and is unable to authenticate. The team is aware of the issue and asks the community member to provide more information, such as the NextJS SDK version, deployment platform, browser, and whether the issue can be reproduced locally. The community member responds with the details requested and mentions that the issue is working on Safari but not on the ARC browser. The team suggests the community member review a workaround posted by another community member on Discord. Ultimately, the issue resolves itself without any action from the community member, but the team requests the community member to record the environment and logs if the issue appears again.

Useful resources
Hmmm am I the only one not being able to authenticate ?
Attachment
image.png
O
I
7 comments
Hey @IkiTg07,
Our team is aware of this issue. Are you able to check a few things for me:
  1. Are you using NextJS SDK? If so what SDK version?
  2. Did you deploy your code to Vercel/Cloudflare/something similar?
  3. Are you using Chrome when experiencing this issue? If so what version of Chrome are you using? Can you check if this issue occurs for you on e.g. Safari?
  4. Can you reproduce this issue locally too?
Hey, so
  1. Yes and the version I use is "@kinde-oss/kinde-auth-nextjs": "^2.3.3"
  2. I deployed using Vercel
  3. I’m using ARC Browser. As for the version right now I can’t tell. It’s working on safari
  4. I has the same behavior locally
I can’t tell right now if it’s working on arc or chrome because I’m not with my computer but it worked in prod on vercel using safari
Hey @IkiTg07,
Thanks for getting back to me.
It seems like you are having the same issue as the community member here: https://discord.com/channels/1070212618549219328/1263615687222362112/1267709887027347548

I posted details the issue and a video from Peter explaining a workaround for the issue.
Are you able to review the details Peter posted and see if it fixes your issue?
I just got back home and weridly enough, without any action from me it's working
Weird. Please let me know @IkiTg07 if it appears again and try to record the state of your environment (and any logs) at that point so we can try replicate it.
Add a reply
Sign up and join the conversation on Discord