I have supertokens-frontend running on localhost:3000 and different project for backend on localhost:3002 from UI when I am trying to login to google, I get "recipeImplementation.js:163 GET http://localhost:3002/auth/authorisationurl?thirdPartyId=google 404 (Not Found)" but localhost:3002 is up

What version of NodeJS SDK is supported on SuperTokens core? Because I'm running : supertokens-node

14.0.2

and NodeJS SDK

18.16.0

and I get this error: "The running SuperTokens core version is not compatible with this NodeJS SDK."

Hey guys, we have implemented supertokens in our app and using COOKIE as Token transfer method. But every time we try to login it's stuck in infinite refresh calls. Can anyone help!?

So I'm getting this error when calling `SuperTokens.init`: > Please provide a valid URL path This is my config

ts
SuperTokens.init({
  supertokens: {
    connectionURI: "http://127.0.0.1:3567",
  },
  appInfo: {
    appName: "SuperTokens Testing",
    websiteDomain: "http://localhost:3000",
    apiDomain: "http://localhost:3000",
    apiBasePath: "/auth",
  },
  recipeList: [
    EmailPassword.init(),
    Session.init(),
  ],
});

Any idea why I'd be getting this error? Seems like the URLs I have are valid.

Hi. Am trying to run

supertokens-postgres

docker container in my local providing it a postgres connection string of

neon db

. It is failing with the following error

What caused the crash: Driver org.postgresql.Driver claims to not accept jdbcUrl, jdbc:postgres://ep-fragrant-firefly-243626.us-west-2.aws.neon.tech/neondb?allowPublicKeyRetrieval=true

. Kindly help. 🙏

Hello, idk if this is the right channel but im having problems with apple sign in Im unable to sign the jwt with the key apple provided, the jsonwebtoken library gives me the error

secretOrPrivateKey must be an asymmetric key when using ES256

Hi, I have update Supertokens core to 5.0 and updated supertokens-node to 14.1.1 (latest) but when I try to login it says SOMETHING_WENT_WRONG_ERROR with error 500 Node express backend log:

data: { error: 'invalid_grant', error_description: 'Bad Request' }
POST /auth/signinup 500

should I update any of my node codes after updating to core 5.0?

Is there any sort of thing like a "best practice audit?" I feel like we're (still) regularly encountering major issues with SuperTokens slowing down our Next.js application (far more than I ever experienced with Auth0 before) and the performance is really a problem.

Any ideas on this "RESTART_FLOW_ERROR". Signing up via passwordless and getting internal server error. Nodejs logs gave this error message

Redirect to mobile app after post login on web with the tokens