It seems like that egress statis IP is still http-proxy based outbound IP mapping. It doesn’t work for non-http traffic. Can someone from fly let us know if support for non-http calls is in the works?
I just lost a week on this issue, pulling my hair out. Simply hadn’t faced it before, but it’s clear now.
Could you PLEASE document this platform constraint more clearly, adding catch terms for MongoDB Atlas and other common cases.
Could you please doc the static, and static egress IP functionality better. Add line items on the pricing page too? This thread was my first contact with the topic after 10-20+ search & LLM sessions.