On Thursday, 26 May 2016 10:33:03 UTC+2, Dennis Oelkers wrote: > > Hey Martin, > > > On 26.05.2016, at 09:19, Martin René Mortensen <[email protected] > <javascript:>> wrote: > > > > After upgrading and reconfiguring my apache proxy for the new > graylog-server 2.0.1 according to > http://docs.graylog.org/en/2.0/pages/configuring_webif.html I can get it > to login and see messages, but some pages are blank or wont load. In web > browser debug mode I can see > > > > It seems that graylog api needs authentication which its not getting > from when graylog itself calls it? > > > > My browser seems to be getting some replies when hitting > http://graylog-web-url/system/inputs , but it shows my 2 inputs as 0 > RUNNING and the output it gets from the ajax requests looks odd to me. Only > response for /system/inputstates is (json) > > {"ac7773b1-403d-4d3d-acc7-98a779140854":null} > > it looks like your Graylog server cannot connect back to itself. Do you > see anything related to this in the server log? > Exactly what its saying. but it doesnt make any sense. 2016-05-26T09:20:46.527+02:00 WARN [ProxiedResource] Unable to call http://localhost:12900/system/metrics/multiple on node <ac7773b1-403d-4d3d-acc7-98a779140854>, result: Service Unavailable 2016-05-26T09:20:48.520+02:00 WARN [ProxiedResource] Unable to call http://localhost:12900/system/metrics/multiple on node <ac7773b1-403d-4d3d-acc7-98a779140854>, result: Service Unavailable 2016-05-26T09:20:50.517+02:00 WARN [ProxiedResource] Unable to call http://localhost:12900/system/metrics/multiple on node <ac7773b1-403d-4d3d-acc7-98a779140854>, result: Service Unavailable 2016-05-26T09:20:52.496+02:00 WARN [ProxiedResource] Unable to call http://localhost:12900/system/metrics/multiple on node <ac7773b1-403d-4d3d-acc7-98a779140854>, result: Service Unavailable 2016-05-26T09:20:54.519+02:00 WARN [ProxiedResource] Unable to call http://localhost:12900/system/metrics/multiple on node <ac7773b1-403d-4d3d-acc7-98a779140854>, result: Service Unavailable 2016-05-26T09:20:56.716+02:00 WARN [ProxiedResource] Unable to call http://localhost:12900/system/metrics/multiple on node <ac7773b1-403d-4d3d-acc7-98a779140854>, result: Service Unavailable 2016-05-26T09:20:58.745+02:00 WARN [ProxiedResource] Unable to call http://localhost:12900/system/metrics/multiple on node <ac7773b1-403d-4d3d-acc7-98a779140854>, result: Service Unavailable
when I try, I get a 401 error. From the client the calls to graylog api needs to be authenticated, but do calls from internal graylog also have to be authenticated? curl -I -X POST http://localhost:12900/system/metrics/multiple HTTP/1.1 401 Unauthorized WWW-Authenticate: Basic realm="Graylog Server" X-Graylog-Node-ID: ac7773b1-403d-4d3d-acc7-98a779140854 X-Runtime-Microseconds: 3195 Date: Thu, 26 May 2016 08:52:00 GMT Content-Length: 0 > > > Im not even sure how this would work in a multi graylog node > configuration, rest_transport_uri is localhost... which noone outside local > apache can reach. > > If you are running a multi node setup, you need to configure > rest_transport_uri & rest_listen_uri on every node to something that is > reachable from the other nodes. > ok, I get that. Just hope it works from clients through proxy as well. (yes, I need to change the proxypass destinations in apache config as well). > > Kr, > D. > > -- > Tel.: +49 (0)40 609 452 077 > Fax.: +49 (0)40 609 452 078 > > TORCH GmbH - A Graylog company > Steckelhörn 11 > 20457 Hamburg > Germany > > Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175 > Geschäftsführer: Lennart Koopmann (CEO) > > -- 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/5ba257a5-ef06-406e-86af-e30e741830e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
