Hi, the graylog2-web-interface is using the graylog2-server.uris setting from the configuration to build the hyperlinks to the graylog2-server API browser.
In your case, you obviously run graylog2-server and graylog2-web-interface on the same system and thus use the loopback interface (localhost/127.0.0.1) to connect both components. The API browser runs inside graylog2-server, so please try to bind graylog2-server to a public network interface (see the rest_listen_uri in your graylog2.conf) and try to access it through that interface. But please be aware that it might have severe security implications if you bind graylog2-server to a public network! Cheers, Jochen Am Dienstag, 19. August 2014 21:26:36 UTC+2 schrieb Manuel Garrido Peña: > > Hi, > > We are setting up Graylog in my company, we are using AWS (m3 instance), > and everything is going fine, however, we cant make the api browser work. > (navigating to the api-browser via the interface points to > http://127.0.0.1:12900/api-browser , which is not found) > > Here is the config file that we have set up right now. > > https://gist.github.com/manugarri/306537ab7c502625b834 > > I read that enabling > > rest_enable_cors = true > > Would make it work, however, changing that parameter didnt fix the issue. > > Is there any parameter on the config file that needs to be modified for > graylog2 implementations in AWS? > > Thanks so much for your help! > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
