Posted on 07-03-2023 01:13 AM
Hello Jamf people, we have recently migrated our on-premises 10.46.1 Jamf Pro to another server (Ubuntu 18 to Ubuntu 22), and everything seems to be working OK, however all clients reporting localhost IP address now - 127.0.0.1, while previously it was their actual IP address.
It might be related to Apache proxy we've got running on that server as well - it was migrated to the new one with exactly the same configuration though.
Is it possible it's something JAMF related or we should keep looking more into Apache config? Did someone else face this kind of issue before?
Thank you!
07-03-2023 01:38 AM - edited 07-03-2023 01:39 AM
maybe related .. but when using F5 load balancer, there are setting required to parse the client IP. See
https://community.f5.com/t5/technical-forum/get-clientip-address-behind-loadbalancer/td-p/50647
You must enable the X-Forwarded-For header in the HTTP profile (Insert X-Forwarded-For)