Thank you, but you might want to revise that.
localhost isnt enough, you need to be able to specify normal proxy
exclusions, like .domain. If you have multiple graylog servers they should
not use proxy to communicate.
Brgds. Martin
On Monday, 30 May 2016 14:30:02 UTC+2, Dennis Oelkers wrote:
>
Hey Martin,
we have now implemented a function to disable the proxy for requests going to
localhost. It is already merged and will be included in the next release of
Graylog.
Thanks for your support,
D.
> On 27.05.2016, at 12:19, Dennis Oelkers wrote:
>
>> On 27.05.2016, at 10:18, Ma
> On 27.05.2016, at 10:18, Martin René Mortensen
> wrote:
>
>
> On Friday, 27 May 2016 09:39:46 UTC+2, Dennis Oelkers wrote:
> Do you have the http_proxy_uri configuration directive set in your config
> file, by any chance?
>
> ah yes, I do, if it uses the http_proxy to access its internal
On Friday, 27 May 2016 09:39:46 UTC+2, Dennis Oelkers wrote:
>
> Do you have the http_proxy_uri configuration directive set in your config
> file, by any chance?
>
> ah yes, I do, if it uses the http_proxy to access its internal
interfaces, that would cause these errors - I see.
The response
Do you have the http_proxy_uri configuration directive set in your config file,
by any chance?
The response you are getting from the server for the /cluster/metrics/multiple
call implies that it cannot connect back to itself (the response for the node
id is null), although you can do the call t
On Thursday, 26 May 2016 17:20:44 UTC+2, Dennis Oelkers wrote:
>
> What happens when you do something like:
>
> curl -XPOST -u admin -v -H "Content-Type: application/json" -d
> '{"metrics": []}' http://localhost:12900/cluster/metrics/multiple
>
> looks good:
* Trying 127.0.0.1...
* Connected
What happens when you do something like:
curl -XPOST -u admin -v -H "Content-Type: application/json" -d '{"metrics":
[]}' http://localhost:12900/cluster/metrics/multiple
and
curl -XPOST -u admin -v -H "Content-Type: application/json" -H "Accept:
application/json” -d '{"metrics": []}'
http://l
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-Graylo
> On 26.05.2016, at 10:53, Martin René Mortensen
> 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
> , result: Service Unavailable
> 2016-05-26T09:20:4
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 > 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/confi
Hey Martin,
> On 26.05.2016, at 09:19, Martin René Mortensen
> 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 a
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
12 matches
Mail list logo