we assigned egress IP to our machines for our proxy server, but over time it always gets lost and when it hit https://api.ipify.org it is not the assigned egress IP. this has happened multiple times.
please can anyone help?
Are you seeing this problem right now? From our side it looks like the NAT rules translating your machine’s private IP to the static egress IPs are OK. If you are still experiencing this issue, could you make those machines send some requests out (or authorize us to do so by entering your machine) for debugging purposes? If the issue self-resolved, do you have an approximate time frame of when this happened last time?
Hi still experiencing this issue. I authorize you to enter the machines. I’m not sure if it was ever self resolved or whether we just had a working machine that just failed late. but this happens as time goes on. we previously had a separate deployment that experienced the same issue.
I just tested inside both of these machines and they do seem to be using the assigned static egress IPs correctly for both IPv4 and IPv6. When/how are you observing these cases where they lost the egress IP? What does api.ipify.org return in that case?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.