Unauthorized fetch with server side rendering, (im...
# support-questions-legacyr
ressiject
10/14/2022, 4:41 PMUnauthorized fetch with server side rendering, (implement front end server side rendering), Next.js and Axios
r
rp_st
10/15/2022, 4:08 AMHey @ressiject
rp_st
10/15/2022, 4:09 AMIs your api domain and website domain different? What are the values?
r
ressiject
10/16/2022, 2:00 AMyes
ressiject
10/16/2022, 2:01 AMclient will access at localhost:3000
ressiject
10/16/2022, 2:01 AM0
ressiject
10/16/2022, 2:02 AMwhile we are trying to implement front-end with server side rendering
ressiject
10/16/2022, 2:02 AMshould i try to handle with user cache ?
ressiject
10/16/2022, 2:03 AMi mean we are treat api as gate way where front-end only ask for resource
r
rp_st
10/16/2022, 5:06 AMI see. So the cookies are not being sent to localhost:3000? (During server side rendering)
r
ressiject
10/16/2022, 1:17 PMyes
r
rp_st
10/16/2022, 1:18 PMDo the cookies get sent to the api gateway?
r
ressiject
10/16/2022, 1:18 PMnope
r
rp_st
10/16/2022, 1:19 PMwhats 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)
r
ressiject
10/16/2022, 1:20 PM8000 for api, 3000 for website
ressiject
10/16/2022, 1:21 PMmy solution now is use cookie and send
ressiject
10/16/2022, 1:21 PMXD
r
rp_st
10/16/2022, 1:21 PMwhat do you mean?
r
ressiject
10/16/2022, 1:21 PMi mean i write front-end
ressiject
10/16/2022, 1:22 PMby read cookie from user computer
ressiject
10/16/2022, 1:22 PMand send to website domain
r
rp_st
10/16/2022, 1:23 PMi don't think i undersatnd
r
ressiject
10/16/2022, 1:24 PMi mean the problem here
ressiject
10/16/2022, 1:25 PMnot when we send request from front-end to back-end
ressiject
10/16/2022, 1:25 PMi mean
ressiject
10/16/2022, 1:26 PMit look like comunication between client and server (in front end)
ressiject
10/16/2022, 1:27 PMits didn't send cookies from user computer to front-end
r
rp_st
10/16/2022, 1:27 PMso 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.
r
ressiject
10/16/2022, 1:27 PMoh i see
ressiject
10/16/2022, 1:28 PMthen why should i track the cookie
ressiject
10/16/2022, 1:28 PMit look like some bug here
r
rp_st
10/16/2022, 1:29 PMwhat do you mean why should you track cookies.
r
ressiject
10/16/2022, 1:29 PMi mean
ressiject
10/16/2022, 1:29 PMi write that part myself
r
rp_st
10/16/2022, 1:29 PMyou don't need to. Just use our SDKs 🙂
r
ressiject
10/16/2022, 1:29 PMthanks
ressiject
10/16/2022, 1:29 PMit a little bit confuse
ressiject
10/16/2022, 1:30 PMbecause it work before
r
rp_st
10/16/2022, 1:30 PMhmm
rp_st
10/16/2022, 1:30 PMmaybe see what you changed and try and debug
r
ressiject
10/16/2022, 1:31 PMok thank you 🙂
ressiject
10/16/2022, 1:31 PMit problem in my team XD
ressiject
10/16/2022, 1:31 PMthey ask me to ask you
r
rp_st
10/16/2022, 1:31 PMhmm ok
rp_st
10/16/2022, 1:32 PMhaha.. if you can't figure out the issue, maybe try seeing one of our example apps
r
ressiject
10/16/2022, 1:33 PMwe looked before
ressiject
10/16/2022, 1:33 PMthank you
ressiject
10/16/2022, 1:34 PMnext.js is a little bit different
r
rp_st
10/16/2022, 1:36 PMwe have a nextjs example app as well
rp_st
10/16/2022, 1:36 PMtry it with
npx create-supertokens-app