But when I call SuperTokens.doesSessionExist() it returns false. This should be true after a successful call to /signin right? And the cookies should automatically be set in my browser? I only see one cookie when I use devtools to inspect them (although I'm not sure you can see http-only cookies with devtools??)

Hello, I have a question regarding SuperTokens Core - how to debug issues related to it? App is working fine for me (dockerized), but for my friend which is running it on local machine it's throwing an error "No SuperTokens core available to query" - this occurs while trying to register (I removed post from support-questions)

It seems Next.js is still a dumpster fire compared to Remix and SvelteKit. 🤦🏿‍♂️ I will be debating whether I want to wait longer on the Next.js example again or just create a higher-order function now that's easy to understand. Next is weird. It's surprising that simple features have taken so long compared to other tools.

Hi all, I'm new to SuperTokens. I'm using PasswordLess authentication. I have followed the recipe. I do have a nice Sign In which is quite straightforward and works well, thanks for that! However, I don't have any *SIGN UP * and I don't get why. I added the first users through the Supertokens UI. I'm using NextJS. My back-end config is the following :

return {
    debug: true,
    framework: "custom",
    supertokens: {
      connectionURI:
        process.env.SUPERTOKENS_URI || "https://try.supertokens.com",
      apiKey: process.env.SUPERTOKENS_API_KEY,
    },
    appInfo: appInfo("backend"),
    recipeList: [
      PasswordlessNode.init({
        flowType: "MAGIC_LINK",
        contactMethod: "EMAIL",
        emailDelivery: {...}
      }),
      SessionNode.init(),
      Dashboard.init(),
      UserRoles.init(),
      UserMetadata.init(),
    ],
    isInServerlessEnv: true,
  };
};

Could somebody help me?

[Symbol(Response internals)]: { url: 'https://www.googleapis.com/oauth2/v1/userinfo?alt=json', status: 401, statusText: 'Unauthorized', headers: Headers { [Symbol(map)]: [Object: null prototype] }, counter: 0 } I am using signin using google using my custom ui and my backend is giving this error

Hi @rp_st , even when i resend code , then also i am able to use the old code and get success respose , but ideally this should not be the case. Any specific reason why its happening

has anyone integrated supertokens with nuxt3?

Hi, I'm getting an error when trying to follow the instructions for Third Party Email Password, but I keep getting this error :

No instance of ThirdPartyEmailPassword found.

Hi, thank you for inviting me in. My application is using Vite, React and Nodejs, using Supertokens to handle login and sign up. So we send out invitation emails with accept button linking to an address like: myapp.com/invitation/[the project id user got invited to]?email=userEmail@user.com And when click this link open, user would be redirected to the address: myapp.com/signin/?redirectToPath=[the project id user got invited to] Somehow the email param was not showing, any idea why or how I fix it? Thank you!

Hey. I am attempting to run a self-managed instance of SuperTokens. It is connected to the CloudSQL instance. To improve on my testing time etc, I decided to compose my backend container & the supertokens core together via docker-compose. My data is stored on a Google CloudSQL instance. Additionally, my express backend is run on port 3000, and the

supertokens-postgres

is run on port 3567. All of this is run on the same network. When I try to send a POST request to

/auth/signin

, I receive a

status 500

. Additionally, in my logs I receive the following error

TypeError: fetch failed
2023-12-22 06:26:56     at Object.fetch (node:internal/deps/undici/undici:11730:11)
2023-12-22 06:26:56     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-12-22 06:26:56     at async sendRequestHelper._a (/usr/src/node_modules/supertokens-node/lib/build/querier.js:51:36)
2023-12-22 06:26:56     at async Querier.sendRequestHelper (/usr/src/node_modules/supertokens-node/lib/build/querier.js:326:32)
2023-12-22 06:26:56     at async Querier.getAPIVersion (/usr/src/node_modules/supertokens-node/lib/build/querier.js:41:38)
2023-12-22 06:26:56     at async sendRequestHelper._a (/usr/src/node_modules/supertokens-node/lib/build/querier.js:85:38)
2023-12-22 06:26:56     at async Querier.sendRequestHelper (/usr/src/node_modules/supertokens-node/lib/build/querier.js:326:32)
2023-12-22 06:26:56     at async Querier.sendPostRequest (/usr/src/node_modules/supertokens-node/lib/build/querier.js:81:40)
2023-12-22 06:26:56     at async Object.signIn (/usr/src/node_modules/supertokens-node/lib/build/recipe/emailpassword/recipeImplementation.js:58:30)
2023-12-22 06:26:56     at async Object.signInPOST (/usr/src/node_modules/supertokens-node/lib/build/recipe/emailpassword/api/implementation.js:450:28)

The

localhost:3567/hello

is reachable and responsive. The other endpoints on my backend are also responsive. Could someone help me with this error please?