Hi Jochen, That's a good question! I'm sure I looked at this a few weeks ago and decided I needed to use localhost. I will revisit the Kibana setup and see if it can be changed.
On Wednesday, 14 September 2016 18:58:19 UTC+10, Jochen Schalanda wrote: > > Hi Michael, > > this setting can currently not be overridden in the OVA. > > Could you elaborate on why Kibana can't access Elasticsearch on the > primary network interface of the VM (which is where the IP address comes > from) and has to access it on 127.0.0.1? > > Cheers, > Jochen > > On Wednesday, 14 September 2016 10:16:17 UTC+2, Michael Anthon wrote: >> >> Hi All, >> Every time I run the reconfigure command at the moment it updated the >> "network.host" entry in /opt/graylog/elasticsearch/config/elasticsearch.yml >> to the network address of the machine instead of the (for me) desired >> 0.0.0.0 (I have Kibana running on the server as well attempting to connect >> to 127.0.0.1). >> >> I'm fairly sure this didn't happen prior to the last update I did to >> 2.1.0 and that there were no intentional config changes (but I won't rule >> that out!) >> >> I can see in the reconfigure output that it's replacing this line but I'm >> not sure where it's getting the network address from. >> >> Is this something that may have changed in the latest release and/or is >> there a way for me to override the setting so that elasticsearch will be >> configured to listen on 0.0.0.0? >> >> Currently I'm manually editing the >> /opt/graylog/elasticsearch/config/elasticsearch.yml after a reconfigure >> >> Thanks, >> Michael >> > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/2303b2ce-b669-40e3-a881-4151317f6011%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
