Static egress IP

[hbagdi]

Is there any way to have stable egress IP addresses on a per app basis or a per account basis? The use case is to provide our customers with a set of known IP address - unfortunately still needed in 2022.

[hbagdi]

I came across this unanswered one but nothing else that answers the question otherwise: How can I make docker container use static ip address?.

[greg]

Hi,

There is not.

There are a variety of threads about it e.g

Set/get outgoing IP address for whitelisting on external APIs/Hosts

Hi there, I don’t think this is something that Fly currently does, but is there any way to set an IP address (or a list/range) that a fly app will use to make requests to external hosts? I’d really like to be able to reliably whitelist Fly apps by IP/list/range/whatever. I run reverse proxies, and occasionally one or more Fly IPs will get blacklisted by an external host. Since some requests go out through different Fly IP addresses to the external host, we get an intermittent “sometimes it mak…

One approach would be this suggestion, from Kurt:

Outbound IP Address

We still don’t have the plumbing to give people stable outbound IPs. For now, the simplest thing is either quotaguard.com or VMs from someone like DigitalOcean running a proxy (Smokescreen would be pretty easy: GitHub - fly-apps/smokescreen: An example of deploying Smokescreen on Fly.io)

[ignoramous]

@greg

There is not.

I haven’t tried this, but another user wonders if can clients/servers bind their socket to FLY_PUBLIC_IP, which might then give both a stable ingress (in case of clients via experimental.allowed_public_ports) and egress (if the server process binding to that IP works).

[hbagdi]

Unfortunately, using another proxy doesn’t work because I’m providing a proxy service myself.

Is this something on the roadmap at all?