Hey I am trying to deploy our app via Digital Ocean (with supertokens - managed service) but I am ge...

mnove.

04/29/2022, 1:51 PM

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_st

04/29/2022, 1:52 PM

rp_st

04/29/2022, 1:52 PM

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

mnove.

04/29/2022, 1:55 PM

this is the supertokens config

mnove.

04/29/2022, 1:55 PM

in the front end

rp_st

04/29/2022, 1:56 PM

Right yea. So you should visit websiteDomain/auth

rp_st

04/29/2022, 1:56 PM

To see the login screen

rp_st

04/29/2022, 1:56 PM

If that’s where your react app is hosted

mnove.

04/29/2022, 1:58 PM

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

mnove.

04/29/2022, 1:58 PM

rp_st

04/29/2022, 2:00 PM

Can you enable debug log and show me the output?

mnove.

04/29/2022, 2:00 PM

then getting 404 in the inspector

rp_st

04/29/2022, 2:00 PM

Right. Have you integrated our SDK with your backend api layer?

rp_st

04/29/2022, 2:00 PM

Node / golang or python

mnove.

04/29/2022, 2:00 PM

Yes. Node. Emailpassword recipe

rp_st

04/29/2022, 2:01 PM

Can you enable debug logs and show the output?

rp_st

04/29/2022, 2:01 PM

See the troubleshooting section

mnove.

04/29/2022, 2:04 PM

ok. can that be done even when using the managed service?

rp_st

04/29/2022, 2:05 PM

Yes. Checkout the troubleshooting section 🙂

mnove.

04/29/2022, 2:33 PM

[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.

04/29/2022, 2:34 PM

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

rp_st

04/29/2022, 2:34 PM

Can you please format it correctly?

mnove.

04/29/2022, 2:37 PM

yeah sorry ;D just added to a text file

logs

rp_st

04/29/2022, 2:38 PM

So it seems that the cookies are not getting sent

rp_st

04/29/2022, 2:39 PM

https://github.com/supertokens/supertokens-website/issues/68

rp_st

04/29/2022, 2:39 PM

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

mnove.

04/29/2022, 2:39 PM

ok will do and let you know

mnove.

04/29/2022, 2:39 PM

thanks

mnove.

04/30/2022, 1:27 PM

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_st

04/30/2022, 4:10 PM

What’s the output of the sign in API?

rp_st

04/30/2022, 4:10 PM

The response headers and status code

mnove.

04/30/2022, 4:28 PM

mnove.

04/30/2022, 4:28 PM

this is what I see

rp_st

04/30/2022, 4:29 PM

Can you enable debug logging and show me the output?

mnove.

04/30/2022, 4:29 PM

when I land on the sign in form

rp_st

04/30/2022, 4:29 PM

Also, you said this works all fine in development mode?

mnove.

04/30/2022, 4:30 PM

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_st

04/30/2022, 4:30 PM

Hmm.

rp_st

04/30/2022, 4:30 PM

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

mnove.

04/30/2022, 4:32 PM

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 )

logs

rp_st

04/30/2022, 4:33 PM

What’s is your apiBasePath?

rp_st

04/30/2022, 4:34 PM

Or if you can send the logs when the process starts

rp_st

04/30/2022, 4:34 PM

That will help

mnove.

04/30/2022, 4:37 PM

logs from SDK when the server startup

logs

rp_st

04/30/2022, 4:38 PM

Right. On the backend, you have set apiBasePath to /api/auth

mnove.

04/30/2022, 4:38 PM

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

/api

rp_st

04/30/2022, 4:38 PM

On the frontend, you need to do the same

rp_st

04/30/2022, 4:39 PM

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

rp_st

04/30/2022, 4:40 PM

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

mnove.

04/30/2022, 4:40 PM

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_st

04/30/2022, 4:41 PM

See this

mnove.

04/30/2022, 4:44 PM

mm just checked but I think it is set up correctly?

rp_st

04/30/2022, 4:44 PM

This is on the frontend?

mnove.

04/30/2022, 4:44 PM

ah damn.. no backend

mnove.

04/30/2022, 4:44 PM

sorry one sec

rp_st

04/30/2022, 4:44 PM

Yup…

mnove.

04/30/2022, 4:46 PM

this is ... sorry bit messy

rp_st

04/30/2022, 4:47 PM

I don’t think process.env exists on the frontend

rp_st

04/30/2022, 4:47 PM

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

mnove.

04/30/2022, 4:48 PM

mm I have not done that part, let me ask

mnove.

04/30/2022, 4:55 PM

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

mnove.

04/30/2022, 4:55 PM

rp_st

04/30/2022, 4:55 PM

Yeaaa. That should be /api/auth

mnove.

04/30/2022, 4:56 PM

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

mnove.

05/01/2022, 10:23 AM

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.

05/01/2022, 10:25 AM

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_st

05/01/2022, 10:25 AM

Hmm. You would need to set apiGatewayPath to /api then too

mnove.

05/01/2022, 10:27 AM

this? https://supertokens.com/docs/thirdpartyemailpassword/appinfo#apigatewaypath-optional

rp_st

05/01/2022, 10:27 AM

Yes

mnove.

05/01/2022, 10:29 AM

so you are suggesting the apiGatewayPath to the backend config ?

mnove.

05/01/2022, 10:29 AM

* to add

rp_st

05/01/2022, 10:33 AM

Yes.

rp_st

05/01/2022, 10:34 AM

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

7 Views

Previous Next

SuperTokens.com

SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).