Railway•9mo ago

Axios (node server) private network

If my private network name is "exotic-auth", how can I do a Axios request to it via private network. The http client is setup like this:

const authApi = axios.create({
  baseURL: process.env.API_URL,
  timeout: 15_000,
  headers: standardHeaders
});

const authApi = axios.create({
  baseURL: process.env.API_URL,
  timeout: 15_000,
  headers: standardHeaders
});

for API_URL I've tried http://exotic-auth/v1 and exotic-auth/v1 but nether resolve.

Solution:

fiber runs on tcp4 by default, and the private network is ipv6 only, so tcp tells fiber to bind to both tcp4 and tcp6 (ipv4, ipv6)

Jump to solution

36 Replies

Percy•9mo ago

Project ID: dd3f96f7-3ab3-4453-86a3-32328b2f81d6

macwilko•9mo ago

dd3f96f7-3ab3-4453-86a3-32328b2f81d6

Brody•9mo ago

what port does it listen on?

macwilko•9mo ago

i guess whichever $PORT is set by railway right? but it's a web server via REST its accessible on its public URL over https://

Brody•9mo ago

you can think of the private network like a lan, if you wanted to access an http service on another device on the lan, you would need to use a port in your url in that scenario, this is the same for railway private network, you need to use a port when connecting to other services in the private network

macwilko•9mo ago

i see i see so I should specify the port in the uri

Brody•9mo ago

indeed

macwilko•9mo ago

ok big brain question here, can I use port 80 ? 😄 im guessing not, it's probably assigned a random port right

Brody•9mo ago

I can't recommend you listen on a privileged port if it is indeed listening on railways random PORT, simply set a fixed PORT service variable and use that same port when making requests to the service across the private network

macwilko•9mo ago

booom! right that'll solve it lemme do that ok weirdly baseURL: 'exotic-auth:3000/v1', AxiosError: Unsupported protocol exotic-auth: i'm guessing i need to use http://exotic-auth:3000/v 1

Brody•9mo ago

yes use http, and use the full domain name instead for good measure

macwilko•9mo ago

right oof if this works gonna be so good i imagine even faster

Brody•9mo ago

and zero networking costs as long as communication is done exclusively over the private network

macwilko•9mo ago

yeah mostly doing this because damn Cloudflare is acting up though reliability + speed

Brody•9mo ago

lmao you'll have that when an entire core data center drops offline

macwilko•9mo ago

getting AxiosError: connect ECONNREFUSED fd12:34a7:645b::a3:de4:3b2a:3000 on

baseURL: 'http://exotic-auth:3000/v1';,
method: 'post',
url: '/auth/sign_in',

baseURL: 'http://exotic-auth:3000/v1';,
method: 'post',
url: '/auth/sign_in',

Going to try the full internal name exotic-auth.railway.internal

Brody•9mo ago

are you sure your exotic thingy is running on port 3000?

macwilko•9mo ago

http://exotic-auth.railway.internal:3000/v1 yes one sec

time=2023-11-04T16:27:31.083Z level=INFO msg="🚀 Starting auth api ✅"

time=2023-11-04T16:27:36.097Z level=INFO msg=Connected

┌───────────────────────────────────────────────────┐

│                   Fiber v2.50.0                   │

│               http://127.0.0.1:3000               │

│       (bound on host 0.0.0.0 and port 3000)       │

│                                                   │

│ Handlers ............ 33  Processes ........... 1 │

│ Prefork ....... Disabled  PID ................. 1 │

└───────────────────────────────────────────────────┘

time=2023-11-04T16:27:31.083Z level=INFO msg="🚀 Starting auth api ✅"

time=2023-11-04T16:27:36.097Z level=INFO msg=Connected

┌───────────────────────────────────────────────────┐

│                   Fiber v2.50.0                   │

│               http://127.0.0.1:3000               │

│       (bound on host 0.0.0.0 and port 3000)       │

│                                                   │

│ Handlers ............ 33  Processes ........... 1 │

│ Prefork ....... Disabled  PID ................. 1 │

└───────────────────────────────────────────────────┘

Brody•9mo ago

ah I see the problem, let me consult the fiber docs

macwilko•9mo ago

Brody•9mo ago

in fiber.Config set Network to tcp

macwilko•9mo ago

right

Solution

Brody•9mo ago

fiber runs on tcp4 by default, and the private network is ipv6 only, so tcp tells fiber to bind to both tcp4 and tcp6 (ipv4, ipv6)

macwilko•9mo ago

O.O i have no idea how you work that out brody salute

^.^

Brody•9mo ago

I read the fiber docs so I know about this specific thing, I just had to check back for the correct config name

macwilko•9mo ago

yeah 🙂 works. damn pretty cool

Brody•9mo ago

pog

macwilko•9mo ago

fr this must also add some speed... i think pretty much everything is communicating by private network now

Brody•9mo ago

doesn't need to loopback around on the edge, yeah

macwilko•9mo ago

side question but do you think railway webhooks can also resolve on the private network lol i'm gonna test it but this would be nice, since then I can verify the webhook came from railway also

Brody•9mo ago

nope it can't

macwilko•9mo ago

ahh fair.

Brody•9mo ago

you could verify by cidr range maybe

macwilko•9mo ago

i might add that as feedback, usually webhooks contain a HMAC or some means to verify the sender but since it's railway, i figured a private network thingy might do it also or some special header

Brody•9mo ago

see what headers they do set, maybe there will be something useful

macwilko•9mo ago

true!

Gaming

Programming

Axios (node server) private network