yes, it seems API calls are taking 4 to 5 seconds. Initially I thought my implementation. But I tried this repo: https://github.com/supertokens/next.js/tree/canary/examples/with-supertokens and also the ReactJS implementation. they both took similar time.

So it seems to be the problem of cold start in serverless functions. Normally this is solved by keeping the serverless functions warm by sending a periodic ping to them.

Also, are you using try.supertokens.io as the connection URI? That instance is located in India region and if you are not close to that, that may add further delays

so, would it be better to have a self hosted implementation to improve the latency?

Yea. for sure. Or you could sign up and use our managed service to deploy the core in a location closer to where the lambda functions run.

ok got it. Thanks for the response @User . Else I would have been running in circles.

Happy to help 🙂

Hey all, I am setting up Supertokens with Next.Js project and Flask. So my backend APIs' are running on Python flask on Http://localhost:5000/ and Next.js App is running on http://localhost:3000/. Using Managed service as Core. Followed Next.Js steps and can see the login page but when trying to signup or login I am getting CORS errors. Questions: Do I need any changes to Flask to make backend work or not? How to fix CORS errors? Please advise. Thanks in Advance.

NextJs_Flask Setup Questions

Hi everyone. 👋 I hosted my supertokens core behind a reverse proxy at example.com/supertokens. I'm using

connectionURI: 'https://example.com/supertokens/'

, but it seems like my backend is trying to make requests like

https://example.com/apiversion

. Does supoertokens support using a base path/prefix for the connectionURI? Seems like it is ignored.

@User we don't support base path for the connection URI :(. You will have to give a sub domain for the core. If you'd like this feature, please feel free to open an issue about this on our github.

Is there any examples of using supertokens with a custom UI for us non-react users? I'm having a hard time with that.

Hey! there is a blog post about how to setup social login with custom UI that might help: https://supertokens.com/blog/adding-social-login-to-your-website-with-supertokens We are also working on a non react SDK which will provide helper functions like

signIn

,

signUp

etc so that you don't have to make API calls manually.

@User so, I'm making a POST to

/auth/signin

with

rid: 'emailpassword'

header. I do get back a 200 with the json and the tokens in the set-cookie response headers. However, I'm a bit lost on what I should do after that. More specifically,

await SuperTokens.doesSessionExist()

returns false.

Have you called init on the supertokens-website repo? ANd on the backend, have you added session.init()? Perhaps you can share your frontend and backend config here.

@User Here you go. Context: I'm trying to use the JWT feature to integrate with Hasura. Frontend config:

js
SuperTokens.init({
  apiBasePath: '/api/auth',
  apiDomain: 'https://my.website.com'
});

Backend config:

js
supertokens.init({
  framework: 'fastify',
  supertokens: {
    connectionURI: process.env.SUPERTOKENS_URL,
    apiKey: process.env.SUPERTOKENS_API_KEY
  },
  appInfo: {
    appName: 'My Website',
    apiDomain: 'https://my.website.com',
    websiteDomain: 'https://my.website.com',
    apiGatewayPath: '/api'
  },
  recipeList: [
    EmailPassword.init(),
    Session.init({
      jwt: {
        enable: true
      }
    })
  ]
});

You need to set

apiBasePath

on the backend as well.

to

/api/auth

. And you can remove

apiGatewayPath

(unless you are using something like AWS's staging environment.

So, here's the situation, my backend is at

https://my.website.com/api

, which means that supertokens endpoints are at

https://my.website.com/api/auth

Yes. So you need to set

apiBasePath

on both frontend and backend to

/api/auth

And you can remove

apiGatewayPath

Then try again

@User the problem is that now my endpoints are at

https://my.website.com/api/api/auth

That's why I used

apiGatewayPath

.

I guess the frontend supertokens needs an

apiGatewayPath

as well, but I don't think that's an option.

That's odd. Using this on the backend config:

appInfo: {
    appName: 'My Website',
    apiDomain: 'https://my.website.com',
    websiteDomain: 'https://my.website.com',
    apiBasePath: '/api/auth',
  },

Will expose the APIs on

https://my.website.com/api/auth

@User Yes, but that assumes that the backend is running at root

ah i see.. okay. So the backend doesn't see

/api

part

Exactly.