Fly using compromised IP address

1

Earlier today, our outbound IP address was set to 89.222.99.36 which twilio for some reason thought was a malicious IP and shut off our phone systems. This could have cost us 100s of thousand of $ if we didn’t see the message in time and take action right away

We created a dedicated ip 169.155.56.198, but if I curl -4 ifconfig.me from my fly app, I see 66.225.208.83, when in the fly console, my ip is set as a dedicated ip to 169.155.56.198.

We are trying to have a control over the IP address so it doesn’t get reported for malicious activity, because that can basically kill our company if it happens and we don’t act right away.

I’m wondering why fly changes the IP address and if there is anyway to force it to use the dedicated IPv4 address we are paying for?

3

please see our docs on outbound IPs: Egress IP addresses · Fly Docs

by default, egress IPs are sourced from our upstream providers (so, can have been used by anyone else in the past) and shared with other Fly.io customers. they can and will change as machines are moved across hosts (for maintenance, rebalancing, etc…)

if you need an outbound IP address dedicated to you, use the static egress IP functionality, ideally through a proxy app (example)

2 Likes
5

Thanks, @lillian that makes it a lot easier

6

Also, for anyone using node, I’ve found GitHub - gajus/global-agent: Global HTTP/HTTPS proxy agent configurable using environment variables. seems to be a good option for connecting to the proxy automatically on nodejs

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.