Ohhh

I added the key to the root of my server

I see. You should checkout this link if you haven't: https://github.com/supertokens/supertokens-docker-postgresql

It contains the instructions on how to run the docker image you are running

the above should start the container with the in memory db.

Gotcha

Why does

COOKIE_SECURE=true

make supertokens always throw 440 on docker?

Ohh that's https

@User yup. COOKIE_SECURE=true means that the cookies will only be send to your nodejs APIs when you are using https. If not using https, no session cookies will go through resulting in session timeout

Why does cookie_domain only work with

COOKIE_DOMAIN=127.0.0.1

on Docker? I thought 127.0.0.1 was a loopback address that means 'this container' 0.0.0.0 doesnt work, local ip 192... doesn't work nor does the name of the service in the Docker network. Only 127.0.0.1?

what is the address of your APIs? is it http://127.0.0.1 ?

It's running on docker at http://0.0.0.0:4000

But it can be accessed by name by other docker services like http://name:4000/

but neither of these work for

COOKIE_DOMAIN

only 127.0.0.1

no i mean what is the URL that's in your react native app to access your APIs?

@User , let me try and explain what cookie_domain is. Basically, you have a client (your react native app) and your server (your nodejs APIs). Your nodejs APIs are accessible via some URL. In your local dev environment, that URL can be http://127.0.0.1:400 or http://localhost:400. In your production environment, that URL is https://yourdomain.com. Now, cookie_domain is a feature that answers the following question for the client (your react native app) - "I am about to send a request to https://abc.com, for each cookie I have in my storage, which ones do I send?" In this case, only cookies that have the cookie_domain as "abc.com" will get sent. So likewise, if in your dev environment, if your nodejs APIs are accessable via http://127.0.0.1:4000, then only cookies with the cookie_domain as "127.0.0.1" will get sent to it.

Brilliant explanation @User really helpful

👍

If I have a user that's signed up already, how do I fetch the session information? Or do I need to create a new one everytime?

So do I need to do

await supertokens.createNewSession(res, userObj.objectId, jwtPayload, {})

everytime a user logs in?

> If I have a user that's signed up already, how do I fetch the session information? Or do I need to create a new one everytime? In the sign up API, you will have to create a new session, and then in subsequent APIs, you will have to use our middleware to verify sessions. > So do I need to do await supertokens.createNewSession(res, userObj.objectId, jwtPayload, {}) everytime a user logs in? Yes. Cause logging in means you verify the credentials, and then create a new session.

TypeError: Cannot read property 'hostname' of undefined

Getting this error…

Can I please see your code for the init function?

supertokens.init({ hosts: process.env.SUPERTOKEN_HOST })

SUPERTOKEN_HOST is a string

oh right. Seeing what the issue is. What version of the node lib are you using?

"supertokens-node": "^2.0.2"