I have a strange case where a request to the signout API returns a 401 in production. What’s the reason for that? How can I solve it? The issue is that users are basically never able to sign off

Hello. I've been using the ThirdPartyEmailPassword recipe for my Supertokens setup on the backend and everything worked great. Now I actually wanted to switch to ThirdParty recipe, since I'm not really doing email password login currently in my app. But after switching the backend config to use ThirdParty recipe, the

/{apiBasePath}/signinup

route is no longer there and I can not POST to it. Can anyone suggest what could be the cause? Thanks.

my supertokens core is on v4.2. How can i get this upgraded to 6.0.X

Hey, @rp_st I have integrated supertokens passwordless receipe in backend python(fastAPI) where I used 2 endpoints /signinup/code and /signinup/code/consume It's working fine and override these both endpoints and added some logic, so our frontend react-native have to use backend API only but if we are using backend API we get session false when we are using supertokens endpoint for the same then everything is working good FE can get session True Thanks!!

Hii everyone, I have three apps running on https, and self hosted supertokens core that too running on https api.example.com example.com app.example.com I can login to example.com, it works. But when I go to app.example.com, I can see the cookies being attached to the http req, but api.example.com throws unauthorised. I have no idea what to do now. This is what I see on app.example.com

Is there a way to get ip address from userContext? Trying to get user ip address when overriding sign up function

Hey, does anyone have any experience with migrating from clerk to supertokens? Especially migrating email/password users. My company is planning to do this but we're unsure of the best approach for this. Thanks in advance. (Efficiency is very important as we'd be migrating upwards of 100k accounts)

when h3 support ? with nitro https://nitro.unjs.io/

Are there any standard approaches to verifying the user in .NET?

Hey @rp_st I am getting a 500 internal server error if the authtoken is expired. So it should give a needs refresh response instead. I have two different services, in one it is working fine, but it is giving 500 error in one.