I have 2 applications running on Fly.io. Application #1 is the client. Application #2 is the API with an IP address allow list . I have an egress IP assigned to Application #1. If I try to use Application #1 to fetch data from Application #2 (server side), it is not using Application #1’s egress IP. I just moved Application #2 from another hosting provider where it has worked for over 5 years.
This is expected – any Fly-internal access is terminated on the same server hosting the source machine, and hence will not see the real egress IP as you would outside of Fly.
If the intention is to limit access to the other app (app 2), we recommend switching app 1 to only serve a Flycast address – you’ll also save the cost of the egress IP this way.
Thank you.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.