I have a question: I'm experiencing an odd bug rel...
# support-questions-legacy
m
I have a question: I'm experiencing an odd bug related to Supertokens library I'm using supertokens with javascript. I'm testing it using supertokens self hosted. Everything works like a charm locally, so i deploy supertokens with mysql and docker locally, as i said. The problem arises when i deploy supertokens (core) in a remote server and i test implementing a nodejs backend locally using supertokens-core remotelly
r
Hey @mcabgil when you visit the core’s url on the browser, what do you get back?
m
Hey rp
Gimme a sec
"/auth/dashboard"
r
No I mean when you visit the core url
The connection url
On the browser
m
It works
I get the hello message
r
Hmm. This means the core is working fine
m
Yep
That's the weird thing
r
What’s the error log from the core when you make a request from the backend SDK?
That’s the log from the backend SDK
I’m asking about the core error logs
m
I don't have any errors from the core
Let me double check just in case
None
r
What about debug / info logs?
Can you call the /apiversion api via postman?
m
Let me try
Thank you rp
The problem was the load balancer. I had a rule that routed only traffic to "/auth/*" and "/hello"
r
Ah right
m
So it did not cover "/apiversion" route
thank you so much for the supper. May God bless you
r
The core APIs are here supertokens.com/docs/cdi
m
Thank you rp. I'll check it out. Have a nice rest of day
r
To you as well 🙂