I'm unable to connect to another process on the internal network

oh i'm a moron, wasn't following these docs

https://docs.railway.app/guides/private-networking

i've used private network in other PAAS and you don't have to broadcast over ipv6, maybe should have a big red disclaimer or something because I didn't realize railway behaves differently

hmm still running into issues actually

my llm router is listening on ipv6 port 6969

Error calling MAIN LLM API (attempt 5/5) error calling LLM router: Post "http://llm-router.railway.internal:6969/chat";: dial tcp [fd12:534b:a115:0:8000:18:5fb0:aefb]:6969: connect: connection refused

never mind i am still a moron and even if you listen on ipv6 in go fiber you have to change some obscure network setting because it defaults to ipv4 only instead of both ipv4 and ipv6????

hoping this fixes it 😭

🙏

this server is the best rubber duck ever <:rubber_duck:1055213027038859395>

i'm sorry to waste all of your tme

this is probably a good idea though

IT WORKED

I AM FOREVER GRATEFUL TO DOCUMENTATION

🙏

I don't know if a big red disclaimer is necessary, but the docs say you must listen on IPv6.

we also have docs for that! -

also, the private network does not take 3 seconds anymore, that is old information and will be removed very soon, similarly, you no longer need any work around for alpine

fair enough

maybe just Private Network (IPV6) would be enough to signal it

but yea it's just idiot proofing, not explicitly needed but will avoid people like me going down the rabbithole

don't we already say that?

> Since the private network is an IPv6 network...

this was where in the UI i found out about private networking support in railway

and I was like oh sick i'll use that then