internal networking to finish build step
hi there, i am trying to access a document hosted on one backend service by another backend service. during startup, i have backend service a reach out to backend service b and it is able to get the document. i am using the pattern:
http://${{service-b.RAILWAY_PRIVATE_DOMAIN}}:${{service-b.PORT}} and service b is bound to ::8080 so i would think it should be pretty straightforward. anything i am missing here?16 Replies
Project ID:
cef55847-90eb-44a9-9c3b-ac12a882132bcef55847-90eb-44a9-9c3b-ac12a882132b
i should also note that this step writes files to disk to be referenced in the actual business logic. wondering if there could be something there as well?
what issues are you running into?
i am loading a graphql schema, and am getting the following error:
is there something i can run to verify that service-a can access serivce b? i would think that they should be able to. i just don't know how to test it
service-a can access service-b, there is just a config error somewhere on your part
can you get a better error message than "Failed to load schema"
for now, this is all i have:
well thats not super helpfull
is service-b listening on Ipv6?
trying to find the exact lines in the underlying 2 libs, but yes, it should be using ::
are you getting that error during build or runtime?
runtime
are you sure you are listening on port 8080?
yes
then please confirm it is listening on ipv6, since railways private network is ipv6 only
my inputs seem to be as such. how does one go about confirming? what command can i run?
i see tcp6's when i run
netstat my-domain.up.railway.appthis would be something you need to confirm in your code