Hi Guillaume, usually it's working out-of-the-box. Check the Developer (JavaScript) Console of your web browsers for error messages:
- https://developers.google.com/web/tools/chrome-devtools/debug/console/ - https://msdn.microsoft.com/en-us/library/gg589530(v=vs.85).aspx Typically the problem is either the mixed content policy of your web browser (e. g. using HTTPS only for the web interface but not for the Graylog REST API) or having the Graylog REST API not publicly accessible for your web browser. Cheers, Jochen On Tuesday, 2 August 2016 12:35:38 UTC+2, Guillaume Migaszewski wrote: > > Well I have a connection refused message from IE 10 and Chrome 52 . > > Is it working out of the box or do I have to do something on web browser > side ? > > Until now I was looking on server side , configuration file. But I see no > parameters for restriction ... . > > I am lost . > > Thanks for your assistance. > > Guillaume. > > On Tuesday, August 2, 2016 at 12:29:40 PM UTC+2, Jochen Schalanda wrote: >> >> Hi Guillaume, >> >> the web interface of Graylog 2.x is accessing the Graylog REST API >> directly. You browser must be able to communicate with the Graylog REST API. >> >> Cheers, >> Jochen >> >> On Tuesday, 2 August 2016 12:25:39 UTC+2, Guillaume Migaszewski wrote: >>> >>> Hello Jochen, >>> >>> Thanks for your reply and for taking some time to read my post. >>> >>> Classic install , rpm based. Yes I have seen this page... but it is not >>> entirely clear for me. I have no firewall in place for testing. >>> >>> Do I need to setup a proxy to access my graylog server web interface >>> from another computer than my server ?. >>> >>> from the Doc >>> >>> Both the web interface port (http://127.0.0.1:9000/ by default, see >>> web_listen_uri) and the REST API port (http://127.0.0.1:12900 by >>> default, see rest_listen_uri and rest_transport_uri) must be accessible by >>> everyone using the web interface. This means that both components must >>> listen on a public network interface or be exposed to one using a proxy or >>> NAT! >>> >>> >>> I am not use to this REST API ... so I am confused. ... ah the good old >>> LAMP setup ... ;) . >>> >>> Regards >>> >>> Guillaume >>> >>> >>> >>> On Tuesday, August 2, 2016 at 12:12:58 PM UTC+2, Jochen Schalanda wrote: >>>> >>>> Hi Guillaume, >>>> >>>> how exactly did you install Graylog (OVA, OS packages, or manual >>>> install/environment specifics)? Did you read >>>> http://docs.graylog.org/en/2.0/pages/configuration/web_interface.html? >>>> >>>> Cheers, >>>> Jochen >>>> >>>> On Tuesday, 2 August 2016 11:59:14 UTC+2, Guillaume Migaszewski wrote: >>>>> >>>>> Dear Graylog group, >>>>> >>>>> I am new to graylog. I have successfully installed latest version of >>>>> graylog 2.0.3 according to official documentation. Graylog is working but >>>>> .... I can only login via local host http://127.0.0.1:9000 ... not >>>>> ideal when your servers are setup to init3 ... . >>>>> >>>>> As a result I would like to know if this is the normal behavior . I >>>>> was thinking about using Apache with mod proxy ... a bit overkill but ... >>>>> . >>>>> >>>>> Thanks for you help. >>>>> >>>>> Guillaume. >>>>> >>>> -- 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/c62cabc5-f30b-4429-8cf5-04f6e06b3e52%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
