https://supertokens.com/ logo
Join Discord
Powered by
I get the following error when i try to sign up wi...
# support-questions-legacy
j
I get the following error when i try to sign up with a user: Error: No SuperTokens core available to queryError: No SuperTokens core available to query Setup: I am self hosting a core, without docker on my mac. (It should be running, i can get the hello message when visiting /hello) The connection to my postgresql is successful (the default supertokens tables have been generated)
r
hey!
Can you visit http://localhost:3567/hello on your browser? What do you see?
j
Yes sure can
r
ok so the core is running properly.
Are you running the node server in docker?
j
no
no docker at all
r
hmm
this is strange. Can you change 
http://localhost:3567
to 
https://try.supertokens.com
in the connectionURI in the node server and see if you get this error?
j
I am pretty sure that this will work
r
i see
j
Yup that worked
(I tried it previously as well)
r
the node server is not being able to reach localhost:3567.. usually that happens if you are running node in a docker image. But since you are not it's strange
j
Might be some security settings on my mac?
r
is there any firewall setting on your mac that might be preventing this?
usually there isn't anything as such.. but maybe you had configured something in the past
j
After disabling all firewalls, the issue still persists.
I could try to get the core hosted, then at least we will know that it is not my mac
I do have some extra security settings on this mac, that I will not be able to disable. So it could be those
r
probably.
You could try using docker and create a virtual network there, or host the core someone else that is non localhost, or use your managed service.
Im pretty sure it's security config on the mac that's causing this problem.
j
I'm going to give it a shot, and return to you afterwards
r
sounds good
j
running the core in docker solved the issue. Also running it locally
r
Cool!
Im curious what setting you have on your mac that prevented localhost to be reachable via node
Maybe some permission restriction is there for the node command itself?
j
Could be, I have not checked it out.
I am hosting the core in docker on a digitial ocean droplet. I don't have an ssl encryption on the server. So I currently access it through http://myIp:port I was wondering if there are any security risks associated with this, and if I need to comminutcate over https to the droplet. Do you know this?
r
You should use https. The way we support that now is by adding an nginx in front of the core. There is a section about this in our docs
Also, since you are exposing the core to the internet, add an api key to it.
j
thanks I will check that out!
I have created a selfsigned cert however my https route does not work... it works on http
r
Yea. Self signed won’t work with the browser. Browsers trust a specific set of certs.
j
aaah, okay only tried the browser
r
Digital ocean should have a guide on setting up ssl
j
but it might be working between my backend and the core
r
I think so
j
I think they do, but I guess I will need a domain name to set up ssl for the browser
r
Yea
j
I don't think that would make sense to have a domain name for the core
r
It’s not required. Yea..
j
I get the following error on my backend when it tries to contact the core
r
Hmm. I’m not sure. Might wanna google this
3 Views
PreviousNext
Powered by