a month ago
We enabled Static Outbound IPs on our dispatcharr service, and the UI shows a static IP (162.220.234.15, region us‑east4).
However, the service’s actual outbound IP remains 71.44.216.10 even after multiple redeploys and restarts.
Steps tried
Enabled Static Outbound IPs in service settings
Redeployed the service (multiple times)
Restarted the service
Verified outbound IP from inside the service using:
railway run curl -s https://api.ipify.org
Output is still 71.44.216.10
Expected
Outbound traffic should use the static IP shown in the UI.
Actual
Outbound traffic continues to use a different IP (71.44.216.10).
Project/Service
Project: observant-illumination
Service: dispatcharr
Environment: production
Region shown in UI: us‑east4
Any guidance to force the static IP to apply would be appreciated.
1 Replies
a month ago
The command railway run executes code on your local machine, not on Railway's infrastructure. That's why you're seeing 71.44.216.10 - it's your local outbound IP, not your service's. To verify the static IP is working, run the curl command from within your deployed service itself, either by adding it to your application code temporarily, using the service shell in the Railway dashboard, or hitting an endpoint in your app that returns the result of that ipify call.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • about 1 month ago