Yes. You will need to set the apiBase path to /api/auth on backend and frontend.

i wonder how it worked in dev and testing.. 🤔

@User on dev, the frontend and backend runs on port 3000 and 5000 respectively. On the server, we have configured the nginx to route requests to /api to go the backend process, and every other request to go the frontend process.

Got it. Does nginx strip away the /api?

no it doesn't

ok. So then setting apiBasePath to /api/auth on front and back should work. If the refresh API call returns 401 (when not logged in), it means you have configured it correcly.

okay, will try.

I can also get on a quick call to help out in case this error persists!

That can be super helpful. Thanks I'll let you know in a little while.

@User we were able to get it work after adding

apiBasePath

to both backend and frontend. 😄

great!!

@User What is the easiest way to see the list of users who have signed up?

Thanks! Is there is web UI as well?

not yet..

got it, curious if it is in the roadmap

yes. It is.

Awesome!

Hello, I have a question. I've been using a hosted dev environment for some time without any issue but this morning my requests all return error 500 "No SuperTokens core available to query". When I went to the dashboard, I saw that the env was "restarting" and thought it was the cause but it is now "active" and I still have the error 500. Would you have an idea of what could be the cause ? Thanks by advance !

@User can you please send your connectionURI? Without your API key

hi @User here it is :

supertoken_url=https://4768a1a1b88611eba14af57593aa338f-eu-west-1.aws.supertokens.io:3567

It does seem to be working fine. Are you still getting a 500 error code from it?

I mean are you still getting the "No SuperTokens core available to query" error?

well I just tried again and yes

Okay. Checking on our side..

thank you 🙂 I'm going to try and restart everything again to be sure

hum... could it be this one instead ? https://f7f7a66155c611eb97c9a350a8f32315-eu-west-1.aws.supertokens.io:3573

"https://f7f7a66155c611eb97c9a350a8f32315-eu-west-1.aws.supertokens.io:3573/" -> where did you get this one from? Cause it's not operational.

We are seeing why it's not working.. give us a few mins