Using Graylog Helm Chart


(jubilee) #1

In an attempt to access the web browser I get the following error message below:

" We are experiencing problems connecting to the Graylog server running on http://publicIP:9000/api/ . Please verify that the server is healthy and working correctly.

You will be automatically redirected to the previous page once we can connect to the server. "

Side notes:

Graylog pods are healthy. No information related to the browser in logs.

We already have an existing Elasticsearch running in Dev environment, and I’ve already integrated Graylog to our Elasticsearch cluster. The only thing at this point is getting past the web UI issue. I’ll appreciate any help and suggestions.

Thanks in advance.

Graylog version: 2.5.1
MongoDB version: 3.8.7


(Jan Doberstein) #2

the API need to be reachable by your browser - e.g. http://100.115.66.182:9000/api/


(jubilee) #3

Thanks for the response Jan, below is a short snippet of my Config Maps.

[/quote]
graylog.conf:
node_id_file = /usr/share/graylog/data/journal/node-id
root_username = admin
root_email =
root_timezone = America/Los_Angeles
plugin_dir = /usr/share/graylog/plugin
rest_listen_uri = http://0.0.0.0:9000/api/
#web_enable = true
web_listen_uri = http://0.0.0.0:9000/
[/quote]

Here are the full details from the error web UI error :

[/quote]
Error message

Request has been terminated Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.

Original Request

GET http ://PublicIP:9000/api/system/sessions

Status code

undefined

Full error message

Error: Request has been terminated Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.

[/quote]

The pod seems to be working just fine, and there’s are no indications of any errors with regards to the webpage.

Side Note: I purposefully spaced the link GET http ://PublicIP:9000/api/system/sessions


(Jan Doberstein) #4

you should really format your postings with markdown - that would help to read your provided information.

Let me say it again the rest API need to be reachable by your browser - or you need to work with a proxy that make it accessable. Or you need tell via configuration were your browser can reach the API.

http://docs.graylog.org/en/2.5/pages/configuration/server.conf.html#general

Read the comments for rest_listen_uri and rest_transport_uri


(Tess) #5

This part is wrong. You cannot/shouldnot/mustnot bind the API etc to the catch-all IP.


(jubilee) #6

Thanks for your response Guys!, Does this look good?

 graylog.conf: |-
    root_timezone = {{ default "UTC" .Values.graylog.rootTimezone }}
    plugin_dir = /usr/share/graylog/plugin
    rest_listen_uri = http://0.0.0.0:9000/api/
    rest_transport_uri = http://graylog.testing-infrastructure.care/api ?
    web_listen_uri = http://127.0.0.1:9000/api/
    web_endpoint_uri =  http://graylog.testing-infrastructure.care/api

(Tess) #7

No.

Do you honestly want to make the web interface accessible from localhost only? And I do believe the REST API should not listen on 0.0.0.0.


(jubilee) #8

What do you propose? @Totally_Not_A_Robot


(Tess) #9

For starters, add your host’s actual IP address in there. The one that you want the API and web GUI to be reached at.


(jubilee) #11

All set! Thanks @Totally_Not_A_Robot


(jubilee) #12

Thanks a lot @jan All set now.