# Kibana Timelion doesn't use proxy when connecting to Quandl

**URL:** <https://discuss.elastic.co/t/kibana-timelion-doesnt-use-proxy-when-connecting-to-quandl/66140>\
**Category:** Kibana\
**Tags:** timelion\
**Created:** [November 15, 2016, 5:52pm UTC](https://discuss.elastic.co/t/kibana-timelion-doesnt-use-proxy-when-connecting-to-quandl/66140 "2016-11-15T17:52:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Drew\_Town](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drew_town/32/44829_2.png) [@Drew\_Town](https://discuss.elastic.co/u/Drew_Town)\
**Post date:** [November 15, 2016, 5:52pm UTC](https://discuss.elastic.co/t/kibana-timelion-doesnt-use-proxy-when-connecting-to-quandl/66140/1 "2016-11-15T17:52:11Z")

</div>

We are behind a corporate proxy for all outgoing requests on 80 and 443. When using Timelion v5.0.0 and requesting data from Quandl we get a failure.

```
    Timelion: Error: in cell #3: request to [quandl url] failed, reason: connect ECONNREFUSED 54.174.87.84:443

```

Is there a configuration I am missing in order to get Timelion to utilize a proxy either via configuration or environment variable?

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [November 17, 2016, 5:52pm UTC](https://discuss.elastic.co/t/kibana-timelion-doesnt-use-proxy-when-connecting-to-quandl/66140/2 "2016-11-17T17:52:22Z")

</div>

This could be happening because requests for data Timelion that makes come from the Kibana server, not the browser. Having a firewall between the Kibana server and the outside Internet is likely the problem.

---

<div class="post-metadata">

**Author:** ![Drew\_Town](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drew_town/32/44829_2.png) [@Drew\_Town](https://discuss.elastic.co/u/Drew_Town)\
**Post date:** [November 17, 2016, 7:03pm UTC](https://discuss.elastic.co/t/kibana-timelion-doesnt-use-proxy-when-connecting-to-quandl/66140/3 "2016-11-17T19:03:43Z")

</div>

I do have http\_proxy and https\_proxy environment variables setup on the kibana server. It doesn't seem to utilize those variables though.

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [November 17, 2016, 7:56pm UTC](https://discuss.elastic.co/t/kibana-timelion-doesnt-use-proxy-when-connecting-to-quandl/66140/4 "2016-11-17T19:56:11Z")

</div>

> [@Drew\_Town](#):
>
> http\_proxy and https\_proxy environment

As far as I can tell, software has to be designed to be aware of that variable, and many Ubuntu utilities are, such as `apt-get`. But it looks like NodeJS isn't aware of that env. variable and it doesn't come with its own way to configure proxy settings globally.

I have seen in some coding forums that people have decided to overwrite the `http.request` method in Node to get it to include global proxy settings. You are free to file an issue in [Issues · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues) and give the team a proposition for implementing a solution for this use case.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 15, 2016, 7:56pm UTC](https://discuss.elastic.co/t/kibana-timelion-doesnt-use-proxy-when-connecting-to-quandl/66140/5 "2016-12-15T19:56:42Z")

</div>

Closed on December 15, 2016, 7:56pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.