# Reverse proxy X-Forwarded-For

**URL:** https://meta.discourse.org/t/reverse-proxy-x-forwarded-for/403181
**Category:** Support
**Tags:** unsupported-install, nginx
**Created:** [May 17, 2026, 4:27am UTC](https://meta.discourse.org/t/reverse-proxy-x-forwarded-for/403181 "2026-05-17T04:27:01Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Eviepayne](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviepayne/32/352733_2.png) [@Eviepayne](https://meta.discourse.org/u/Eviepayne)
#### Post date: [May 17, 2026, 4:27am UTC](https://meta.discourse.org/t/reverse-proxy-x-forwarded-for/403181/1 "2026-05-17T04:27:02Z")

</div>

I recently migrated my forum to a much more performant host, and I am working towards high availability.

in the reverse proxy I added the Forward Proto and For headers but the nginx configuration on the discourse only respected the Proto.

I had to add under server:

```nginx
set_real_ip_from loadbalancerip;
real_ip_header X-Forwarded-For;

```

Is there a discourse envvar to add these?  
or possibly a argument to add to app.yml?

---

_[View the full topic](https://meta.discourse.org/t/reverse-proxy-x-forwarded-for/403181)._