Callback URL Error: doesn't work even though i add it to the panel
Hi! My app's login uses Kinde. Today it stopped working and we don't know why, and users get this error on screen. I already have that URL in the allowed callbacks URLs field (It has always been there), and even though I try to add it again it doesn't work. No user has been able to login today because of that. Thank u beforehand!
14 Replies
Hello, @acrv,
Based on your message, it seems this was working before but stopped functioning today. This may be due to an error on our end, such as a bug or a temporary issue.
To investigate further with the team, could you please provide the following details:
- The SDK you are using
- The SDK version number
- The authentication method(s)
Thanks in advance!
Hi! I'm using "kinde-oss/kinde-auth-nextjs": "^1.10.2". Is this enough?
Yes, let me get back to the team to investigate. Thank you!
Hello again, @acrv.
Could you confirm whether you’ve recently upgraded to the version you shared, or if you’ve been using it all along?
Could you confirm whether you’ve recently upgraded to the version you shared, or if you’ve been using it all along?
Hi, I've used the same version since 5 months ago. Just today I had the issue with the login, it worked fine until now
Thank you. The team is already investigating, and you can expect to have an update as soon as they have a result with their testing.
Hi! are there any updates?
Hello!
The team is still working on reproducing the error. I received an update yesterday with the documentation for this task. Once they are able to test it, I will let you know.
Hi! are there any updates? I don't know if this is useful, but i changed the values of the vars in the admin panel to localhost and the login worked fine in localhost, but then when i change them back to the prod urls it doesn't work. And even though i add the callback url manually or with that button, it doesn't work (but the url is written in the field, it just doesn't recognize it)
@acrv
Today, I received an update from the developer team stating that they’ve been unable to replicate the issue. To investigate further, they’ve requested any relevant logs related to your case. I’ve asked for clarification on which specific logs or details would be most helpful, and they should respond today. Once I have their feedback, I’ll follow up with you promptly. Given that it was working before, you have made no further changes recently, and it works with localhost, which suggest this is not a code issue but a configuration issue, it is a bit challenging to replicate, but I can assure you that they are actively working on the issue and giving an update daily.
In the first image you can see my env vars, and in the second and third the vars of the admin panel. They have always worked. What's strange to me is the error, because in the past i've entered wrong the env vars but the error showed it and fixing it it worked, but now the error is something that is aparently correct
btw, i'm sure the secrets are also correct
If the team has the time i can connect with them in a meeting to show them my configs, if we don't solve this soon we will have to change provider:( Our prod app (that has real users) hasn't been working in 3 days and we're using our dev stage, but we can't keep doing this
@acrv
I’ve shared this information with the team, and they will reach out soon with an update on scheduling a call, since it seems a better way to understand what may be happening indeed. In the meantime, please check for any extra spaces or hidden whitespace—this could apply to the dashboard and/or the variables.
Thank you very much!
No problem, I know it is very frustrating, especially since your site is in production. We will be in touch today.
Hey acrv,
Just jumping in here to help. We understand this is a critical issue — especially with real end-users currently unable to authenticate into your application.
While we haven’t been able to reproduce the issue on our side, we strongly recommend upgrading to the latest version of the Next.js SDK (
Just jumping in here to help. We understand this is a critical issue — especially with real end-users currently unable to authenticate into your application.
While we haven’t been able to reproduce the issue on our side, we strongly recommend upgrading to the latest version of the Next.js SDK (
v2.6.1). The version you’re using is quite outdated and missing some important fixes and improvements that may resolve what you're seeing.
Once you’ve had a chance to upgrade, please let us know how it goes. We’re keen to get this sorted and ensure it doesn’t happen again.