# Graylog behind nginx sub directory how-to configure

**URL:** <https://community.graylog.org/t/graylog-behind-nginx-sub-directory-how-to-configure/3968>\
**Category:** Graylog Central (peer support)\
**Created:** [January 29, 2018, 7:43pm UTC](https://community.graylog.org/t/graylog-behind-nginx-sub-directory-how-to-configure/3968 "2018-01-29T19:43:47Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [January 30, 2018, 1:34pm UTC](https://community.graylog.org/t/graylog-behind-nginx-sub-directory-how-to-configure/3968/8 "2018-01-30T13:34:22Z")

</div>

I’m still not clear how this is a problem with Graylog. The thread in the LibreNMS Community you’ve linked to clearly shows that the Graylog REST API is accessible via `http://<graylog-host>:8888/graylog/api`.

Maybe the LibreNMS Graylog integration simply doesn’t work?

One wild assed guess: LibreNMS is using HTTP/1.0, while curl is using HTTP/1.1.  
HTTP/1.0 doesn’t know anything about the HTTP `Host` header, so if your nginx is hosting anything other than Graylog (“virtual hosts”) and LibreNMS doesn’t perform a proper HTTP/1.1 request, it might not be able to serve the data it should.

---

_[View the full topic](https://community.graylog.org/t/graylog-behind-nginx-sub-directory-how-to-configure/3968)._