Some times this error starts popping up and then I...
# support-questions-legacyy
youscript
09/28/2023, 11:59 AMSome times this error starts popping up and then I need to restart the server again to resolve this error. Is it just because of the restrictions on the dev env from the SuperTokens or something else ?
r
rp_st
09/28/2023, 12:13 PMhey @youscript this happens if you have access tokens issued using the rotating access token keys and have set the
useDynamicAccessTokensSigningKeys: falsey
youscript
09/28/2023, 12:22 PMSo how do I fix it and stop it from coming tho ?
youscript
09/28/2023, 12:22 PMI have set the useDynamicAccessTokensSigningKeys to false
r
rp_st
09/28/2023, 12:22 PMrelogin to your application when testing
rp_st
09/28/2023, 12:23 PMand if you had created any JWTs before that are saved somewhere, discard them and recreate them.
y
youscript
09/28/2023, 12:25 PMI have relogin to my application dozens of time. I did not create any JWTs manually tho. I am use self managed service for now
r
rp_st
09/28/2023, 12:27 PMhmmm.
rp_st
09/28/2023, 12:27 PMThen this should not have happaned
rp_st
09/28/2023, 12:27 PMhappened*
rp_st
09/28/2023, 12:27 PMwhich backend sdk are you using?
y
youscript
09/28/2023, 12:28 PMsupertokens-node
youscript
09/28/2023, 12:29 PMgithub:supertokens/supertokens-node#backwards/edge_compatibility_check This branch that porcellus shared with me to test the fixed cross_fetch error
youscript
09/28/2023, 12:30 PMJust to clear this to you thir error also used to come when I was not using this branch tho
r
rp_st
09/28/2023, 12:30 PMright. It might be a bug then. Does this happen after 1 hour of logging in? When the access token expires and is recreated?
rp_st
09/28/2023, 12:32 PM@porcellus can help here.
y
youscript
09/28/2023, 12:32 PMDid not nitice the time tho but this does happen after some time of doing work in the app. Not right in the start
p
porcellus
09/28/2023, 12:35 PMhi. One interesting thing here is that there are two very different error messages in your screenshots. Are you sure the two are related? Also, the error message in your frontend also refers to an exception thrown by our backend SDK. Are you referencing supertokens-node in your frontend/client code?
y
youscript
09/28/2023, 1:10 PMAh really sorry guys. The frontend screensot of the error was wrong. Really sorry for that
youscript
09/28/2023, 1:11 PMThis is the actual frontend error
youscript
09/28/2023, 1:11 PMand backend log was correct
r
rp_st
09/28/2023, 1:18 PMright. This just means that the access token has expired
rp_st
09/28/2023, 1:18 PMand that you need to refresh it
y
youscript
09/28/2023, 1:30 PMOh so I have to manually handle this token refresh flow in my application ?
r
rp_st
09/28/2023, 1:31 PMIs this during server side rendering?
y
youscript
09/28/2023, 1:37 PMsession = await Session.getSessionWithoutRequestResponse(accessToken) So does using this func verifies the access token ? Because this is the function that I call on server side and may be this could be the reason
r
rp_st
09/28/2023, 1:39 PMYup. It does. And it throws the error if the token has expired
rp_st
09/28/2023, 1:39 PMFor api calls, our frontend SDK handles the refresh automatically. But for SSR, you need to handle it. See our docs for SSR please
y
youscript
09/28/2023, 1:41 PMOkh. Thanks!