500 Error on Kinde Server - Password Set Form with Existing Email

Hello Kinde Team, Getting a 500 Internal Server Error on Kinde's server when a user tries to register with an email that already exists. The error occurs on Kinde's UI before any request reaches our backend. Steps i followed to get said error: 1. In Kinde Dashboard → Users, find an existing user with email (e.g., user@example.com) 2. In my app, start new user registration Enter: First name: different from existing user Last name: different from existing user Username: different from existing user Enter the same email as the existing user (user@example.com) Complete email verification (enter code) Set password and confirm password 3.Click Continue Result: 500 Internal Server Error from Kinde's server Expected : Gracefully let user know user the email already exist and redirect to login Observed : 500 error page <attached ss> Configuration: Multiple connection types enabled: Email+Password and Username Questions : 1. Is there a way Kinde prevents this at the UI level before form submission?, I see the login_hint is not useful in the registration scenario. 2. Is this a known issue with multiple connection types? 3. What is the recommended approach to prevent duplicate registrations?
No description
7 Replies
Koosha-Kinde
Koosha-Kinde2w ago
Hello, Ranjana, Thank you for reporting this issue and providing the detailed steps. I am currently working to reproduce this on our end to better assist you with your specific questions. To help me investigate, could you please let me know which SDK you are using? I will get back to you as soon as I have an update.
Ranjana_Raghavan
Ranjana_RaghavanOP2w ago
Hi Nathaly, Thank you so much for getting back to me ,really appreciate the quick response! Here’s my current configuration for reference: Frontend (SvelteKit): @kinde-oss/kinde-auth-sveltekit: ^2.2.3 Backend (Express): @kinde-oss/kinde-node-express: ^1.6.0 Please let me know if you need any more details from my side.
Koosha-Kinde
Koosha-Kinde2w ago
It is my pleasure. Thank you for these, I will get back to you with an update soon Hello Ranjana,
This is to inform you that as I have been unable to reproduce the issue, I have escalated the matter to the team for additional investigation. I will keep you posted. Hello, Ranjana. Thank you for your patience as we investigated the 500 error occurring during user registration. I was able to reproduce and validate the issue you reported. This behavior is unexpected, and as a result, I have officially reported it to our development team as a bug. It is now in the process of being validated and prioritized for a fix. To answer your specific questions: 1. Is there a way Kinde prevents this at the UI level? Yes, the system is designed to handle this gracefully, but a bug is currently preventing that for certain configurations. 2. Is this a known issue with multiple connection types? So far, our investigation has found issues occurs specifically with these connection types: * Password connection + Username * Passwordless connection (Username + Code) 3. What is the recommended approach to prevent this? This should indeed be handled by Kinde's system. While we work on a permanent resolution, I have two suggestions for the interim: 1. I can investigate a potential temporary fix or workaround for you, if one is available. 2. Alternatively, we can await the official fix once it is developed and validated. Please let me know which path you would prefer. We appreciate you bringing this to our attention and look forward to your response.
Ranjana_Raghavan
Ranjana_RaghavanOP2w ago
Thanks for the update Nathaly, will get back to you soon
Koosha-Kinde
Koosha-Kinde7d ago
Thank you, I will be here
Ranjana_Raghavan
Ranjana_RaghavanOP6d ago
Thanks Nathaly, will wait for the official resolution from Kinde's side. request to let me know when its available. Meanwhile do you have any suggestions , we could follow to avoid this issue temporarily?
Koosha-Kinde
Koosha-Kinde5d ago
Hello Ranjana, Thanks for getting back to me. The team is already working on a fix and will share an ETA as soon as it's available. I am following up with them to confirm the timing. In the meantime, I am exploring all available options to find a temporary workaround for you, if possible. I will get back to you within two business days.

Did you find this page helpful?