@User adding the interceptor for axios fixed the problem. Thanks

@User just wondered what is your advice on handling this extreme case. I just turned the core off whilst being logged in as a user

when clicking on sign out whilst core is down

I get the following error

Error: No SuperTokens core available to query

problem is I never get signed out as cookies are not removed on frontend

is your advice to wrap superTokensNextWrapper in a try catch

obviously this is in an extreme case

as I will add monitoring around core

but just wanted to make sure that logged in users are not affected by this

as some of my logged in pages remain empty at moment

and do not render

as they need session validation

but the error "Error: No SuperTokens core available to query" is not handled

> problem is I never get signed out as cookies are not removed on frontend So if the core is down, this is expected to happen since you did not end up revoking the session successfully in the first place. Now you can add a

try catch

around

superTokensNextWrapper

if you'd like. But what would you do in the try / catch anyway? You would have to return a 500 error to the client anyway right? Which I believe would be currently happening.

Hi everyone Just a quick question, say im using digital ocean using 1 CPU and 1 GB RAM, how many concurrent users can login using the above mentioned VM

that can go upto 100 RPS

but if you can, make it 2 CPUs and 500 mb ram

that would be higher rps than 100

Thanks mate for the quick response

@User some more info about scaling - you can add more cores and a load balancer in front of them.. it scales pretty linearly for upto 1k RPS. That would support several millions of users without any issues at all.

Thanks mate (:

I couldn't find any information on how to change how password-reset emails get send. Like which SMTP server or service is used. It defaults to one of your services?

See this link: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/reset-password/password-reset-email

Oh. I think you are using the emailpassword recipe. So see this link please: https://supertokens.io/docs/emailpassword/common-customizations/reset-password/password-reset-email

Ah, thank you 🙂

Hi there! We're currently looking to implement supertokens with a chrome extension. Are there any specific blockers that I need to be aware of? Thanks!

Also another question, are there docs or general directions on how we can build our own front end (and maybe just call a few functions) when using reactjs? We still want to keep all the other functionalities of the sdk.

How to get the name for google and facebook providers?

@User > We're currently looking to implement supertokens with a chrome extension. Are there any specific blockers that I need to be aware of? I think it should work out of the box, but we haven't tried it yet with an extension. > Also another question, are there docs or general directions on how we can build our own front end (and maybe just call a few functions) when using reactjs? We don't expose the functions from the reactJS SDK (yet), except for the session recipe functions. For other recipes, you may want to directly call the API exposed by our backend SDK: https://app.swaggerhub.com/apis/supertokens/FDI