https://supertokens.com/ logo
Join Discord
Powered by
hello guys. I just used Supertokens Social login ...
# support-questions
m
hello guys. I just used Supertokens Social login + Email Password and it worked fine, and this time I used the Paswordless recipe, and found a problem. I have followed the steps in the guide, and using Self Hosted Without Docker PostgreSQL, the problem is when I enter the phone number into the form, and the response from the API is 500 INTERNAL SERVER ERROR. And once again I rechecked the steps in the guide, to make sure there were no steps left behind. After that, I run my application again, and get the same error. please help me. 🙂
r
How have you configured the core's connectionURI? Also, are you running your backend API in docker?
m
this is my config, im not using docker, just install supertokens in my laptop
r
are you running the core on port 4000?
m
yes
r
or the default one (3567)
hmm
can you go to your browser and navigate to http://localhost:4000/hello
what does that return?
m
this is the return
r
hmm. so the core is running
For some reason, your node process is not being able to contact the core
can you try removing the apiKey and see what happens?
m
okey, i'll try it
still same problem
r
strange
earlier, when you said the email passwords auth was working, what was your setup then?
m
its same u know 🙂
r
hmm
m
just change the import for Passwordless
and some adjust
but still same config
r
can you enable debug logs on the backend and show the output when you call the API?
m
wait
like this ?
r
m
this is the response
r
hmm. Which version of the core are you using?
m
this is my version
r
right. This is the latest version.
Im honestly not sure why this is happening
Can we get on an quick debugging call?\
m
What does that mean?
r
I mean try and debug this on a call
easier to see whats happening
m
okey
but my english is not fluent enough
r
ah right.
m
im using node 18.6
r
can you replace the connectionURI with 
https://try.supertokens.com
and see what happens?
m
ah, its success
with this
r
hmm
so definitely something wrong with how you the node process is trying to reach localhost
m
Actually, I installed the backend when my node was still version 16.
Is there any effect?
r
hmm. Maybe
try remocing package-lock, node_moduless
and then reinstalling
m
okey
still the same
i think i wanna try previous recipe
r
Can you try running it with node 16 and see what happens?
> i think i wanna try previous recipe This should not make a difference
m
okey, i want try this
good news
working normal in 16
r
oh nice! ok. So seems like some issue with node 18 and how we are querying the core
can you open an issue about this on our github? We can have a look
m
hemm i'll try it
btw, thank u very much rp
👍
r
happy to help 🙂
m
r
thank you
m
your welcome, thanks for the help 😁
PreviousNext
Powered by