Hey <@!521966699423989770> did you fix the issue?
# community
r
Hey @User did you fix the issue?
y
not able to fix it
r
Alright! Can you install the node SDK in your code from branch 9.1 of the GitHub repo?
Supertokens-node repo, branch 9.1
actually, we just released a new version of the node SDK which has debug logging feature. So can you install the version
9.1.2
and then run your app like:
Copy code
DEBUG=com.supertokens node index.js
And then show me the output of the console on startup. Then query the JWKs endpoint via your browser and show me the output on the console after that.
@User please do try the above as well. It will help us debug why the jwks endpoint is not working
y
yipp sure
just let me finish the flow
r
It's actually a little late here (11 pm), so if you could do this and sort out the JWKs endpoint thing first, I would appreciate it.
y
lets do it tomorrow then , i am also from India 😃
r
haha fair enough
y
thanks for your quick responses
r
feel free to message though. In case im available, i'll reply
y
i have a feeling that this issue is due to some fastify mismatch config
will let you know
r
yea it probably is. We can find out via the output logs
y
does is work for express properly ?
r
yes
we also have a lot of poeple using it for fastify. So it works there too
probably some config error somewhere.
y
yipp
output on console on startup
r
Thanks. And the output when you call the jwks endpoint via the browser?
y
working for this version
r
Huh.. so strange. There is no change in this version related to routing or this part of the code.
y
let me check on older version
it seems to be working now
weird though
r
Yea. Weird.
2 Views