2 months ago
Hi,
We are having terrible trouble with static IPs on one of our projects. Basically they just aren't working.
project=03b4dcf5-df4b-46c9-a27b-24545a802178
environmentId=6a8e3ef8-da5b-46b8-8d33-feb5cf6a2b80
All services are deployed from Docker images, when doing a check on the IP address being used the response is always a random IP despite the fact we have Static IP addresses turned on for a number of the services.
Our latest test shows Detected public IP address: 208.77.244.43 when we have static IP's turned on and we should be using 208.77.244.15
This has crippled a very important application. I've selected one service as an example, however we are having the same problem across all services with static IP's turned on.
Any help asap would be gratefully appreciated.
9 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
2 months ago
Hi there, is this a recent occurrence? Were static IPs previously working for this same project + environment and now aren't?
Just to confirm, I'm seeing the static IP service enabled enabled only on these two service groups (total 2 services, 1 in each group): "Proxies" and "Deprecated"
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
2 months ago
If you have recently enabled static IPs, you will have to redeploy your service for it to take effect.
2 months ago
Hi,
The project itself is new.
The service in the 'Deprecated' group has been used before with a static IP but in a different project.
The other services have only just been brought across to Railway.
I have redeployed many times since turning on Static IP's on the services. I have also turned Static IPs off, redeployed, turned them back on, redeployed to no avail.
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Hello!
We've escalated your issue to our engineering team.
We aim to provide an update within 1 business day.
Please reply to this thread if you have any questions!
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Hi there, sorry to hear it failed despite you trying a couple of different things here.
We've located the issue to likely be related to the IPv4 network. Could you please try turn off the flag for the IPv4_PRIVATE_NETWORKS and see if that fixes the issue?
2 months ago
By disabling this feature, you may need to ensure your services support communication over IPv6 before redeploying
Seeing redis among your services, so if you are using ioredis you'd have to enable the dual stack look up to support IPv6. To do this, in your REDIS_URL environment variable, you can set the family to 0
Our docs on this are available here: https://docs.railway.com/reference/errors/enotfound-redis-railway-internal#ioredis
2 months ago
✅ The ticket Static IP inconsistency issue has been marked as completed.
2 months ago
Hello,
Regarding the original issue, it has been fixed, and you should only need to redeploy to get the correct outbound IP assigned!
Best,
Brody
Status changed to Solved brody • about 2 months ago