Today I had a scenario where a fly machine with egress static ip and two anycast ips on the app got stuck without internet access. The machine is a proxy for radius servers that run in fly. It connects to an external wireguard network for nas devices like routers.
After lots of debugging, I found out the vm didnt have internet access. After releasing the static egress ip and the anycast ips, it got back to normal. I dont understand what caused this at all.
Any ideas?
Could you share the name of your app and, if possible, the static egress IP that was assigned to your machine?
(By the way, it sounds like your use case may not necessarily require a static egress IP? They are mostly intended for applications where the other end limits access by source IP, but if you’re already using something like Wireguard, you probably don’t need it.)
I am facing the same problem, bunch of troubeshooting, end result is my app my app not able to make outbound http request, I am afraid to release/new IP because if it changes I will need to get it whilelisted which can take a while. need help
Can you share your app name? That’ll help us look into what’s going on.
up-proxy
Can you check if it works now? Sorry for the fuss, we’re going to improve the experience of egress IPs pretty soon and should hopefully get rid of this kind of weirdness as well.
First, the app needs a static ip to be whitelisted to connect to the external wireguard at machine level. Since is a radius proxy, we just run one tiny machine which handles proxying so yes it does need a static ip. The static ip is whitelisted on 2 external VPN servers where it brokers RADIUS UDP services.
Whats the way to share the app details with you? Am new to community.
app can ping outside now. testing functionality, will let you know
Usually it should be OK to share the app name on community except if the app serves sensitive data but is also exposed on public IPs. In that case, we sometimes do accept emails.
Though, in this case I think I have already figured out why this is happening, and I’ll look at fixing this quickly. There are also bigger improvements to egress IPs coming soon – stay tuned!
Sounds perfect. My guess was the machine was stuck somewhere because of the ip assignment. All good now so yup, no need to share anymore. Hopping app assignment comes with the egress ip changes. It will bring quite new possibilities 
.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.