Active Sessions: backend returns internal pod IP (10.244.0.0/16) instead of the client's real public IP

On https://jinxxy.com/my/settings, the "Active Sessions" section shows an internal private IP (e.g., 10.244.99.32, 10.244.133.89) for the current session instead of the user's real public IP. As a side effect, the "Location" column falls back to "Unknown" because private IPs cannot be geolocated