# HAProxy / NGINX SYSLOG keep originating IP?

**URL:** <https://discuss.elastic.co/t/haproxy-nginx-syslog-keep-originating-ip/118894>\
**Category:** Logstash\
**Created:** [February 7, 2018, 5:36pm UTC](https://discuss.elastic.co/t/haproxy-nginx-syslog-keep-originating-ip/118894 "2018-02-07T17:36:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![devinacosta](https://avatars.discourse-cdn.com/v4/letter/d/a3d4f5/32.png) [@devinacosta](https://discuss.elastic.co/u/devinacosta)\
**Post date:** [February 7, 2018, 5:36pm UTC](https://discuss.elastic.co/t/haproxy-nginx-syslog-keep-originating-ip/118894/1 "2018-02-07T17:36:21Z")

</div>

We are looking to put either NGinx or HAProxy in front to provide some level of High Availability in regards to our syslog ingest. What we have noticed is to get syslog to work we use protocol TCP however all the messages then get logged as coming from NGinx or HAProxy, is there a trick to get it so it shows the originating box instead of the Load Balancer?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 11, 2018, 9:32pm UTC](https://discuss.elastic.co/t/haproxy-nginx-syslog-keep-originating-ip/118894/2 "2018-02-11T21:32:35Z")

</div>

Logstash's tcp input supports v1 of the Proxy protocol that solves this problem. See [http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 11, 2018, 9:45pm UTC](https://discuss.elastic.co/t/haproxy-nginx-syslog-keep-originating-ip/118894/3 "2018-03-11T21:45:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
