# Connect local Kibana instance to remote Elasticsearch instance behind a proxy

**URL:** <https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283>\
**Category:** Kibana\
**Created:** [July 10, 2018, 7:16am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283 "2018-07-10T07:16:57Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Giuseppe\_Merlo](https://avatars.discourse-cdn.com/v4/letter/g/a88e57/32.png) [@Giuseppe\_Merlo](https://discuss.elastic.co/u/Giuseppe_Merlo)\
**Post date:** [July 10, 2018, 7:16am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283/1 "2018-07-10T07:16:57Z")

</div>

Hi everyone!

As title says, i'm trying to connect a local Kibana instance to a remote ES instance. ES instance is working behind a proxy.  
I set up elasticsearch.url in kibana.yml to url that permits to access remote ES, but Kibana log is:

`[error][status][plugin:elasticsearch@6.2.2] Status changed from yellow to red - Request Timeout after 3000ms`

If i connect my pc to our corporate network bypassing proxy and if i set ES ip and port in kibana.yml elasticsearch.url, it works fine!

Maybe do I have to change something in proxy?

Thanks for your reply!

**EDIT:** I forget to say that ES instance is accessible by Browser API Call or Advanced Rest Client API Call from remote pc.

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [July 10, 2018, 8:19am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283/2 "2018-07-10T08:19:15Z")

</div>

Hi @Giuseppe_Merlo,

Hmm, can you try to increase values in `elasticsearch.pingTimeout` and `elasticsearch.requestTimeout` (kibana.yml) to something like `500000`, just to make sure you're not hitting a _real_ timeout because of proxy?

Thanks,  
Oleg

---

<div class="post-metadata">

**Author:** ![Giuseppe\_Merlo](https://avatars.discourse-cdn.com/v4/letter/g/a88e57/32.png) [@Giuseppe\_Merlo](https://discuss.elastic.co/u/Giuseppe_Merlo)\
**Post date:** [July 10, 2018, 8:52am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283/3 "2018-07-10T08:52:18Z")

</div>

Hi!  
Thank you for reply!

I've tried to set up these 2 parameters but Kibana log is the same:

`[error][status][plugin:elasticsearch@6.2.2] Status changed from yellow to red - Request Timeout after 3000ms`

it seems that Kibana doesn't see changes.

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [July 10, 2018, 9:05am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283/4 "2018-07-10T09:05:57Z")

</div>

> [@Giuseppe\_Merlo](#):
>
> Request Timeout after 3000ms

Hmm, that's weird. Okay a silly question, have you restarted Kibana and are you sure you don't have some old `kibana.yml` sitting somewhere at `/etc/kibana/kibana.yml` or something like that?

In the meantime, I'll go and check source code to see where this old `3000ms` comes from, I see Kibana 6.2.2 is [defaulting to 30000, not 3000](https://github.com/elastic/kibana/blob/v6.2.2/src/core_plugins/elasticsearch/index.js#L36).

Best,  
Oleg

---

<div class="post-metadata">

**Author:** ![Giuseppe\_Merlo](https://avatars.discourse-cdn.com/v4/letter/g/a88e57/32.png) [@Giuseppe\_Merlo](https://discuss.elastic.co/u/Giuseppe_Merlo)\
**Post date:** [July 10, 2018, 9:11am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283/5 "2018-07-10T09:11:49Z")

</div>

No, there's not another `kibana.yml` and i have restarted Kibana after configurations changing.

Thanks so much for your support!

**EDIT:** In my kibana/src/core\_plugins/elasticsearch/index.js i have timeout set to 30000.

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [July 10, 2018, 9:55am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283/6 "2018-07-10T09:55:05Z")

</div>

Hmm, it turned out to be a [known bug](https://github.com/elastic/elasticsearch-js/issues/547) . And there was even [PR with workaround](https://github.com/elastic/kibana/pull/19308/files) (you can try that locally if you want).

I'll check with relevant team once they wake up if there is anything we can do and let you know.

Best,  
Oleg

---

<div class="post-metadata">

**Author:** ![Giuseppe\_Merlo](https://avatars.discourse-cdn.com/v4/letter/g/a88e57/32.png) [@Giuseppe\_Merlo](https://discuss.elastic.co/u/Giuseppe_Merlo)\
**Post date:** [July 10, 2018, 10:15am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283/7 "2018-07-10T10:15:35Z")

</div>

I used that workaround and it changes Request Timeout but it doesn't fix my original issue.

`log [10:14:36.996] [error][status][plugin:elasticsearch@6.2.2] Status changed from yellow to red - Unable to connect to Elasticsearch at http://elasticsearch.tilab.com/elasticsearch/.`

```
http://elasticsearch.tilab.com/elasticsearch/ 

```

is public IP to Elasticsearch behind Proxy

Thank you for everything.

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [July 10, 2018, 10:39am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283/8 "2018-07-10T10:39:32Z")

</div>

I see, can you try specifically mention `port` in the `elasticsearch.url`: `http://elasticsearch.tilab.com:80/elasticsearch`?

---

<div class="post-metadata">

**Author:** ![Giuseppe\_Merlo](https://avatars.discourse-cdn.com/v4/letter/g/a88e57/32.png) [@Giuseppe\_Merlo](https://discuss.elastic.co/u/Giuseppe_Merlo)\
**Post date:** [July 10, 2018, 11:03am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283/9 "2018-07-10T11:03:26Z")

</div>

Adding port seems to fix the issue!

You've saved me!

Thank you so much!!!!

---

<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:** [August 7, 2018, 11:03am UTC](https://discuss.elastic.co/t/connect-local-kibana-instance-to-remote-elasticsearch-instance-behind-a-proxy/139283/10 "2018-08-07T11:03:32Z")

</div>

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