HTTP_PROXY support for connections towards Elasticsearch

[markdav]

I can't run Kibana behind a corporate firewall, pointing at an elasticsearch instance outside of the corporate firewall. When I try to do so I get the error:

{"name":"Kibana","hostname":"kibanahost.mycorp.com","pid":31277,"level":50,"err":{"message":"Request Timeout after 5000ms","name":"Error","stack":"Error: Request Timeout after 5000ms\n at null. (/home/markdav/kibana-4.1.2-linux-x64/src/node_modules/elasticsearch/src/lib/transport.js:282:15)\n at Timer.listOnTimeout as ontimeout"},"msg":"","time":"2015-10-27T20:08:37.995Z","v":0}
{"name":"Kibana","hostname":"kibanahost.mycorp.com","pid":31277,"level":60,"err":{"message":"Request Timeout after 5000ms","name":"Error","stack":"Error: Request Timeout after 5000ms\n at null. (/home/markdav/kibana-4.1.2-linux-x64/src/node_modules/elasticsearch/src/lib/transport.js:282:15)\n at Timer.listOnTimeout as ontimeout"},"msg":"","time":"2015-10-27T20:08:37.997Z","v":0}

the http_proxy/https_proxy (upper and lowercase) is set, and curls, etc work just fine.

[rashidkpc]

This is likely due to using wreck: hapijs/wreck#64

[jperkelens]

Running into this issue as well, I'm not sure it's the same thing as the wreck dependency as it seems like it's only being used for plugin installation. Kibana is not respecting HTTP_PROXY / NO_PROXY env variables when trying to request status updates from an Elasticsearch cluster behind a proxy. And AFAIK the console.proxyConfig setting isn't meant for configuring a general proxy kibana should be making requests through.

[mrvincenzo]

Any updates? I am able to reproduce this bug with Kibana 5.2.2

[Ochir]

any updates? @timroes is it possible to migrate code from #12753 to fix this issue?

[tylersmalley]

This feature request is an interesting idea but since its opening, we have not seen enough feedback that it is a feature we should pursue. We prefer to close this issue as a clear indication that we are not going to work on this at this time. We are always open to reconsidering this in the future based on compelling feedback; despite this issue being closed please feel free to leave feedback on the proposal (including +1s).