Good morning! I have a question about session refresh and access token. We are seeing an issue that hasn't appeared before. And it happens when we change enviroment from localhost to a hosted backend cluster. For some reason i get the error "unauthorized" specifically when trying to call supertokens.attemptrefreshsession() in my react native client. But i'm able to get a user id from supertokens.getUser()

Hello, I am planning to use SuperTokens as a self-hosted auth service. I have successfully done the docker setup connected with the DB, but I am wondering for the back-end, I see there are libraries for Node, GoLang, and python, but is there a library for Rust? If not, how can I make Rust be able to communicate with SuperTokens?

HI everyone, I am new to supertoken and docker, I am trying to follow this instruction to host the core with docker - https://supertokens.com/docs/emailpassword/quick-setup/database-setup/mysql I have a mysql server running at port 3306 and my ip address is 192.168.1.207, I run the docker command with my env variables, and I got an error saying that "Socket fail to connect to host:192.168.1.207, port:3306. Connection refused". What is wrong here? Thank for your help~

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?

Hi All, I have an Issue with supertokens-react-native. When using the signOut function, calling doesSessionExist still return true. Does anybody have the same issue ?

I'm having trouble with NestJS + GraphQL, I've seen there were older messages about this in discord but it didn't really help... Honestly I have no clue of how, according to the supertokens documentation of vanilla graphql on nodejs, this should be done:

ts
@Injectable()
export class GQLAuthGuard implements CanActivate {
  async canActivate(context: ExecutionContext): Promise<boolean> {
    const ctx = GqlExecutionContext.create(context).getContext();

    let err = undefined;
    // You can create an optional version of this by passing {sessionRequired: false} to verifySession
    await verifySession({ sessionRequired: false })(
      ctx.req,
      ctx.res,
      (res) => {
        err = res;
      },
    );

    if (ctx.res.headersSent) {
      throw new STError({
        message: 'RESPONSE_SENT',
        type: 'RESPONSE_SENT',
      });
    }

    if (err) {
      throw err;
    }

    return true;
  }
}

What's the best way to temporarily disable sign-up? I want to keep the existing users on my core.

Hello everyone, does anybody encounter this error

{t: "2023-12-22T11:15:13.063Z", message: "middleware: Started", file: "/gateway/node_modules/supertokens-node/lib/build/supertokens.js:145:22" sdkVer: "16.6.5"}
2023-12-22T11:15:13.072Z com.supertokens {t: "2023-12-22T11:15:13.072Z", message: "middleware: Not handling because request path did not start with config path. Request path: /.well-known/jwks.json", file: "/gateway/node_modules/supertokens-node/lib/build/supertokens.js:152:26" sdkVer: "16.6.5"}

We've noticed that some of our authentication-related emails are being flagged as spam by GMail (e.g. password reset). * We're using our own domain name * We're using Mailgun to send the messages * SPF and DKIM is set up correctly * The GMail message implies the risk factor is the content of the emails itself: "Similar messages were used to steal people's personal information. Avoid clicking links, downloading attachments or replying with personal information" Our next move, therefore, will be to change the content of the message so that it doesn't resemble the default ST template. Was wondering if other people had faced something similar and had success with a different approach?

I'm running a Supertokens managed instance in production (on my Flask Python backend, which is hosted on Google Cloudrun). Since it's inconvenient to access the dashboard URL through cloudrun, I found I can run my backend locally (with production flags set) and then access the production dashboard at http://localhost:8000/auth/dashboard Is this recommended / might this interfere with the instance running on prod? (e.g. if limited connections to the Supertokens instance is permitted at once)