You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that my geolocation was not being set. I tried trusting the IP ranges for my load balancers as well, but that did not work. I think an additional IP for my cloud run instance gets added as advised by this article, and that was hard to find documentation for a specific range.
Ended up just taking the first IP address (which in most cases should be the client's original IP) from the X-Forwarded-For header.
I noticed that my geolocation was not being set. I tried trusting the IP ranges for my load balancers as well, but that did not work. I think an additional IP for my cloud run instance gets added as advised by this article, and that was hard to find documentation for a specific range.
Ended up just taking the first IP address (which in most cases should be the client's original IP) from the X-Forwarded-For header.
And send that as the Real-IP
proxy_set_header X-Real-IP $first_x_forwarded_for;
The text was updated successfully, but these errors were encountered: