hey, I am using a NestJS backend (with Fastify adapter). I've followed the full guide here - https://supertokens.com/docs/session/nestjs/guide (with a self hosted supertokens core). I have the setup mostly working but running into CORS issues. (api listening on

http://localhost:3001

and ui running on

http://localhost:3002

)

app.enableCors({
    origin: ['http://localhost:3002'],
    allowedHeaders: ['content-type', ...supertokens.getAllCORSHeaders()],
    credentials: true,
  });

It looks like the CORS policies are not being applied correctly to the endpoints that supertokens middleware adds, ex. /auth/session/refresh CORS is applied correctly to the rest of my NestJs endpoints and my react UI at localhost:3002 can query all my regular endpoints but any requests to supertoken middleware endpoints fail with the error below (even though the preflight to /auth/session/refresh seems to be successful 204

Access to fetch at 'http://localhost:3001/auth/session/refresh' from origin 'http://localhost:3002' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

If the supetoken-core is running in docker, How to allow cors origin? I am getting this error - "from origin 'http://localhost:3001' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Credentials' header in the response is '' which must be 'true' when the request's credentials mode is 'include'."

Is there a health check endpoint for the service using the backend sdk? I mean is there a healthcheck route that the middy middleware injects? I know there is one for supertokens-core.

I got 405 when signin/up. I am using NextJS and passwordless login. (Phone) I have

pages/api/auth/[[...path]].tsx

and it's content is same as doc. This is my appInfo

export const appInfo = {
  appName: NAME,
  apiDomain: DOMAIN,
  websiteDomain: DOMAIN,
  apiBasePath: "/api/auth",
  websiteBasePath: "/auth"
}

I can see UI in

<DOMAIN>/auth

, but when I provide phone number and click continue, I got this.

[Error] Failed to load resource: the server responded with a status of 405 (Method Not Allowed) (refresh, line 0) <DOMAIN>/api/auth/session/refresh

[Error] Failed to load resource: the server responded with a status of 405 (Method Not Allowed) (refresh, line 0)
<DOMAIN>/api/auth/session/refresh

[Error] Failed to load resource: the server responded with a status of 405 (Method Not Allowed) (refresh, line 0)
<DOMAIN>/api/auth/session/refresh

[Error] Failed to load resource: the server responded with a status of 405 (Method Not Allowed) (code, line 0)
<DOMAIN>/api/auth/signinup/code

here

http://localhost:3000/auth?redirectToPath=

I'm getting this error ->

Unhandled Runtime Error
TypeError: style.toLowerCase is not a function

This after upgrading my supertokens-auth-react, supertokens-node, and supertokens-web-js

Hello. Is https://artifacthub.io/packages/helm/graphql-hive-subcharts/supertokens your official Helm repository for Supertokens Core?

Hi, I followed the nestjs setup guide and when I went to auth/dashboard it showed a server error. Nest app shows this error: SuperTokens core threw an error for a GET request to path: '/apiversion' with status code: 401 and message: Invalid API key. The connection uri and api key in nest are the ones provided in the managed service, I don't know what could be wrong.

Hey @war_ace when you get the fetch error, does it make an api call to the backend or error out before the api call is actually made?

Does anyone getting a blank screen after signup in supertoken saas?

Hello support. I'm tryng to setup the front end sdk for react native on a expo project with react native web. When i try to use the init function. it says that the domain name is invalid but am pretty sure it is and have tested with postman. is there something that im missing or it could be something about the expo and react native web itself that are not compatible. I also tried the web version on it and it seem like it worked. but i dont know if that will be able to work on the andoid and ios side of the app. Ty for you help and if there anything else you need im glad to provide it