What’s the right way to pass the real client-side IP when using
I’m using the example Next.js tunnel implementation; however, the user IP reflected in Sentry UI is that of the backend server, not of the client.
I have also tried forwarding
req.headers['x-forwarded-for'] || req.socket.remoteAddr as
X-Forwarded-For to the
/envelope endpoint. The resulting
X-Forwarded-For header I’m sending contains the real client IP in the first position. However, that doesn’t seem to change its behaviour at all, Sentry UI still shows the IP of the backend server as the user IP.