internal URLs not working
joeypedicini92
PROOP

a year ago

I'm having trouble making http requests between node services using internal urls. when I use the external urls they communicate just fine.

25 Replies

joeypedicini92
PROOP

a year ago

db725181-006d-41c4-98b5-38a46a6a74b7


joeypedicini92
PROOP

a year ago

the service is never being contacted there are no logs coming from that service


a year ago

Does your app listen on IPv6? Internal/Private networking only works with IPv6 https://docs.railway.com/guides/private-networking


joeypedicini92
PROOP

a year ago

ah that might be it thank you


joeypedicini92
PROOP

a year ago

that seemed to do the trick to connect internally but now I can't connect externally. need to debug more should the URL change at all now for external connections?


a year ago

I am afraid that I can't help you any further than this.

It may be related to the paragraph below, which has been cited from the docs above.

Note: If your application needs to be accessible over both private and public networks, your application server must support dual stack binding. Most servers handle this automatically when listening on ::, but some, like Uvicorn, do not.


joeypedicini92
PROOP

a year ago

yeah I did do that. hmm I'll take a look and respond here when i figure it out for anyone in the future who comes across this


joeypedicini92
PROOP

a year ago

as far as i'm aware node+express supports dual stack binding


a year ago

yes it does, please link to the service in question


joeypedicini92
PROOP

a year ago

project id: db725181-006d-41c4-98b5-38a46a6a74b7 service authentication


joeypedicini92
PROOP

a year ago

currently can connect internally from the API service, but externally getting 502s


a year ago

node is running on port 5000 not 8080


a year ago

check your target port for the domain


joeypedicini92
PROOP

a year ago

🤦‍♂️


joeypedicini92
PROOP

a year ago

thank you very much


a year ago

no problem!


joeypedicini92
PROOP

a year ago

lol sometimes the problem is staring right in front of you


a year ago

sometimes haha


joeypedicini92
PROOP

a year ago

but im curious how it was working before i made the code change to support the dual binding


joeypedicini92
PROOP

a year ago

same port


a year ago

before you where listening on port 8080


a year ago

idealy you still should be, but thats besides the point


joeypedicini92
PROOP

a year ago

hmm ok. well either way appreciate the help @Brody @uxuz


a year ago

happy to help, and thank you uxuz for the initial solution!


a year ago

!s


Status changed to Solved brody over 1 year ago


Loading...