Getting the following error when trying to send a verification e-mail:

[INFO] 05:38:57 ts-node-dev ver. 2.0.0 (using ts-node ver. 10.9.2, typescript ver. 4.9.5)
API Server listening on port 3001
Error: 140384285034368:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

where my smtp settings are:

ts
let smtpSettings = {
    host: "mail.privateemail.com",
    authUsername: "no-reply@website.com",
    password: "password",
    port: 587,
    from: {
        name: "Website No Reply",
        email: "no-reply@website.com"
    },
    secure: true
}

Tried switching to port 465 as well but that times out the connection w/ a 504 error and has the following server side error after 2 minutes:

Error: Connection timeout
    at SMTPConnection._formatError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:790:19)
    at SMTPConnection._onError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:776:20)
    at Timeout.<anonymous> (/app/node_modules/nodemailer/lib/smtp-connection/index.js:235:22)
    at listOnTimeout (internal/timers.js:557:17)
    at processTimers (internal/timers.js:500:7)

I tried testing it in java like so and this does work: Ran some [tests]() on . so not sure what I'm doing entirely wrong on the NodeJS back end not sure if relevant at all but I am using NameCheap's mail service (

privateemail.com

) with the DNS handled through Cloudflare. Followed the instructions Namecheap provides [here]() & [here]() Hope that's everything you might need to assist me with my issue

Hi, I would appreciate some help with getting session authorization to work with a second api. I have NextJS 14 setup with app router and a backend api with Express. Server sided components are getting 'unauthorised' responses from the Express api.

ERROR [ExceptionsHandler] Received response with status 401 and body

Hi there, I’ve got a question around recipe user id usage for email verification please as I’m not sure if there is a bug in

getUser

or I just don’t understand how user id mapping is supposed to work between recipe user ids and external ids. Currently we’re mapping our users to an external id with

createUserIdMapping

after signing them up. We then verify their emails using the external id as it’s the id returned by calling

getUser

. Once the email is verified, a row is added to

emailverification_verified_emails

with the external user id as the

user_id

in the database. This works well as the email verification claim

st-ev

is

true

in the access token jwt and if I call

isEmailVerified

with the external user id converted to a recipe user id then it returns true.
The problem seems to be with

getUser

as it returns a list of

loginMethods

but the

verified

flag is false even though

isEmailVerified

returns true if I check using the same

recipeUserId

and email returned in the login method. The email verification claim for this user is

true

in the access token too. However if I change the logic to verify the email based on the supertokens user id instead, then

getUser

will return the login method

verified

as true but the email verification claim

st-ev

is false. I may be misunderstanding how the different ids are supposed to be used but it seems like

getUser

may be returning the verification status of the email login method incorrectly please?

Getting this error on Google login success. Though login is happening fine.

Error: No access, refresh token, API key or refresh handler callback is set.
    at OAuth2Client.getRequestMetadataAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:272:19)
    at OAuth2Client.requestAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:371:34)
    at OAuth2Client.request (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:365:25)
    at createAPIRequestAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis-common/build/src/apirequest.js:273:31)
    at createAPIRequest (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis-common/build/src/apirequest.js:49:9)
    at Resource$Userinfo.get (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis/build/src/apis/oauth2/v2.js:104:58)
    at Object.<anonymous> (/Users/hitesh/dev/jwt_supertokens_hasura/dist/supertokens_config.js:117:57)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/hitesh/dev/jwt_supertokens_hasura/dist/supertokens_config.js:5:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Any suggestions?

Is it a bug, when the user metadata in the dashboard is empty, but it is in the db. Or just not implemented yet because of beta

hi, is it expected that using Supertokens with next.js disables static optimization entirely? Our entire app is protected, so we get this error in the Vercel logs:

Warning: You have opted-out of Automatic Static Optimization due to `getInitialProps` in `pages/_app`. This does not opt-out pages with `getStaticProps`

This causes some strange downstream issues for us, because now everything in our client needs to get rendered via serverless functions

Is there a pricing guidance on upcoming multi-tenant and oauth workflow features? We are in process of revamping very very old .net enterprise code with js.

Is is possible for Frontend(Next js) to get the user meta data ?

Hello, I've implemented emailpassword recipe with fastify node.js backend and vue 3 frontend. I did the rest api endpoints authentication using verifySession as per the documentation. But whenever the access token expires it doesnt get refreshed through refresh token and im getting an error message: "try refresh token". I dont understand where im going wrong.