Hey I am trying to deploy our app via Digital Ocean with sup

Question

Hey I am trying to deploy our app via Digital Ocean with supertokens managed service but I am getting a 404 error when accessing the login page signup page I am using the same domain for the front end React and the API However the api endpoint is at api I think it might have something to do with the supertokens config in my code

rp · Answer

Hey I am trying to deploy our app via Digital Ocean with supertokens managed service but I am getting a 404 error when accessing the login page signup page I am using the same domain for the front end React and the API However the api endpoint is at api I think it might have something to do with the supertokens config in my code

rp · Answer

What s your frontend config The default login page is auth on the frontend

Mnove · Answer

this is the supertokens config

Mnove · Answer

in the front end

rp · Answer

Right yea So you should visit websiteDomain auth

rp · Answer

To see the login screen

rp · Answer

If that s where your react app is hosted

Mnove · Answer

yep and that works meaning I can see the login form or signup form But when I try to use it it throws errors

rp · Answer

Can you enable debug log and show me the output

Mnove · Answer

then getting 404 in the inspector

rp · Answer

Right Have you integrated our SDK with your backend api layer

rp · Answer

Node golang or python

Mnove · Answer

Yes Node Emailpassword recipe

rp · Answer

Can you enable debug logs and show the output

rp · Answer

See the troubleshooting section

Mnove · Answer

ok can that be done even when using the managed service

rp · Answer

Yes Checkout the troubleshooting section

Mnove · Answer

2022 04 29 14 27 36 2022 04 29T14 27 36 790Z com supertokens t 2022 04 29T14 27 36 790Z message getSession Started file workspace node modules supertokens node lib build recipe session recipeImplementation js 142 26 sdkVer 9 1 2 2022 04 29 14 27 36 2022 04 29 14 27 36 2022 04 29T14 27 36 790Z com supertokens t 2022 04 29T14 27 36 790Z message getSession rid in header true file workspace node modules supertokens node lib build recipe session recipeImplementation js 153 26 sdkVer 9 1 2 2022 04 29 14 27 36 2022 04 29 14 27 36 2022 04 29T14 27 36 791Z com supertokens t 2022 04 29T14 27 36 791Z message getSession request method post file workspace node modules supertokens node lib build recipe session recipeImplementation js 154 26 sdkVer 9 1 2 2022 04 29 14 27 36 2022 04 29 14 27 36 2022 04 29T14 27 36 791Z com supertokens t 2022 04 29T14 27 36 791Z message getSession returning undefined because idRefreshToken is undefined and sessionRequired is false file workspace node modules supertokens node lib build recipe session recipeImplementation js 161 34 sdkVer 9 1 2 2022 04 29 14 27 36 2022 04 29 14 27 36 2022 04 29T14 27 36 792Z com supertokens t 2022 04 29T14 27 36 792Z message middleware Started file workspace node modules supertokens node lib build supertokens js 158 26 sdkVer 9 1 2 2022 04 29 14 27 36 2022 04 29 14 27 36 2022 04 29T14 27 36 792Z com supertokens t 2022 04 29T14 27 36 792Z message middleware Not handling because request path did not start with config path Request path session refresh file workspace node modules supertokens node lib build supertokens js 165 30 sdkVer 9 1 2

Mnove · Answer

so this is the first part of logs i see when visiting the signin form

rp · Answer

Can you please format it correctly

Mnove · Answer

yeah sorry D just added to a text file

rp · Answer

So it seems that the cookies are not getting sent

rp · Answer

https github com supertokens supertokens website issues 68

rp · Answer

Please go through the list above and check if any of the above reasons is why it s not working

Mnove · Answer

ok will do and let you know

Mnove · Answer

thanks

Mnove · Answer

Did some experiments but unfortunately still having problems locally it all works but in prod it keeps trying to create a session and failing to do so No cookie is set in the browser and the SDK debug mode logs `2022 04 30T13 16 36 089Z com supertokens t 2022 04 30T13 16 36 089Z message getSession returning undefined because idRefreshToken is undefined and sessionRequired is false file workspace node modules supertokens node lib build recipe session recipeImplementation js 161 34 sdkVer 9 1 2 `

rp · Answer

What s the output of the sign in API

rp · Answer

The response headers and status code

Mnove · Answer

this is what I see

rp · Answer

Can you enable debug logging and show me the output

Mnove · Answer

when I land on the sign in form

rp · Answer

Also you said this works all fine in development mode

Mnove · Answer

yes in dev all good I can connect and it seems the tokens are generated properly and I get a successful redirect to the app

rp · Answer

Hmm

rp · Answer

Send over the debug logs for this env where you are getting 404s

Mnove · Answer

these are the logs from the SDK the last batch since it is firing them like crazy while I am on the sign in page ahah

rp · Answer

What s is your apiBasePath

rp · Answer

Or if you can send the logs when the process starts

rp · Answer

That will help

Mnove · Answer

logs from SDK when the server startup

rp · Answer

Right On the backend you have set apiBasePath to api auth

Mnove · Answer

this test production app is hosted at alpha hyperlane app while the API is the same domain but routed at ` api`

rp · Answer

On the frontend you need to do the same

rp · Answer

Oh Ok So the routing to api happens on its own By some proxy or a gateway

rp · Answer

So on the frontend you need to set the apiBasePath to api auth for this environment

Mnove · Answer

mmm I think it is enabled via the hosting provider Digital Ocean App Platform as you can set up HTTP Request routes that a specific component can listen to this case the server

rp · Answer

See this

Mnove · Answer

mm just checked but I think it is set up correctly

rp · Answer

This is on the frontend

Mnove · Answer

ah damn no backend

Mnove · Answer

sorry one sec

rp · Answer

Yup

Mnove · Answer

this is sorry bit messy

rp · Answer

I don t think process env exists on the frontend

rp · Answer

Can you log the values and see what it s setting it to

Mnove · Answer

mm I have not done that part let me ask

Mnove · Answer

still waiting sorry but from my logs on a built version of the React App CRA

rp · Answer

Yeaaa That should be api auth

Mnove · Answer

mmm ok let me rebuild everything and try again Will keep uou posted thanks so much

Mnove · Answer

Hey So i finally managed to get it to work So the react app was actually fine since the Vars were already applied correctly even with `process env` since they get included in the build However I had to change in the backend the supertokens config in order to have API BASE PATH to be just ` auth` while before both the front end and back end were ` api auth` So now the api base path in the front end is `api auth` while on the backend is just ` auth` I guess before it was not working because the ST middleware was not catching the route properly so it kept trying to create a session

Mnove · Answer

Locally I guess it was working fine since I am just using the `localhost 3000` and `localhost 9000` for front and back respectively while in Prod I am using the pattern `mywebsite com` for the client and `mywebsite com api` for the server Node

rp · Answer

Hmm You would need to set apiGatewayPath to api then too

Mnove · Answer

this https supertokens com docs thirdpartyemailpassword appinfo apigatewaypath optional

rp · Answer

Yes

Mnove · Answer

so you are suggesting the apiGatewayPath to the backend config

Mnove · Answer

to add

rp · Answer

Yes

rp · Answer

That s assuming that the backend code doesn t see the api part of the path Depends on how you have setup the routing