Unauthorized fetch with server side rendering implement fron 603466164219281420 #support-questions

whats the value of apiDomain and websiteDomain that you have set in the appInfo? Also, can i see the set-cookie header response when you call the sign in API (screenshot from chrome will do)

Ressiject

10/16/2022, 1:20 PM

8000 for api, 3000 for website

my solution now is use cookie and send

10/16/2022, 1:21 PM

what do you mean?

Ressiject

10/16/2022, 1:21 PM

i mean i write front-end

by read cookie from user computer

and send to website domain

10/16/2022, 1:23 PM

i don't think i undersatnd

Ressiject

10/16/2022, 1:24 PM

i mean the problem here

not when we send request from front-end to back-end

i mean

it look like comunication between client and server (in front end)

its didn't send cookies from user computer to front-end

10/16/2022, 1:27 PM

so if the cookies are attached to localhost:8000, they should also be sent to webserver on localhost:3000 when you navigate to the site from the browser.

Ressiject

10/16/2022, 1:27 PM

oh i see

then why should i track the cookie

it look like some bug here

10/16/2022, 1:29 PM

what do you mean why should you track cookies.

Ressiject

10/16/2022, 1:29 PM

i mean

i write that part myself

10/16/2022, 1:29 PM

you don't need to. Just use our SDKs 🙂

Ressiject

10/16/2022, 1:29 PM

thanks

it a little bit confuse

because it work before

10/16/2022, 1:30 PM

hmm

maybe see what you changed and try and debug

Ressiject

10/16/2022, 1:31 PM

ok thank you 🙂

it problem in my team XD

they ask me to ask you

10/16/2022, 1:31 PM

hmm ok

haha.. if you can't figure out the issue, maybe try seeing one of our example apps

Ressiject

10/16/2022, 1:33 PM

we looked before

thank you

next.js is a little bit different

10/16/2022, 1:36 PM

we have a nextjs example app as well

try it with

npx create-supertokens-app

command

#support-questions Join Discord