Hello Got supertokens running in production in combination w

Question

Hello Got supertokens running in production in combination with Hasura and an Angular Frontend Everything works except one thing The Frontend sends a request to <apiDomain> auth session refresh every 3 seconds that returns with a 404 This fills up my logs and can t be too good Can you give ma any help on that What information do you need

rp · Answer

hey < turbosepp>

rp · Answer

404 or 401

turbosepp · Answer

404

rp · Answer

can you enable backend debug logs and show me the output when this API is called Also does it work in dev

turbosepp · Answer

To be honest no dev env currently availabe as dev had to became prod fast but there should be in some days I ll try to get the backend logs one moment

turbosepp · Answer

` type http log timestamp 2023 01 16T13 37 48 382+0000 level error detail operation error path $ error resource does not exist code not found request id 13573d63 9de9 45d0 bd46 03aae1650ee5 response size 65 request mode error raw query request id 13573d63 9de9 45d0 bd46 03aae1650ee5 http info status 404 http version HTTP 1 1 url auth session refresh ip 172 19 0 1 method POST content encoding null `

turbosepp · Answer

This is from the hasura logs It s sending this refresh request there This is right

turbosepp · Answer

In my understanding it should go to the supertokens express server we set up instead Or am I wrong

rp · Answer

it should go to supertokens express server indeed

rp · Answer

what is the apiDomain that you have set on the frontend Does it point to the express server

turbosepp · Answer

Ahh seems like this is the thing I thought with apiDomain the backend API is meant not the supertokens server

rp · Answer

well it s not the supertokens core server It s the api s domain in which you have integrated our backend SDK

turbosepp · Answer

the URL of your app s API path

turbosepp · Answer

hmmm

rp · Answer

it should point to the supertokens express server that you had setup

turbosepp · Answer

yes I understand But in the express server there should be the same for apiDomain right

rp · Answer

yes

rp · Answer

apiDomain on frontend and backend should be set to the same value

turbosepp · Answer

Ok thanks

turbosepp · Answer

But then I wonder why this all worked in the first place

rp · Answer

yea im wondering the same thing

rp · Answer

are you using our pre built UI

turbosepp · Answer

No got an already built UI for login register in the frontend and connected this to supertokens

turbosepp · Answer

Hmmm was some time ago so I have to check that code again

rp · Answer

hmm ok

rp · Answer

were you making sign in calls to the backend via fetch axios or via our web js SDK

turbosepp · Answer

I m looking into it right now one moment

turbosepp · Answer

Ok so it looks like the signin and signup POST calls are via the angular httpClient package going to auth singin and auth signup

rp · Answer

right That s why it was all working before

rp · Answer

So you need to change the apiDomain on the frontend and backedn to point to the same domain on which signin signup are being called

turbosepp · Answer

Yes it looks like I got a mess with my env vars and therefore the domains there

turbosepp · Answer

but I can keep the implementation with the angular http calls

rp · Answer

yes

turbosepp · Answer

And it pobably also resolves my troubles getting a https connection without broken links to logos in the browser to auth dashboard right

turbosepp · Answer

as there is the wrong apiDomain put in the express server

rp · Answer

what do you mean The logos on the dashboard are not loading up

rp · Answer

can i see a screenshot and if you don t mind sharing which country are you from

turbosepp · Answer

Got CORS errors in the console

rp · Answer

i see Can i see the console logs

turbosepp · Answer

Die Ressource unter https raw githubusercontent com supertokens supertokens logo master logo ST full logo dark theme svg wurde aufgrund ihres Cross Origin Resource Policy Headers oder dessen Fehlens blockiert Weitere Informationen unter https developer mozilla org docs Web HTTP Cross Origin Resource Policy CORP dashboard

rp · Answer

thanks We will fix that

rp · Answer

It s got nothing to do with the apiDomain misconfig

turbosepp · Answer

Ah ok Good to know

turbosepp · Answer

I would probably have took more time on that

turbosepp · Answer

thanks for your help < rp>

rp · Answer

happy to help