Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running Graylog in /subfolder/ is not possible #5702

Closed
jalogisch opened this issue Feb 20, 2019 · 8 comments
Closed

Running Graylog in /subfolder/ is not possible #5702

jalogisch opened this issue Feb 20, 2019 · 8 comments
Assignees

Comments

@jalogisch
Copy link
Contributor

@jalogisch jalogisch commented Feb 20, 2019

Expected Behavior

Graylog should run on a subfolder from a proxy setup that you can access http://your-proxy/graylog/ to get Graylog that is running in the network somewhere.

Current Behavior

ezgif com-gif-maker

Steps to Reproduce (for bugs)

  1. Install Graylog
  2. Install NGINX taking config from: http://docs.graylog.org/en/3.0/pages/configuration/web_interface.html#nginx
  3. Adjust to your local Networt
    screenshot 2019-02-20 16 48 07

Context

It is not uncommon to have Graylog running in a subfolder when you expose it via proxy from a network to another. That worked before and should work again. To not break existing setups when they upgrade.

Your Environment

  • Graylog Version: 3.0
  • Elasticsearch Version: 6.6.0
  • MongoDB Version:4.0
  • Operating System: Linux
  • NGINX: 1.12.2
@jalogisch jalogisch added the bug label Feb 20, 2019
@dennisoelkers dennisoelkers self-assigned this Feb 20, 2019
dennisoelkers added a commit that referenced this issue Feb 20, 2019
In #5193, the newly created `NavigationLink` component performs
prefixing the path passed to it with the application prefix. This is
happening although in `Routes.jsx` all routes are already being prefixed
before being exported.

This change is removing the prefixing in `NavigationLink`.

Fixes #5702.
@jlcrow
Copy link

@jlcrow jlcrow commented Feb 22, 2019

3.0 really screwed the config on this one. I followed the document http://docs.graylog.org/en/3.0/pages/upgrade/graylog-3.0.html to upgrade from 2.5 to 3.0 and updated the variables in the configuration with the external url. Everything fails, I've tried updating several properities including the http_external_uri, http_bind_address, and http_publish_uri with various options trying to mirror the functionality provided by web_endpoint_uri, web_listen_uri, and rest_listen_uri previously. Nothing works properly.

@deeshe deeshe added the triaged label Feb 25, 2019
@kmerz kmerz closed this in #5703 Feb 26, 2019
kmerz added a commit that referenced this issue Feb 26, 2019
…5703)

* Prevent double prefixing paths for navigation items in system menu.

In #5193, the newly created `NavigationLink` component performs
prefixing the path passed to it with the application prefix. This is
happening although in `Routes.jsx` all routes are already being prefixed
before being exported.

This change is removing the prefixing in `NavigationLink`.

Fixes #5702.

* Removing unneeded import.
dennisoelkers added a commit that referenced this issue Mar 12, 2019
This PR is backporting #5703 to `3.0`.

In #5193, the newly created `NavigationLink` component performs
prefixing the path passed to it with the application prefix. This is
happening although in `Routes.jsx` all routes are already being prefixed
before being exported.

This change is removing the prefixing in `NavigationLink`.

Fixes #5702.

(cherry picked from commit bcf53ec)
kmerz added a commit that referenced this issue Mar 14, 2019
…5765)

This PR is backporting #5703 to `3.0`.

In #5193, the newly created `NavigationLink` component performs
prefixing the path passed to it with the application prefix. This is
happening although in `Routes.jsx` all routes are already being prefixed
before being exported.

This change is removing the prefixing in `NavigationLink`.

Fixes #5702.

(cherry picked from commit bcf53ec)
@marif1989
Copy link

@marif1989 marif1989 commented Mar 27, 2019

I am facing the same issue? please let me know what was the solution?

@bernd
Copy link
Member

@bernd bernd commented Mar 27, 2019

@marif1989 The upcoming version 3.0.1 of Graylog has a fix for this.

@marif1989
Copy link

@marif1989 marif1989 commented Mar 27, 2019

@bernd
Copy link
Member

@bernd bernd commented Mar 27, 2019

@marif1989 We are planning to release it next week.

@marif1989
Copy link

@marif1989 marif1989 commented Apr 3, 2019

is graylog version 3.0.1 version released?

@bernd
Copy link
Member

@bernd bernd commented Apr 3, 2019

@marif1989 Yes, please see the announcement blog post: https://www.graylog.org/post/announcing-graylog-3-0-1

@gimmesomethinggood
Copy link

@gimmesomethinggood gimmesomethinggood commented Jun 29, 2019

When will be this version coming? Actually I am using Apache as proxy not ngnix.

On Wed, Mar 27, 2019, 6:08 PM Bernd Ahlers @.***> wrote: @marif1989 https://github.com/marif1989 The upcoming version 3.0.1 of Graylog has a fix for this. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5702 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AbkFHdakaUHznreGpdEgmNH4-Q-Hj-G_ks5va2ZAgaJpZM4bFoVB .

@marif1989 Did you ever get this working with Apache? If so what worked for you? I am trying to do the same thing...I am on 3.0.2 and it is not working for me.

Here is my config...

# Graylog
 ProxyPass /graylog/ http://servername:9000/
 ProxyPassReverse /graylog/ http://servername:9000/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

7 participants