what's a good way to check all avaliable routes in `auth` middleware I am currently deploying super...
m
what's a good way to check all avaliable routes in
auth
middleware I am currently deploying supertokens, on fly.io . it works on my local machine. Broken on deployed
Copy code
{
2022-09-23T04:01:03Z app[1a7515c8] sin [info]  framework: 'awsLambda',
2022-09-23T04:01:03Z app[1a7515c8] sin [info]  isInServerlessEnv: true,
2022-09-23T04:01:03Z app[1a7515c8] sin [info]  appInfo: {
2022-09-23T04:01:03Z app[1a7515c8] sin [info]    apiDomain: 'https://staging.darisini.com',
2022-09-23T04:01:03Z app[1a7515c8] sin [info]    websiteDomain: 'https://staging.darisini.com',
2022-09-23T04:01:03Z app[1a7515c8] sin [info]    appName: 'Darisini',
2022-09-23T04:01:03Z app[1a7515c8] sin [info]    apiGatewayPath: '/.redwood/functions',
2022-09-23T04:01:03Z app[1a7515c8] sin [info]    websiteBasePath: '/auth',
2022-09-23T04:01:03Z app[1a7515c8] sin [info]    apiBasePath: '/auth'
2022-09-23T04:01:03Z app[1a7515c8] sin [info]  },
2022-09-23T04:01:03Z app[1a7515c8] sin [info]  supertokens: {
2022-09-23T04:01:03Z app[1a7515c8] sin [info]    connectionURI: 'https://darisini-supertokens-staging.fly.dev',
2022-09-23T04:01:03Z app[1a7515c8] sin [info]    apiKey: 'Z8bhDE4EmCrmU2auutPbLw2wMiFyPJpoFqQ2ZK9VLMUdY7ZzvzaF6FTBG4FKC76A'
2022-09-23T04:01:03Z app[1a7515c8] sin [info]  },
2022-09-23T04:01:03Z app[1a7515c8] sin [info]  recipeList: [ [Function (anonymous)], [Function (anonymous)] ]
```
r
Hey! Checkout supertokens.com/docs/fdi
What’s the error that you get?
m
Copy code
https://staging.darisini.com/.redwood/functions/auth/session/refresh
I am running out of clue 🥹
do you have any idea? what more information I can provide?
apiDomain seems to be correct, website domain seems to be correct
r
Can you enable backend debug logs and call that api?
m
sure, what information are we looking for?
does supertokens has any flag I can toggle?
for debugging?
r
The logs that are printed out when you call the api
m
okay
r
Yea. See the troubleshooting section in the docs
m
here's the log
r
These aren’t logs generated by us
When our logs are generated, you will see a com.supertokens phrase in them
m
do you mean in the core
or in supertokens-node
r
Supertokens-node
You have to give the node process an env var
DEBUG=com.supertokens
m
ah i se
let me try that
Copy code
app[55547670] sin [info]2022-09-23T04:52:51.247Z com.supertokens {t: "2022-09-23T04:52:51.247Z", message: "middleware: Not handling because request path did not start with config path. Request path: /.redwood/functions/.redwood/functions/auth/session/refresh", file: "/app/node_modules/supertokens-node/lib/build/supertokens.js:231:30" sdkVer: "11.3.0"}
okay it seems the
/.redwood/functions/.redwood/functions
is duplicated
nice, found a clue
thanks @rp_st . You have been super super helpful
r
Great!
2 Views