a month ago
Summary
On a project created in 2026 (post the Oct 2025 dual-stack rollout described here), both my manually-created dev and prod environments correctly show both IPv4 and IPv6 tags in the services Private Networking panel, but PR preview environments only show IPv6.
Expected Behaviour
Per the docs, environments on this project should resolve internal hostnames to both IPv4 and IPv6, regardless of whether they are manual environments or PR-spawned preview environments.
5 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Sorry for the delay on this. You're correct that PR preview environments should have dual-stack private networking. We've identified and pushed a fix for this. Could you try creating a new PR environment and let us know if it now shows both IPv4 and IPv6?
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Hi, just raised a new PR and it's still showing up as IPv6 only... Anything else I should try?
Status changed to Awaiting Railway Response Railway • 26 days ago
19 days ago
Hey, sorry for the continued wait on this. We've identified the root cause — when PR preview environments are created, the private network is initialized without the dual-stack (IPv4) tag that regular environments get. We have a fix in review now and will update you once it's shipped.
Status changed to Awaiting User Response Railway • 19 days ago
19 days ago
Perfect, thanks! I'll keep an eye out
Status changed to Awaiting Railway Response Railway • 19 days ago
19 days ago
This fix has shipped. Your next PR environment should get both IPv4 and IPv6 on the private network. Let us know if you still see issues.
Status changed to Awaiting User Response Railway • 19 days ago
11 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 11 days ago