Graylog 3.0 behind proxy (apache with sub dir)

Graylog Central (peer support)
1

Hi all, this is actually my first post to the community.

I just upgraded from 2.5 to 3.0. Everything is working fine, for the most part.

My problem is that when putting graylog behind my proxy, everything under the ‘system’ menu is broken. An extra ‘/graylog’ is being added to the URL, which gives me the gorilla page. All other pages, dashboards, etc are fine.

I’m using Apache as my proxy. Here is the relevent configuration:

<Location /graylog>
    RequestHeader set X-Graylog-Server-URL "https://$public/graylog/"
    ProxyPass http://$private:9000
    ProxyPassReverse http://$private:9000
</Location>

For example: https://$public/graylog/system/overview gets set to https://$public/graylog/graylog/system/overview

I could rewrite things, but I think this is a problem with graylog itself. Everything was working properly with the 2.5 version.

2

Did you adjust the various URI settings in the server config file?

The split URIs for the API and Graylog were replaced, with one single config line. Both older config settings must be removed.

As per here ->

https://docs.graylog.org/en/3.0/pages/upgrade/graylog-3.0.html

3

Yes. Without having those right, nothing would work :slight_smile:

4

Well, without having the one right, nothing would work. But I can imagine having the other stay in place could double up on the “graylog” part of the URI. :slight_smile:

Glad that you thought of this though. Good on you.

5

The only weird breakage was some dashboard elements I had that used (this that) in queries. Apparently implicit ‘OR’ is gone now? But I digress. I’ll check things again, but it’s only the entire ‘system’ menu that is not working behind a proxy. Everything else is fine.

6

Seems I’m not the only one with this problem: https://github.com/Graylog2/graylog2-server/issues/5610

1 Like
7

Good find! Let’s continue in that thread on Github instead.

8

Unfortunately the issue has been closed. Another person posted the same problem. This definitely seems to be a graylog issue, and not the proxy. See https://github.com/Graylog2/graylog2-server/issues/5610#issuecomment-464274765

9

I have created one github issue for that now:

2 Likes
10

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