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

API-Browser breaks in sub-directory or with "old" config #5078

DerPhlipsi opened this Issue Sep 6, 2018 · 0 comments


None yet
2 participants

DerPhlipsi commented Sep 6, 2018

This is an issue from this community post:
Basically, the API-Browser breaks when Graylog is used from a sub-directory or (from what it seems) "the old way of configuring the endpoints".

Expected Behavior

The Graylog API-Browser should always work, even in a sub-directory.

Current Behavior

The Graylog API-Browser breaks when using "the old way of configuring the endpoints" in the configuration regarding URLs or if you use Graylog from a directory (e.g. http://nuci.lan/graylog/). It fails to replace placeholders with the actual value.

Possible Solution

As @jalogisch mentioned:

The swagger version should be updated and this should work in any configuration.

Steps to Reproduce (for bugs)

  1. Setup Graylog Instance in sub-dir or with the old configuration way for rest and web URIs.
  2. Open API-Browser.
  3. Profit.


Other teams want access to our data and need a playground for learning the API and my colleagues want to start integrating their systems with Graylog without my guidance.

Your Environment

  • Graylog Version: 2.4.6
  • Elasticsearch Version: 5.6.9
  • MongoDB Version: v3.4.2
  • Operating System: RHEL7
  • Browser version: Firefox 61.0.2 (64-Bit)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment