masterdimar
09/28/2021, 10:34 PMrp
09/29/2021, 4:54 AMrp
09/29/2021, 4:56 AMSai Dinesh
09/29/2021, 6:10 AMrp
09/29/2021, 6:11 AMrp
09/29/2021, 6:11 AMSai Dinesh
09/29/2021, 6:11 AMuser
09/29/2021, 7:24 AMrp
09/29/2021, 7:25 AMuser
09/29/2021, 7:25 AMrp
09/29/2021, 7:27 AMhost
value in config.yaml as `"0.0.0.0"`: https://github.com/supertokens/supertokens-core/blob/master/config.yaml#L16user
09/29/2021, 7:28 AMuser
09/29/2021, 7:35 AMrp
09/29/2021, 7:36 AMuser
09/29/2021, 7:38 AMrp
09/29/2021, 8:06 AMuser
09/29/2021, 2:58 PMuser
09/29/2021, 2:58 PMrp
09/29/2021, 2:59 PMrp
09/29/2021, 2:59 PMuser
09/29/2021, 3:01 PMuser
09/29/2021, 3:03 PMrp
09/29/2021, 3:05 PMsupertokens start --host=150.230.130.109
(and comment the host
in the config.yaml file)user
09/29/2021, 3:05 PMrp
09/29/2021, 3:07 PMhost
in config.yaml works, cause in the docker images we provide, we have set it to 0.0.0.0
in the config file, and that works fine.
Might be a stupid quesiton, but are you sure you are editing the right config file?user
09/29/2021, 3:09 PMuser
09/29/2021, 3:11 PMuser
09/29/2021, 3:13 PMuser
09/29/2021, 3:18 PMrp
09/29/2021, 3:24 PM150.230.130.109
is the public IP? If you set the host
to that, it won't be able to bind to it cause the inside the server it's not a recognised host.
Instead, try supertokens start --host=0.0.0.0
and then query on 150.230.130.109
?rp
09/29/2021, 3:24 PM150.230.130.109
is the public IP? If you set the host
to that, it won't be able to bind to it cause the inside the server it's not a recognised host.
Instead, try supertokens start --host=0.0.0.0
and then query on 150.230.130.109
?