a month ago
Having issues impacting specific services internal networking, no recent code changes would have impacted. Moving to public networking resolved this issue temporarily. Any ideas?
5 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
you need to update your service's host/bind address to listen on all IPv6 interfaces rather than just IPv4. Change your bind address from 0.0.0.0 to :: (or [::], depending on your specific framework).
You can also check official docs: https://docs.railway.com/private-networking
a month ago
No this appears to be an internal Railway issue, seeing numerous people experiencing the same thing
samkotlove
No this appears to be an internal Railway issue, seeing numerous people experiencing the same thing
a month ago
internal networking drops usually happen when a framework, language runtime (like a Node.js version bump), or a Docker base image updates its default networking behavior to prefer IPv4 over dual-stack binding.
h701h
you need to update your service's host/bind address to listen on all IPv6 interfaces rather than just IPv4. Change your bind address from 0.0.0.0 to :: (or [::], depending on your specific framework). You can also check official docs: https://docs.railway.com/private-networking
a month ago
this is an internal railway issue
nothing has changed on our end
samkotlove
No this appears to be an internal Railway issue, seeing numerous people experiencing the same thing
a month ago
yes! thank you