Why this error comes sometime randomly ? Not even letting me signIn again

Hi Team, I am attempting to connect Supertokens to my PostgreSQL db running in a Heroku private space. In order to achieve this I need to pass through a client certificate, client key and CA certificate. I have all of these and have tried a multitude of ways to get the connection working through docker but was unable. I have successfully made a connection to a non-secure Postgres db in Heroku, but for production purposes, we are intending to utilise the Private Space. I initially tried to connect with 'Running SuperTokens and PostgreSQL with docker, with docker-compose' but realised that since the database is already running, it makes more sense to utilise 'Running SuperTokens with Docker and PostgreSQL without docker'. The issue I am facing now is I'm not able to pass through the certificates as an environment variable as seemingly only the following are available: POSTGRESQL_CONNECTION_URI POSTGRESQL_USER POSTGRESQL_PASSWORD POSTGRESQL_PASSWORD_FILE POSTGRESQL_CONNECTION_POOL_SIZE POSTGRESQL_HOST POSTGRESQL_PORT POSTGRESQL_DATABASE_NAME POSTGRESQL_TABLE_NAMES_PREFIX POSTGRESQL_TABLE_SCHEMA

Hey, does Supertokens work with Capacitor ( https://capacitorjs.com/ ) ?

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 ?

Hi @rp_st , I have a problem with getting 502 error for POST /session/refresh, so i want to resolve this problem, can you help me?

I have a FastAPI backend and a NextJS frontend. I want to use getServerSideProps to send the logged in user's data to my frontend. When I try to get the logged in user's data in getServerSideProps, I get { message: 'unauthorised' }. I think this is because the cookies in the browser are not sent to my FastAPI backend. Is this even possible?

hello , i am a supertoken user . i have integrated supertokens with my application. And using session context. i need to individually test react components for my unit test. but i cant seem to mock useSessionContext. could you please help me.

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

I am setting up something wrong with supertoken and I have no clue how to fix this? Does anybody have a clue? My first error in the console.log is this in the attached image.

I've got a super weird problem trying to implement Supertokens in a NextJS app for the first time. Using a NestJS backend and everything appears to be configured properly but when I try to sign up with Nest it hits my NestJS backend and then returns a 404. If I hit the exact same URL from the failed network request using CURL it works just fine eg:

http://localhost:3000/api/auth/signup/email/exists?email={email}

returns the expected result. If I visit the email exists URL directly in the browser it also prints the expected JSON. For some reason though the fetch that's getting triggered from the Next app always returns 404 🤔 Its not a CORS error... just a 404 as if the endpoint doesn't exist. I can log and see it hitting the supertokens middleware in all cases