https://supertokens.com/ logo
y

yyogeshwar

04/07/2022, 4:16 AM
When running code from docker i am getting this error , do we need to expose some ports , otherwise working fine for normal local version
r

rp

04/07/2022, 4:18 AM
Hey!
Can you explain the setup please? What are you running in docker?
y

yyogeshwar

04/07/2022, 4:20 AM
i am running it with NODE with fastify on local PC / AWS , both places getting the same issue
r

rp

04/07/2022, 4:21 AM
Can you visit the that f487…supertokens.io url on your browser at the /hello path?
What do you see if you do that?
Make sure to add the right port to that url. The port for that url isn’t 80 or 443. You should visit Our dashboard and see the port
y

yyogeshwar

04/07/2022, 4:25 AM
from browser its fine
r

rp

04/07/2022, 4:26 AM
Right. Have you disabled outgoing ports for the docker env? There is nothing that needs to be done specially for this to work.
y

yyogeshwar

04/07/2022, 4:28 AM
naa nothing is disabled
here its not picking the port
r

rp

04/07/2022, 4:30 AM
What’s the connectionURI provided to the supertokens.init?
y

yyogeshwar

04/07/2022, 4:31 AM
Copy code
https://f487f461b44011ec98ed89cb2be9b480-ap-southeast-1.aws.supertokens.io:3572
r

rp

04/07/2022, 4:34 AM
Hmmm. Does the node app work if it’s not run in docker?
y

yyogeshwar

04/07/2022, 4:37 AM
yess
without any issues
docker is also receiveing the proper URI
r

rp

04/07/2022, 4:38 AM
Hmmmm. CAn I see your docker file and the docker run command?
y

yyogeshwar

04/07/2022, 4:39 AM
fastify.listen(fastify.config.PORT, fastify.config.HOST) HOST here is - 0.0.0.0
can this be issue some issue ?
its a standard docker file and RUN command
r

rp

04/07/2022, 4:53 AM
Probably not.
Can you give an invalid connectionURI in the env var and see if the error is the same? Some URI that you know doesn't exist
y

yyogeshwar

04/07/2022, 5:07 AM
this is without docker , running node app directly
Copy code
connectionURI: 'https://f480-ap-southeast-1.aws.supertokens.io:3572'
r

rp

04/07/2022, 5:08 AM
I see. So even if the port is being picked up (which it is), the error doesn't mention it
So then the issue is probably with docker somehow not allowing you to query this port
y

yyogeshwar

04/07/2022, 5:09 AM
same error running with docker
r

rp

04/07/2022, 5:10 AM
if you can share your dockerfile, how you are running it, the docker version and the OS you are using, that would be helpful
this is more of a docker setup issue than a supertokens' issue
y

yyogeshwar

04/07/2022, 5:10 AM
ok , i will create a repo and will share you in an hour or so
r

rp

04/07/2022, 5:10 AM
sounds good
y

yyogeshwar

04/07/2022, 5:19 AM
meanwhile can u ask any of your exisitng customer in case they are using docker and got this issues ?
r

rp

04/07/2022, 5:19 AM
most of them use docker. However, none of them have complained about this.
2 Views