Well the POST requests worked with authorization, but said it didnt 
understand me. I tried with another api request that seemed to work fine 
when I authenticate properly.

# curl -i -X GET http://localhost:12900/system/inputs -u admin
Enter host password for user 'admin':
HTTP/1.1 200 OK
X-Graylog-Node-ID: ac7773b1-403d-4d3d-acc7-98a779140854
X-Runtime-Microseconds: 8838
Content-Type: application/json
Date: Thu, 26 May 2016 14:28:47 GMT
Content-Length: 937

{"inputs":[{"title":"GELF TCP for security logs","global":true,"name":"GELF 
TCP","content_pack":null,"created_at":"2015-12-09T07:11:48.095Z","type":"org.graylog2.inputs.gelf.tcp.GELFTCPInput","creator_user_id":"admin","attributes":{"recv_buffer_size":1048576,"port":12201,"use_null_delimiter":true,"tls_key_password":"","tls_key_file":"","tls_client_auth_cert_file":"","max_message_size":2097152,"tls_client_auth":"disabled","override_source":"","bind_address":"0.0.0.0","tls_cert_file":""},"static_fields":{},"node":null,"id":"5667d434a78e92fb03f07aa5"},{"title":"GELF
 
UDP for security logs","global":true,"name":"GELF 
UDP","content_pack":null,"created_at":"2015-12-09T07:11:34.949Z","type":"org.graylog2.inputs.gelf.udp.GELFUDPInput","creator_user_id":"admin","attributes":{"override_source":"","recv_buffer_size":262144,"bind_address":"0.0.0.0","port":12201},"static_fields":{},"node":null,"id":"5667d426a78e92fb03f07a94"}],"total":2}

What to configure?

On Thursday, 26 May 2016 14:07:18 UTC+2, Dennis Oelkers wrote:
>
> > On 26.05.2016, at 10:53, Martin René Mortensen <[email protected] 
> <javascript:>> wrote: 
> > 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 
> > 
>
> Can you try doing the request using your user’s credentials? 
>
> -- 
> 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/2b559d33-bdb2-49bc-a237-4d2f74df7f82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to